1. Pause state needs its ownhandling
Many argue you can’t just stop the clock; you must gate the game loop with an explicit paused flag. > "The best approach would be using something like if(game_is_paused) return; in the game loops." – DeathArrow
2. Deterministic replay depends on pause logic
Accurate pause‑based recordings rely on a deterministic simulation that can be re‑played from inputs.
"Determinism isn’t essential to achieve record/playback experiences..." – bob1029
3. Timer implementation pitfalls
Using absolute timestamps (e.g., UTC) can break when the game pauses; an in‑game monotonic clock is safer.
"It depends on how your timers are implemented... this will cause bugs." – astrobe_
4. UI and rendering stay active while paused
Even when gameplay is paused, the UI and render loop often need to keep running to avoid losing surfaces or missing events.
"You’d still want to at least keep the UI alive, and you also need to continue rendering while the game is paused because the swapchain surfaces might lose their content..." – flohofwoe