✨ Description

There are objects that need to participate in the rollback loop, but are not controlled by any input - e.g. moving platforms, interactive objects like doors, etc.

In addition to lacking input, these also depend fully on known state, so there's no point in synchronizing them.

Implementation

Introduce a PredictiveSynchronizer node. It would have a state configured the same way as in RollbackSynchronizer, but no input, nor synchronization-related properties.

It would gather all nodes implementing the _predict_tick() method and run them as part of the rollback loop.

Distribution

netfox core

Notes

• ❓ Should there be optional state synchronization?
• Preferably implemented after HistoryBuffer in Refactor RollbackSynchronizer #358 so it can be reused