#Dwarf fortress dfhack commands install#
#Dwarf fortress dfhack commands archive#
#Dwarf fortress dfhack commands upgrade#
#Dwarf fortress dfhack commands code#

#Dwarf fortress dfhack commands upgrade#

Could drop the plugin, upgrade modtools and use it as a backend for the gui (with script environment or similar) forceequip plugin is mostly replaced by modtools equip item fastdwarf, teledwarf, superdwarf needs sorting out somehow. in an old fortress, this can significantly reduce fps lag. cleans all the splatter that get scattered all over the map, items and creatures. This command fixes crashes caused by previous versions of workflow, mostly in dfhack 0.40.24 r4, and should be run automatically when loading a world (but can also be run manually if desired). define the dfhack enable luacov=1 environment variable to start gathering coverage metrics.

#Dwarf fortress dfhack commands code#

clear webs: removes all webs on the map and or frees any webbed creatures devel block borders: overlay that displays map block borders devel luacov: generate code test coverage reports for script development. Internals ruby library now included on os x ruby scripts should work on os x 10.10 libstdc should work with older versions of os x added support for onloadmap onunloadmap.init scripts game type detection functions are now available in the world module the dfhack log mem ranges environment variable can be used to log information to stderr.log on os x fixed adventure mode menu names fixed.ĭfhack Scripts Dfhack 0 40 24 R3 Documentationĭfhack 0.47.05 r2 new scripts. dfhack.script environment(name) run an lua script and return its environment. note that this function lets errors propagate to the caller. the name argument should be the name stem, as would be used on the command line. n script(name) run a lua script in hack scripts, as if it was started from dfhack command line. for developers, dfhack unites the various ways tools access df memory and allows easier development of new tools. Non standard dfhack scripts and inits can be stored in the raw directory, making raws or saves fully self contained for distribution or for coexistence in a single df install, even with incompatible components. on windows, first delete sdl.dll and rename sdlreal.dll to sdl.dll, then remove the other dfhack files.

#Dwarf fortress dfhack commands archive#

copy the files from a release archive so that: on linux or osx, the dfhack script is placed in the same folder as the df script. Installing dfhack involves copying files into your df folder. note: scripts in subdirectories of hack scripts can still be called, but will only be listed by ls if called as ls a. they are listed at the end of the ls command output. lua or ruby scripts placed in the hack scripts directory are considered for execution as if they were native dfhack commands. I'm glossing over a lot of details, of course, but this is the general idea.Dfhack scripts ¶. The configuration UI can be brought up at any time during gameplay with the tilde (~) hotkey to check status or to make modifications. You can also save the configuration as a profile so you can quickly apply it to another fort, and a profile can be automatically applied to new forts without invoking the configuration UI, if you so desire. The configuration you set in this dialog is persistent for your fort, so you don't need to reapply your settings when you save and reload. Help text is shown for the currently selected tool so you can see what it does. anything that can be 'enabled' for some sort of persistent effect). autofarm, autochop, autobutcher, prioritize, UI tweaks, bug fixes. When the fort is loaded for the first time, a DFHack configuration screen comes up where you can see the status of and enable/disable DFHack tools (e.g.

#Dwarf fortress dfhack commands install#

This is the vision, starting from a fresh, unmodified install of DFHack and a brand new embark:

The idea is just to make it possible to configure everything from the GUI and never have to open a text editor at all. People who prefer to use init files can continue to do so. To be clear, the current method of configuring DFHack from init files isn't going away. Today, let me go over the first one a little: configuring DFHack from the GUI.

We're putting together proposals to address each one of those points. See better help text/tutorials for complex DFHack functionality

Get help while running DFHack commands from the GUI You told us what you wanted, and we listened! Based on the survey results (thank you again for your responses!), DFHack users want to: