ProtoFlux:Update: Difference between revisions
From Resonite Wiki
More actions
m nullabl |
note about driven local user |
||
| Line 26: | Line 26: | ||
The user that the <code>OnUpdate</code> pulse will be generated from and owned by. | The user that the <code>OnUpdate</code> pulse will be generated from and owned by. | ||
This input can be [[drives|driven]] by a [[ProtoFlux:Local User|Local User]] node to generate impulses for every user. However, it would be better to use [[ProtoFlux:Local Update|Local Update]] for this specific node. | |||
=== SkipIfNull ([[Type:Nullable`1|Nullable]]<[[Type:bool|bool]]>) === | === SkipIfNull ([[Type:Nullable`1|Nullable]]<[[Type:bool|bool]]>) === | ||
Revision as of 19:27, 1 January 2025
Update
null
∅
null
∅
Flow
The Update node sends a pulse at every engine update from the UpdatingUser.
Outputs
OnUpdate (Call)
Sends a pulse every engine update from the UpdatingUser.
Globals
UpdatingUser (User)
The user that the OnUpdate pulse will be generated from and owned by.
This input can be driven by a Local User node to generate impulses for every user. However, it would be better to use Local Update for this specific node.
If True, no pulses will be generated if UpdatingUser is null. Otherwise, impulses will be generated by the host user if UpdatingUser is null.
See Also
- ProtoFlux:Local Update to generate an impulse from every user on their respective update timers.
- ProtoFlux:Updates Timer to generate an impulse at a specified interval of updates.
- ProtoFlux:Seconds Timer to generate an impulse at a specified interval of seconds.