ProtoFlux:FireOnChange

Fire On Change

OnlyForUser

OnChanged

Value

Flow

This page is marked for deletion.

Reason: useless template

Please use the article's talk page if you would like to discuss or contest deletion.

See the Resonite Wiki's deletion policy for more details.
Admins: Please check the talk page for any discussions on the matter. Remember to remove all redirects, links, and transclusions relating to this page if deleted.
This page was last edited by YoshBot at 23:52, 20 August 2025 (UTC)

Using this node with Local User or no user input may cause undesired outcomes.

Fire On Change Nodes will only fire if the OnlyForUser (User) provided has seen the value on their local machine change.

When this node triggers from the OnlyForUser (User) provided it can be used to execute code that requires the impulse be from a specific user. This is useful for things like:

• changing world properties
• physics
• cloud variables
• other Local User sensitive nodes.

This node does not runs the calculation on every frame.

Inputs

OnlyForUser (User)

Is the User "watching" for changes, if the Value (Generic) is localized and only changes for the OnlyForUser User, then it will send out a impulse for every change vs someone else who wouldn't see those changes.

For best practice, this should never be left null or evaluated differently based on the user (e.g. via LocalUser). If this input is null and the node is parented under a user, then the impulse will be fired for said user. If this input is null and not parented under a user, or if this input evaluates differently for different users, then the impulse will tend to be fired for the first user that sees the change in value. This is usually the one who caused the change in the first place. This could cause inconsistent behavior unless carefully managed.

Value (Generic)

The value or reference that OnlyForUser (User) should watch for changes on their client.

Outputs

OnChanged (impulse)

Will fire a single impulse from the OnlyForUser (User) input every time the value provided changes.

Use Notes

Because FireOnChange functions based on the trigger for whatever node it is connected to, it may not fire when the node it is connected to is changed if that node does not account for the calculation before it. Therefore, if a node is firing unreiably, an easy fix would be to connect FireOnChange's value to a node below it, preferably whatever value is most critical to the change.[1]

Examples

• Fire On Change being used to tell when someone is on the ground according to the host user of a session.
  Fire On Change being used to tell when someone is on the ground according to the host user of a session.

See Also

• ProtoFlux:Fire On True
• ProtoFlux:Fire On False