ProtoFlux:Update: Difference between revisions

From Resonite Wiki
clear up misinformation and generally fill in
m nullabl
 
Line 27: Line 27:
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.


=== SkipIfNull ([[Type:bool|bool]]) ===
=== SkipIfNull ([[Type:Nullable`1|Nullable]]&lt;[[Type:bool|bool]]&gt;) ===


If <code>True</code>, no pulses will be generated if <code>UpdatingUser</code> is null. Otherwise, impulses will be generated by the [[ProtoFlux:Host User|host user]] if <code>UpdatingUser</code> is null.
If <code>True</code>, no pulses will be generated if <code>UpdatingUser</code> is null. Otherwise, impulses will be generated by the [[ProtoFlux:Host User|host user]] if <code>UpdatingUser</code> is null.

Latest revision as of 21:00, 24 December 2024

Update
OnUpdate
UpdatingUser
null
SkipIfNull
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.

SkipIfNull (Nullable<bool>)

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