Steam News 12 January 20264mo ago

DFHack 53.10-r1

Highlights Compatibility with DF 53.10 This release provides compatibility with Dwarf Fortress 53.10. Bug fixes This release fixes a bug in `suspendmanager` that caused its overlay to appear at inappropriate times, and…

Update log

Full DFHack - Dwarf Fortress Modding Engine update

The complete published notes, normalized for clean reading and source attribution.

Extracted changes

1 fix5 additions1 change1 removal

Compatibility
Fixes
Gameplay
Workshop

changedCompatibility with DF 53.10This release provides compatibility with Dwarf Fortress 53.10.

fixedBug fixesThis release fixes a bug in `suspendmanager` that caused its overlay to appear at inappropriate times, and also fixed a bug in `autochop` that prevented it from reporting its own status.

addedNemesis record validation checkerThe DFHack team has noticed in recent months that many players have saves that have damaged nemesis records. Saves with damaged nemesis records often experience a wide range of misbehaviors. This release has a new feature that will periodically check that every unit in the fort that should have a nemesis record has one, and verify that it's the correct one. If a unit that should have a nemesis record does not have the correct nemesis record, a diagnostic warning will be displayed. If you get this message, we suggest that you contact Bay12 and offer to provide your save to them for debugging purposes.

addedPSAsAs always, remember that, just like the vanilla DF game, DFHack tools can also have bugs. It is a good idea to save often and keep backups of the forts that you care about. Some DFHack tools that worked in previous (pre-Steam) versions of DF have not been updated yet and are marked with the "unavailable" tag in their docs. If you try to run them, they will show a warning and exit immediately. You can run the command again to override the warning (though of course the tools may not work). We make no guarantees of reliability for the tools that are marked as "unavailable". The in-game interface for running DFHack commands ( gui/launcher ) will not show "unavailable" tools by default. You can still run them if you know their names, or you can turn on dev mode by hitting Ctrl-D while in gui/launcher and they will be added to the autocomplete list. Some tools listed as "unavailable" in the docs do not compile yet and are not accessible at all, even when in dev mode. If you see a tool complaining about the lack of a cursor, know that it's referring to the keyboard cursor (which used to be the only real option in Dwarf Fortress). You can enable the keyboard cursor by entering mining mode or selecting the dump/forbid tool and hitting Alt-K (the DFHack keybinding for toggle-kbd-cursor ). We're working on making DFHack tools more mouse-aware and accessible so this step isn't necessary in the future.

addedNew Features[c]gui/notify[/c]: new notification type: missing nemesis records; displays a warning message about game corruption.

removedFixes[c]autochop[/c]: the report will no longer throw a C++ exception when burrows are defined.

Highlights

Compatibility with DF 53.10

This release provides compatibility with Dwarf Fortress 53.10.

Bug fixes

This release fixes a bug in `suspendmanager` that caused its overlay to appear at inappropriate times, and also fixed a bug in `autochop` that prevented it from reporting its own status.

Nemesis record validation checker

The DFHack team has noticed in recent months that many players have saves that have damaged nemesis records. Saves with damaged nemesis records often experience a wide range of misbehaviors. This release has a new feature that will periodically check that every unit in the fort that should have a nemesis record has one, and verify that it's the correct one. If a unit that should have a nemesis record does not have the correct nemesis record, a diagnostic warning will be displayed. If you get this message, we suggest that you contact Bay12 and offer to provide your save to them for debugging purposes.

Announcements

PSAs

As always, remember that, just like the vanilla DF game, DFHack tools can also have bugs. It is a good idea to save often and keep backups of the forts that you care about. Some DFHack tools that worked in previous (pre-Steam) versions of DF have not been updated yet and are marked with the "unavailable" tag in their docs. If you try to run them, they will show a warning and exit immediately. You can run the command again to override the warning (though of course the tools may not work). We make no guarantees of reliability for the tools that are marked as "unavailable". The in-game interface for running DFHack commands ( gui/launcher ) will not show "unavailable" tools by default. You can still run them if you know their names, or you can turn on dev mode by hitting Ctrl-D while in gui/launcher and they will be added to the autocomplete list. Some tools listed as "unavailable" in the docs do not compile yet and are not accessible at all, even when in dev mode. If you see a tool complaining about the lack of a cursor, know that it's referring to the keyboard cursor (which used to be the only real option in Dwarf Fortress). You can enable the keyboard cursor by entering mining mode or selecting the dump/forbid tool and hitting Alt-K (the DFHack keybinding for toggle-kbd-cursor ). We're working on making DFHack tools more mouse-aware and accessible so this step isn't necessary in the future.

Changelog

New Features

[c]gui/notify[/c]new notification type: missing nemesis records; displays a warning message about game corruption.

Fixes

[c]autochop[/c]: the report will no longer throw a C++ exception when burrows are defined.
[c]suspendmanager[/c]: Fix the overlay appearing where it should not when following a unit

API

Added [c]Burrows::getName[/c]: obtains the name of a burrow, or the same placeholder name that DF would show if the burrow is unnamed.

Lua

Added [c]Burrows::getName[/c] as [c]dfhack.burrows.getName[/c].

Source

Steam News / 12 January 2026

Open original