Fix the max-prefix freeze at rival exchanges and keep the loop alive

The max-prefix incident looked up an exchange id as a city, the same
bug as #24. Both messages now name the exchange and its city.

frame() now schedules the next frame first and catches a failing day
tick or draw, so one bad lookup shows a warning instead of freezing the
game.
This commit is contained in:
Frederic Jung 2026-10-24 21:02:08 +02:00
parent 16e1f95d1b
commit 988e0c5d15
No known key found for this signature in database
3 changed files with 31 additions and 6 deletions

View file

@ -6,6 +6,12 @@ All notable changes to this project are documented here. The project follows
## [Unreleased]
- The game no longer freezes when a peer drops you at a rival exchange
(#24, thanks @daniloctdev), or when a route leak melts down one. The
messages now name the exchange and its city.
- One failing day no longer freezes the whole game: the error is caught,
you get a heads-up, and time keeps running.
## [1.10.0] — 2026-10-24
- Router ports are finite. Every transit, IX, PNI and cache port, every wave