Category:Type

A type describes a range of possible values. This includes numbers or other primitive types, but also more abstract concepts ranging from text, users, join requests up to just “parts of a world”.

Categorization

Types can be split into different categories. In many situations there is some kind of distinction between “simple” and “complex” types.

The specifics are dependent on the context you are talking about.

ProtoFlux

Execution of ProtoFlux is a local phenomenon that runs on the computer that started it. In fact the ProtoFlux implementation has been designed to be independent of FrooxEngine.^{[Citation needed]}

In summary it stays close to the underlying C# standards. C# differentiates types based on where the value is stored:

Also see: Enums, a subcategory of value types.

World Model

The world model of Resonite needs to be kept consistent for multiple users. Where a value is stored locally is far less important than how it is communicated across the network.

In effect this means that when dealing with components and their properties one has to differentiate among the following categories:

Be aware that strings, URIs and Nullable are objects in ProtoFlux but values for the world model!
This is especially visible when working with Dynamic Variables.

Generic Types

Generic types are special in that they have type arguments which have to be filled with another type before you can use them. They allow a programmer to write code that can be specialised for a specific use-case without additional implementation. (written once, applied for many types)

They are often used for components that store or process values. Properties and many ProtoFlux nodes are also implemented via generic types.

Type arguments have to be specified in the node browser or component attacher to create a generic node/component.
If you use a generic type as an argument, follow the instructions within the article Complex Types in Components!