BizHawk Git Snapshot Released With Multi-System TAS Emulator Updates
BizHawk's March 19 git snapshot patched two Doom Lua scripting bugs and pulled in a fresh bsnes upstream update across its sprawling multi-system TAS toolkit.

The TAS community's go-to multi-system emulator picked up a fresh git snapshot on March 19, 2026, with four targeted fixes touching Doom Lua scripting, the bsnes core, and the dsda engine.
BizHawk is written primarily in C# and built specifically around rerecording and debugging workflows, making it the standard tool for tool-assisted speedrun work across a wide range of platforms: Apple II, Atari 2600, Commodore Amiga, NES, Game Boy, N64, Sega Genesis, Sega Saturn, and more. Beyond the TAS tooling, it covers the basics with full-screen mode and joypad support for more casual use.
The March 19 changelog is short but specific. Two entries target Doom Lua directly: "doom lua: include overruns dumping" and "doom lua: resolve intercept log issues." If you've been hitting inconsistencies in Lua scripting sessions against Doom-engine content, both of those are worth noting. The third entry, "bsnes: updated from upstream," pulls in the latest changes from the bsnes project into BizHawk's SNES core. The fourth entry, "dsda: corrected playerstarts corruption with intercepts overflow," addresses a data corruption bug in dsda that could corrupt player start positions when intercepts overflowed, a subtle but potentially run-breaking issue for anyone TASing through that engine path.

No commit hashes or upstream bsnes reference IDs accompanied the reported changelog, so if you need to trace exactly what changed in the bsnes pull, checking the BizHawk repository's March 19 commit history directly is the way to go.
The compiled build for this snapshot is available alongside the source, with download and source links listed on the release post. The tag set on the release includes GBA, N64, NES, PSP, SMS, SNES, and SS alongside the BizHawk and Multi labels, confirming the breadth of cores this build touches even when a given changelog is focused on a narrow set of fixes.
Know something we missed? Have a correction or additional information?
Submit a Tip

