CoreTiming: Grow the event table for events a savestate lacks

Taking the highest unused slot instead could steal one that a state event
restores later, as VBlankWake did to MicBlockingResume, which then had
nowhere to go. Also name the event in the assert.

AGENTS.md: When a savestate fails to load, suspect the branch first.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This commit is contained in:
Henrik RydgårdandClaude Opus 5.5 committed 2026-09-30 09:06:30 -06:00
1 parent d86896bed9
commit 54e4be47aa
2 files changed
+8 -9

No files matched your search

+4
View File
@@ -108,6 +108,10 @@ $msbuild = "$installPath\MSBuild\Current\Bin\MSBuild.exe"
- **A stale binary lies consistently.** After a `git stash` cycle that touched a header, do a
`/t:Rebuild`; when bisecting a behavioural change, confirm the binary actually changed before you
believe the result.
- **If a savestate fails to load, first suspect the branch, not the loader.** Either your branch is
behind the build that made the state (rebase it on `origin/master` and rebuild), or the state was
made on a branch that hasn't been merged yet. Only once you've ruled out both is it a savestate
compatibility bug.
UWP, the legacy Android NDK build and the libretro core have their own build systems.