Mint Shock (talk | contribs) mNo edit summary |
Mint Shock (talk | contribs) |
||
| Line 9: | Line 9: | ||
The '''System standard''' is designed primarely as a extension of the [[Avatar standard]]. Both proposals are designed to work together seamlessly. Systems can access variables from the [[Avatar standard]] by reading variables from the <code>Avatar</code> namespace. | The '''System standard''' is designed primarely as a extension of the [[Avatar standard]]. Both proposals are designed to work together seamlessly. Systems can access variables from the [[Avatar standard]] by reading variables from the <code>Avatar</code> namespace. | ||
Example: a flight thruster system might need to know in which direction the users hand is pointing in. Normally you would have to manually find the users hand node using [[ProtoFlux]]. [[Avatar standard]] simplifies this by providing [[Dynamic variable]] of type {{Template:TypeColorCard|Slot}}<code>Avatar/BodyNode.HandR</code> | Example: a flight thruster system might need to know in which direction the users hand is pointing in. Normally you would have to manually find the users hand node using [[ProtoFlux]]. [[Avatar standard]] simplifies this by providing [[Dynamic variable]] of type {{Template:TypeColorCard|Slot}} <code>Avatar/BodyNode.HandR</code> | ||
Dynamic variable | Dynamic variable | ||
== See also == | == See also == | ||
Revision as of 22:07, 25 September 2025
Standardization is required for collaboration and shared assets. This is a proposal made by Mint_Shock which standardizes a list of Dynamic Variables on the "System" namespace to make systems interoperable and portable and enables users to create systems which can easily be installed onto other objects like tools, avatars, and much more. All without using any developer tools.
Systems are anything that goes on top of an base object. This includes ProtoFlux logic and other assets such as slots, meshes, textures and much more.
All variables must be defined including their namespace to avoid them accidentally binding to the wrong namespace: System/VariableName. The namespace must not rely on non-direct binding of variables.
Avatar Standard
The System standard is designed primarely as a extension of the Avatar standard. Both proposals are designed to work together seamlessly. Systems can access variables from the Avatar standard by reading variables from the Avatar namespace.
Example: a flight thruster system might need to know in which direction the users hand is pointing in. Normally you would have to manually find the users hand node using ProtoFlux. Avatar standard simplifies this by providing Dynamic variable of type Slot Avatar/BodyNode.HandR
Dynamic variable