@@ -131,17 +131,19 @@ These methods are called by [RollbackSynchronizer] under the hood.
131131
132132## Input Submission Status
133133
134- In certain scenarios you may wish to delay commiting to something hard to reverse
135- like death, vfx or audio untill its known for sure the outcome won't change. One
136- way of doing this is to check which nodes have submited input and are past a
137- point of rollback.
138-
139- You can query the status of Nodes with ` NetworkRollback.get_latest_input_tick(root_node) `
140- or ` NetworkRollback.has_input_for_tick(root_node, tick) ` . ` root_node ` being what
141- the relevant [ RollbackSynchronizer] has configured.
142-
143- All tracked nodes can be retreived from ` NetworkRollback.get_input_submissions() `
144- which will return the entire <root_node, latest_tick> dictionary.
134+ In certain scenarios you may wish to delay committing to something hard to
135+ reverse like death, VFX or audio until its known for sure the outcome won't
136+ change. One way of doing this is to check which nodes have submitted input and
137+ are past a point of rollback.
138+
139+ You can query the status of Nodes with
140+ ` NetworkRollback.get_latest_input_tick(root_node) ` or
141+ ` NetworkRollback.has_input_for_tick(root_node, tick) ` . ` root_node ` being what
142+ the relevant [ RollbackSynchronizer] has configured.
143+
144+ All tracked nodes can be retrieved from
145+ ` NetworkRollback.get_input_submissions() ` which will return the entire
146+ ` <root_node, latest_tick> ` dictionary.
145147
146148## Settings
147149
0 commit comments