Skip to content

Conversation

@albertok
Copy link
Contributor

@albertok albertok commented Nov 19, 2025

TODO:

  • Docs
  • Version bump
  • Node icon

Closes #374

@albertok albertok marked this pull request as ready for review November 26, 2025 13:13
func _run_prediction_tick(tick: int) -> void:
for node in _nodes:
var is_fresh := _freshness_store.is_fresh(node, tick)
node._predict_tick(NetworkTime.ticktime, tick, is_fresh)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm considering using _rollback_tick() here too.
pros: consistency, code doesn't need to be touched to go from RBS to PredictiveSynchronizer
cons: might be confusing? + might not work well with mixed / nested setups

Thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd much prefer it be called _rollback_tick also but it does leave the door wide open to unintended side effects.

Can I guard against a double call by checking is_simulated maybe?

@elementbound elementbound changed the title PredictiveSynchronizer class feat: PredictiveSynchronizer Dec 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PredictiveSynchronizer

2 participants