DFHack’s mission is to provide tools and interfaces for players and modders to:
- expand the bounds of what is possible in Dwarf Fortress
- reduce the impact of game bugs
- give the player more agency and control over the game
- provide alternatives to toilsome or frustrating aspects of gameplay
- make the game more fun
The best way to make feature requests or report problems is to open an Issue at our GitHub page.
When reporting problems, links to your zipped, uploaded savegame and mods are immensely helpful, and issues with attached savegames and mods get fixed faster. We need a zip of your mods because we can't load your savegame without them.
DFHack installs directly into your Dwarf Fortress directory, so be sure to install it to the same Steam library and drive as Dwarf Fortress.
It is not a problem if you already have DFHack manually installed. You can subscribe to the Steam version and it will absorb the installed files. Your data in dfhack-config/ is safe. No additional steps are necessary.
Highlights
Hotfix to DFHack 52.03-r1
This is a hotfix release to fix an alignment error that was breaking several tools, including the building planner and the trade interface, and also to fix an issue with job names appearing incorrectly for dye-related jobs.
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.\n\nSome 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\".\n\nThe 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.\n\nIf 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
Fixes
job descriptions of mix dye job will display proper dye names
[/*]
Structures
fixed alignment issue in entity_raw
[/*]
Minimum Setup
- Processor: Dual Core CPU - 2.4GHz+Memory: 4 GB RAM
- Memory: 4 GB RAM
- Graphics: 1GB of VRAM: Intel HD 3000 GPU / AMD HD 5450 / Nvidia 9400 GT
- Storage: 50 MB available spaceAdditional Notes: Must be installed to the same Steam library and drive as Dwarf Fortress
Recommended Setup
- Processor: Dual Core CPU - 4GHz+Memory: 16 GB RAM
[ 6176 ]
[ 5746 ]
[ 1265 ]
[ 2018 ]
[ 986 ]















