Mint Shock (talk | contribs) Explain basic premise of the Standard proposal |
Mint Shock (talk | contribs) Mention Avatar Standard |
||
Line 1: | Line 1: | ||
Standardization is required for collaboration and shared assets. This is a proposal made by [[User:Mint Shock|Mint_Shock]] which standardizes a list of [[Dynamic variables|Dynamic Variables]] on the "System" namespace to make systems interoperable and portable and enables [[User|users]] to create systems which can easily be installed onto other objects like [[tools]], [[Avatar|avatars]], and much more. All without using any developer tools. | Standardization is required for collaboration and shared assets. This is a proposal made by [[User:Mint Shock|Mint_Shock]] which standardizes a list of [[Dynamic variables|Dynamic Variables]] on the "System" namespace to make systems interoperable and portable and enables [[User|users]] to create systems which can easily be installed onto other objects like [[tools]], [[Avatar|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 [[Slot|slots]], meshes, | '''Systems''' are anything that goes on top of an base object. This includes [[ProtoFlux]] logic and other [[:Category:Components:Assets|assets]] such as [[Slot|slots]], meshes, [[Texture2D|textures]] and much more. | ||
All variables must be defined including their namespace to avoid them accidentally binding to the wrong namespace: <code>System/VariableName</code>. The namespace must not rely on non-direct binding of variables. | All variables must be defined including their namespace to avoid them accidentally binding to the wrong namespace: <code>System/''VariableName''</code>. 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 | |||
== See also == | |||
* [[Avatar standard]] | |||
* | |||
[[Category:Community standards]] |
Revision as of 21:53, 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