ProtoFlux:Local

Local

*

Variables

This article or section is a Stub. You can help the Resonite Wiki by expanding it.

This page is missing content because it needs many more examples, since this node is quite a complex topic. TODO: Maybe explain this in reference to variables in programming?

Local Nodes will have the default value for their data type until written to during a context. During that context, the local node will keep the value from every write and change to it. Once the context is released, the value instantly returns to the default value, discarding the data, preventing it from being seen or networked. However, if its value is written to a Data Model Store it will persist, allowing it to be seen by everyone in the session through the network.

The visual on this page is not a good representation of the node's appearance in game at the moment.

The node in game has a string in the center that can be edited like a text field. This text field actually just renames the slot of the protoflux node, and will populate with the node's name when unpacked. This is useful for naming your variables, and should have no downsides. As such, never assume this node will have their slot name contain this node's type or something similar.

Locals as Scoped Variables

Local nodes represent a scoped, mutable value which is commonly called a variable. Unlike ProtoFlux:Store and ProtoFlux:Data Model Store, Local is scoped to an individual impulse context. This is similar to a variable that is defined inside of a function in an imperative programming language like JavaScript's var keyword, etc. Upon entering the value is initialized, and it is discarded once it goes out of scope. Like with variables in functions, every ProtoFlux impulse context also has its own independent (not shared) variable.

Unlike most programming languages, a local can be referenced from outside of a context (which would be like accessing a variable from outside the function it it declared). However, outside of any context, the local will just be whatever the default value of the type is. This is a common confusion in ProtoFlux: just because you can pull a wire from a local node doesn't mean that there is anything actually there. If you need to read/write to a variable outside of contexts, use a global and persistent variable like ProtoFlux:Store or ProtoFlux:Data Model Store.

Locals as Scoped Variables

See Also