Uploaded April 2026 | Updated November 2026, 1 day ago
Script for Doom engine games by feos and kalimag.
Latest Bizhawk build: nightly.link/TASEmulators/BizHawk/workflows/ci/master/BizHawk-dev-windows.zip
How to use the Doom core in Bizhawk: tasvideos.org/Bizhawk/Doom
DW thread: doomworld.com/forum/topic/155256-doom-core-in-bizhawk-dsda-doom
Shows player info. If you have several players in-game you can hover on player info and scroll the mouse wheel to show info for different players.
Shows current tic, in-game time, and RNG index along with value at that index.
Shows Automap consisting of linedefs, sectors, and things (toggled via the 'Map' button).
Shows blockmap grid (toggled via the 'Grid' button).
The 'Reset View' button zooms and pans the automap to make all things visible.
The 'Follow' button makes the camera stick to the player that is currently selected on the left panel.
The 'Hilite' buttons enables highlight/selection mode where you can hover on sectors, linedefs, and things to see their info on the left, in corresponding colors.
Use Mouse Wheel to zoom in and out, and mouse movement with the 'Space' key held down to pan.
Buttons for adding things, lines, and sectors allow to track those entities. If more than one object of a given type is tracked, you can hoven on them and scroll through them with the mouse wheel. They can also be removed from the tracked list by hitting the red cross button that appears on hover.
Tracked and highlighted entities show info similar to what XDRE shows. For linedefs, distance from the currently selected player is shown in 2 ways: "distance from line" is similar to that in XDRE, when the line is assumed to be infinite and player position is projected onto it at a right angle. "Distance from segment" assumes line to be finite and only calculates distance to the closest point of that segment regardless of the angle.
Tracked entity lists and Automap config are saved when the script is stopped or restarted or when you add or remove tracked entities. To manually edit the config file, disable the script, edit the 'doom.settings.lua' file if it exists, then start the script again. Editing it while the script is running will overwrite your edits later. Config also stored Angle type which has no other way to change it.
You can log which thing has used or crossed linedefs, with options being None, Player, and All
You can log various info every time a P_Random() call happens with a class that changes the RNG value. Log prints tic count when the call happened, which call it is per that tic, the RNG index, the value at that index, and the call stack (while file and line called P_Random() within which function).
You can display intercepts on the Automap: tracelines and blockmap blocks where intercepts happen. Red color means an intercept happened on this tic, then the color fades to grey.
And the most complicated feature is intercept logging. It will inform you when the intercept count exceeded a user-defined limit, which is 128 by default but can be changed in config (the 'InterceptLimit' value). If the intercept count exceeded that value, a button will appear that will print info on all the intercepts, as well as info on all the vanilla addresses they corrupted, if any. Boom fixed intercept overflow, so in Boom complevel this feature is disabled.
Script for Doom engine games by feos and kalimag.
Latest Bizhawk build: nightly.link/TASEmulators/BizHawk/workflows/ci/master/BizHawk-dev-windows.zip
How to use the Doom core in Bizhawk: tasvideos.org/Bizhawk/Doom
DW thread: doomworld.com/forum/topic/155256-doom-core-in-bizhawk-dsda-doom
Shows player info. If you have several players in-game you can hover on player info and scroll the mouse wheel to show info for different players.
Shows current tic, in-game time, and RNG index along with value at that index.
Shows Automap consisting of linedefs, sectors, and things (toggled via the 'Map' button).
Shows blockmap grid (toggled via the 'Grid' button).
The 'Reset View' button zooms and pans the automap to make all things visible.
The 'Follow' button makes the camera stick to the player that is currently selected on the left panel.
The 'Hilite' buttons enables highlight/selection mode where you can hover on sectors, linedefs, and things to see their info on the left, in corresponding colors.
Use Mouse Wheel to zoom in and out, and mouse movement with the 'Space' key held down to pan.
Buttons for adding things, lines, and sectors allow to track those entities. If more than one object of a given type is tracked, you can hoven on them and scroll through them with the mouse wheel. They can also be removed from the tracked list by hitting the red cross button that appears on hover.
Tracked and highlighted entities show info similar to what XDRE shows. For linedefs, distance from the currently selected player is shown in 2 ways: "distance from line" is similar to that in XDRE, when the line is assumed to be infinite and player position is projected onto it at a right angle. "Distance from segment" assumes line to be finite and only calculates distance to the closest point of that segment regardless of the angle.
Tracked entity lists and Automap config are saved when the script is stopped or restarted or when you add or remove tracked entities. To manually edit the config file, disable the script, edit the 'doom.settings.lua' file if it exists, then start the script again. Editing it while the script is running will overwrite your edits later. Config also stored Angle type which has no other way to change it.
You can log which thing has used or crossed linedefs, with options being None, Player, and All
You can log various info every time a P_Random() call happens with a class that changes the RNG value. Log prints tic count when the call happened, which call it is per that tic, the RNG index, the value at that index, and the call stack (while file and line called P_Random() within which function).
You can display intercepts on the Automap: tracelines and blockmap blocks where intercepts happen. Red color means an intercept happened on this tic, then the color fades to grey.
And the most complicated feature is intercept logging. It will inform you when the intercept count exceeded a user-defined limit, which is 128 by default but can be changed in config (the 'InterceptLimit' value). If the intercept count exceeded that value, a button will appear that will print info on all the intercepts, as well as info on all the vanilla addresses they corrupted, if any. Boom fixed intercept overflow, so in Boom complevel this feature is disabled.










