Old network messages move players backwards after a while
Messages can arrive in the wrong order or twice, and the numbers used to put them in order eventually run out and start again from zero. A naive comparison then treats brand new news as ancient, and players start moving backwards after an hour of play. Here is the comparison that survives the restart.
Why this works
A short counter has to start over, and then the biggest number is suddenly the oldest. Asking which is ahead by counting forward from one to the other, within half the range, stays right across the restart, which a plain bigger-than test cannot.
When not to use it
Not needed if messages come over a channel that already keeps order and loses nothing, or if each message carries the full picture and only the newest matters. Then just keep the latest by its time stamp and ignore the rest.
In the full entry
- What to build, step by step
- Starting values and the reason for each
- 3 common mistakes and the fix
- 26 lines of example code with 4 checks that pass
- How your AI shows you that it works
Say this to your AI
Use the Spielerando entry "Old network messages move players backwards after a while" (read_entry online-order-news-with-wrapping-numbers) in my game. Build it step by step, and show me how you checked that it works.Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP