DFHack 53.11-r1
[p]Please report any issues (or feature requests) on the DFHack GitHub issue tracker. When reporting issues, please upload a zip file of your savegame and a zip file of your [c]mods[/c] directory to the cloud and add links to the GitHub issue. Make sure your files are downloadable by "everyone with the link". We need your savegame to reproduce the problem and test the fix, and we need your active mods so we can load your savegame. Issues with savegames and mods attached get fixed first![/p][h2]Highlights[/h2][h3]Dwarf Fortress 53.11 compatibility[/h3][p]This release is primarily for compatibility with Dwarf Fortress 53.11.[/p][h3]One bug fix[/h3][p]We fixed one bug in 53.10-r2 in this release; the "hates combat" filter on the squad selection filter will now work correctly.[/p][h2]Announcements[/h2][h3]Known defect[/h3][p]53.10-r2 has a reported defect in the "rename" tool which we have not had time to fix; this release also has this defect. We are working to find and fix this bug and will release an update as soon as we can once we've got a fix.[/p][h3]Issues with Steam Client Beta[/h3][p]The beta of the Steam client alters the way Steam applications are deployed in a way that impacts DFHack, and we have had reports of DFHack not working as expected for people who are using the Steam beta client. We are aware of this issue, have a plan to mitigate it in development, and hope to have a solution in place before the change Steam is making makes it to the release client.[/p][h3]PSAs[/h3][p]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.[/p][p]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".[/p][p]The in-game interface for running DFHack commands ([c]gui/launcher[/c]) 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 [c]gui/launcher[/c] 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.[/p][p]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 [c]toggle-kbd-cursor[/c]). We're working on making DFHack tools more mouse-aware and accessible so this step isn't necessary in the future.[/p][h2]Changelog[/h2][h3]Fixes[/h3]
- [p][c]sort[/c]: correct misspelling of [c]PERSEVERENCE[/c]; fixes "hates combat" filter in squad selection screen[/p]
- [p]added codegen support for [c]static-wstring[/c] ([c]wchar_t
- [/c]), required to support DF 53.11[/p]