(I'm pretty sure the odds of this being the first pjira entry asking for this are quite small, but the search returned tons of results that had nothing to do with what I'm looking for (perhaps Google could lend a hand to the guys over Jira to enable better evaluation of relevancy of the search results?) there would be two types of CSG objects Dynamic CSG, these would have the root set to be CSG, and the child prims (probably a reduced maximum number of them) would be have a boolean operation assigned to them, union, intersection, exclusion, subtraction etc (without an operation set it is the same as union, or perhaps not even that if having it just be a regular child prim would save processing time and/or storage space), besides "Edit Linked Parts", there would be another checkbox for "Edit CSG Operators", that would make all the operators (childprims) of the selected CSG object be displayed as regular prims for editing. In a Dynamic CSG object, the childprims can run scripts and be modified by them just like regular childprims, but there would also be a way to change the operation each prim is meant to do (perhaps if the creation of new geometry is too costly, add a bit of forced delay, but try to keep the size of the delay to a minimum) Static CSG Objects would have as much prims as a regular linkset, but no scripts would be left running on Operator prims, and it can be linked as a single prim into a linkset, counting as a single prim, but while linked, the Operators can't be edited. While it is not linked, a script in the base prim can make the Operator prims turn into regular prims, making the scripts in them resume running (or if saving the state of that many scripts would be too expensive, have them start running from scratch). The Static CSG objects would be allowed to have so much more prims because their mesh would not be changed too frequently, it would only be necessary to transmit the data about the Operator prims when the Static CSG object is being edited, the rest of time, just a mesh (and texture mapping) needs to be informed, it might even be possible to run optimization algorithms on the mesh to reduce the number of vertexes even if it takes a couple of seconds since it will only happen sporadicly, also, it wouldn't have any scripts running on it's operators. This way they could also count as a single prim on linksets, since while linked, all that have to be communicated is the resulting mesh. CSG objects would inherit the texture mapping of the prims that made them, in the texture tab the parameters would be multipliers and offsets for the individual parameters of the the prims that originated the mapping, or perhaps some sort of automatic unwrapping could be another option. I'm not sure how the number of faces would be defined, perhaps each individual surface would be a face, or everything would be a single face, i'm not sure.