Heirarchical / Tree-based Linking & Move Sitting Avatar on script-moved prims

Proposal includes:

1. Hierarchical Linking (Tree-based linking)

a. Essentially, organize primitives in a tree / heirarchical set.
b. Branches could be trimmed off or added, removed, or re-ordered.
c. Individual prims could be edited, or entire branches.
d. Scripting linking could be altered to allow scripts to affect entire branches with sub-branches, or a list of branches. (Along with 1.7's movable attachment prims, would greatly improve ease-of-use and functionality of this new feature!)

2. Move sitting AV on script-moved prim

- Currently, Avatars sitting on prims are not moved if the prim is moved by a script.
- Since moving them by hand will move the AV, it makes sense that the script method should work the same way.
- This would allow new features for vehicles, seating, carnival rides, and combat games.

can we merge this with prop 16?

Merge? Sure. Substitute old one? No. The original was far less than what I'm proposing.

Hierarchy would be nice.

I've only been asking for it for two years...

Yeah, a bunch of us have. I think we've got potential with 1.7's moving attachments.

/dig
/dig
/dig

/dust off

/bump

You wish...

Mabey so but no one will blame me for trying

I want this too, especially being able to have an avatar on a sit-target of a child prim move with the child-prim. Hierarchy would be neat, but not a huge concern of mine atm.

Just tried to do something where the hierarchial model would have been really helpful actually.

I'm assuming what you mean is like linked-sets of linked-sets? e.g:-

Haravikk's Complicated Head:

1 - Prim 1
2 - Prim 2
3 - Prim 3
4 - Haravikk's Left Ear
   1 - Ear Prim 1
   2 - Ear Prim 2
5 - Haravikk's Right Ear
   1 - Ear Prim 1
   2 - Ear Prim 2

So the end result is that if I rotate the head, the whole head moves, but if a script in my ear attempts to move the ear, then it moves all the ear prims in a single movement? I just tried to do an attachment with static root prims, and moving parts, the moving part is quite prim heavy so having each piece move independantly doesn't do so in sync and looks horrible. While if I could have manipulated the entire moving piece as though it were a single prim, it would have been perfect?

It probably wouldn't be all that hard to do actually provided it didn't affect existing objects. Every time you link a linked-set to something, it becomes essentially a child-prim of what you linked to, but it has it's own root for scriptings and such.
Would have to watch out for scripting things like rotation, but it would be pretty awesome now that I think about it.