-
-
Notifications
You must be signed in to change notification settings - Fork 43
Open
Labels
featureNew feature or requestNew feature or request
Description
✨ Description
Have a way to know which ticks are confirmed, as in known not to change. This could mean that e.g. the tick is past the history limit so it definitely won't be resimulated, or that all the inputs are known for that tick so there's no reason to resimulate that tick.
Use case
Game mechanics where cancelling an action would be suboptimal, e.g. player death. In this case, the player being despawned and suddenly thrown back into the game is jarring. Instead, the player could be incapacitated but still recording inputs, and once the server confirms death, the player is despawned.
Distribution
netfox core
Notes
- The base API could be a simple bool somewhere, with higher-level primitives optionally built on top of it, like Futures
- Make sure to consider partial inputs - e.g. one RBS is controlled by multiple players
- Also consider cases where a single player can control multiple RBS'
- Kudos @albertok for suggesting this!
Metadata
Metadata
Assignees
Labels
featureNew feature or requestNew feature or request