Bay 12 Games Forum

This looks like it would be really useful for modders who are doing graphics replacement to verify that all their changes look correct for each creature.

DFHack 50.11-r2 released!

Full support for all DF 50.11 releases.

Highlights: Search! Search! Search!, Preserve tomb assignments, Collapse all for stocks screen, Automatic tomb zones, Stranded citizen alert

Get it from:

• GitHub: https://github.com/DFHack/dfhack/releases/tag/50.11-r2
• Steam: https://store.steampowered.com/app/2346660/DFHack

Full installation instructions: https://docs.dfhack.org/en/latest/docs/Installing.html

DFHack 50.11-r2rc1 released!

Full support for all 50.11 releases. Highlight: Search! Search! Search!

Get it from:

• GitHub: https://github.com/DFHack/dfhack/releases/tag/50.11-r2rc1
• Steam: https://store.steampowered.com/app/2346660/DFHack (beta branch)

Full installation instructions: https://docs.dfhack.org/en/latest/docs/Installing.html

EDIT: Ah goddamit, I'm probably looking at upgrading my distro to the next major version. Because apparently manually forcing an update to glibc is a sure-fire way to experience Fun in the DF sense of the word on Linux.

It's not that old, DF should have been built using an older version.

Yeah, we're working with Bay 12 to standardize on a more widely compatible build environment. It's not as easy as just switching build systems, though, since DF actually *uses* functionality only available in more recent versions of glibc and the c++ standard library.

I had trouble with running a modtools command. Can you apply one in the tutorial?

any script can be run with the dfhack.run_script() command, modtools or otherwise (see https://docs.dfhack.org/en/latest/docs/dev/Lua%20API.html#general-script-api). Which one were you having trouble running? Does the script have the "unavailable" tag (https://docs.dfhack.org/en/stable/unavailable-tag-index.html#cap-m )? If so, it hasn't been updated yet and you can't expect it to work.

I missed the definition of the variable modId in the final example.

It's just a string that's set to the name of your mod. There are a few examples of the variable being set in the modding guide. Ctrl-F for "modid".

de mod deactivates by closing the game, but doesnt reactivatie. Id like to have my script always active, if my main mod is loaded .

This is what the onStateChange handler is for in https://docs.dfhack.org/en/stable/docs/guides/modding-guide.html#putting-it-all-together
There's more information about this mechanism here: https://docs.dfhack.org/en/latest/docs/dev/Lua%20API.html#enabling-and-disabling-scripts

Here's a Lua script that will empty bars out of bins:
local count = 0
for _, item in ipairs(df.global.world.items.other.BAR) do
    if not item.flags.in_inventory then goto continue end
    local gref = dfhack.items.getGeneralRef(item, df.general_ref_type.CONTAINED_IN_ITEM)
    if not gref then goto continue end
    local bin = df.item.find(gref.item_id)
    if not bin or not df.item_binst:is_instance(bin) then goto continue end
    if dfhack.items.moveToGround(item, bin.pos) then count = count + 1 end
    ::continue::
end
print(('dumped %d bar(s) out of bins'):format(count))
If you save that into a file named dfhack-config/scripts/barbin.lua, you can run it by running barbin in the DFHack command launcher.

And "A dwarf's got an idea!"

Welcome back! Yes, we have carefully kept the Lua API docs up to date. The largest changes have been in the gui and gui.widgets namespaces. The bulk of the C++ module APIs have stayed largely the same. Plugins, on the other hand, have seen a lot of changes, and not all of them have been updated for v50 yet.