(CUID) Second UUID for Animations, Obtainable Only by Creator / on Upload
Ross Myhre
Animations are not currently triggerable via UUID. For reasons we won't discuss this is unlikely to change. Despite this, many of us would like to facilitate script triggered animations without the need for an animation file in the contents.
Therefore, I propose a second UUID be granted to .bvh and . anim files which can only be obtained by the creator. Possibly terming it CUID, which would stand for Creators Unique Identifier, or something like that.
Perhaps this can be acheived by only generating / revealing the CUID one time during upload. This could preclude all existing animations, removing the requirement to retroactively allocate them CUIDs.
Alternatively, by adding a right click function to the inventory which would check if the owner matches the creator before revealing the CUID. This might require / facilitate existing animations being allocated CUIDs. Maybe the right click function could trigger CUID generation on first use, which would give creators the choice, and not result in unused CUIDs being generated automatically for existing animations.
Log In
Lucia Nightfire
How about making playing animations by UUID require the script to be compiled with the animation creator's experience.
Experience permissions are NOT required for animating.
The compiled experience just acts as a guarantor or the creator's seal of approval.
Only animations created by the experience owner can be played via UUID.
Alternatively, if scripts had "last compiled by" and "last compile time" metadata, the former, itself, could be used without need for an experience.
All animation assets "should" have metadata for "creator" or "uploaded by".
The bad thing about this concept is that it gatekeeps content and ruins any chance of end-users making modifications or repurposing.
Ross Myhre
Lucia Nightfire Works for me! I'm only looking at this from the perspective of using my own animations, objects, and scripts.