Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Rumrusher]

Hello everyone! Was wondering if there are any plans to add classic keyboard support and keybinds to the .50 version of the game? Really missing those old keybinds.

so I went and made a DF50 keyboard cursor script that just a modified version of a different gui liquids script that display an x where the in game cursor is currently placed.

[myk]

DFHack 50.11-r3 released!

Highlights: Selection dimension indicator, Choose mechanisms for linking, Burrows!

Get it from:

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

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

[joostheger]

What do I do when I have found out information, that is currently not in df-structurers?
Or when I have a suggestion for a script-improvement?

Well, it is this: you can kill a unit "by old age". by setting old_age and old_time to any low number. old_age is the age in which the unit dies, and old_time is the time THAT YEAR in which it dies.
So the script 'exterminate' can be updated by a new way of killing people. How nice.

Whats better: this can probably be used to kill off-site units, if you know their unit-id.

[Saiko Kila]

What do I do when I have found out information, that is currently not in df-structurers?
Or when I have a suggestion for a script-improvement?

Well, it is this: you can kill a unit "by old age". by setting old_age and old_time to any low number. old_age is the age in which the unit dies, and old_time is the time THAT YEAR in which it dies.
So the script 'exterminate' can be updated by a new way of killing people. How nice.

Whats better: this can probably be used to kill off-site units, if you know their unit-id.

Units can die of old age before and after the old age time, so it's only approximate. Actually, units practically never die on the exact old age date.

When the new year starts, some of the units with old age in the future also die (especially from the first half of the new year), randomly. And if an unit with old age date in the past is off-screen, it won't die on that date, it will die either after entering the map, or in the beginning of new year. Also, some necromancers have the date set, but of course they won't die, because they are necromancers.

[joostheger]

Well, I let a unit die by setting old_age and old_time on 1, so I'm sure it works.
Maybe the units dieing in the future is because of old_time was negative or something like that. Do you know how those values were related?

[Clément]

What could be causing "Too many failed accepts, shutting down RemoteServer"? It happens when I disconnect/reconnect my client too many times (on Linux, both native and wine, dfhack 50.11-r3 built from sources with extra custom plugins). Although the remote server is disabled, the client connection that caused the error is still working after that (but I cannot make new ones). There is no other error message.

Edit: in "void ServerMainImpl::threadFn(std::promise<bool> promise, int port)", acceptFail counts all accept calls, not only failed ones (commit 0914869). I'm surprised I did not notice this sooner. (reported here)

[myk]

DFHack 50.11-r4 released!

Important bugfixes and QoL improvements.

Get it from:

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

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

[Telgin]

Does anyone know if there's a Lua one-liner to print the agitation level of a fort?  Or are there potentially several map regions?  I've been trying to figure out how to get any of the fort's map data from the Lua interpreter but haven't had much luck.

Also, is there a way to "undiscover" cavern layers with the Lua interpreter?

[0x517A5D]

Does anyone know if there's a Lua one-liner to print the agitation level of a fort?  Or are there potentially several map regions?  I've been trying to figure out how to get any of the fort's map data from the Lua interpreter but haven't had much luck.

This post has a couple of one-liners that print that info.

[Quietust]

Also, is there a way to "undiscover" cavern layers with the Lua interpreter?

If you want to mark a map feature as "not discovered", there's already a script for that - run "feature list" to see which ones are there, then "feature hide N" to undiscover the one you don't want.

Though, it's possible that digging around that feature might cause it to get rediscovered, so you might need to re-disable it again from time to time.

[Telgin]

Perfect, thanks both of you.

Yeah, for the caverns, I accidentally caused a cave-in while digging an open pit mine that collapsed and punched through to the caverns.  I wanted to avoid them entirely so I think undiscovering it once should help.

Edit: I hid the feature, but I see I'm still getting visitors who want to slay monsters.  Is there another flag I have to toggle to stop that?

The cavern is still visible too, which is fine, but I guess that's also controlled by other map data.

[A_Curious_Cat]

So... I'm getting back into the game (now that I've figured out how to exit Steam without it leaving behind zombie processes), and I'm trying to set up autochop so that it excludes trees with products that are brewable, edible, and/or cookable.

I tried first by running gui/autochop, but there apparently weren't any options to exclude trees based on their products.  after searching the DFHack manual, I decided to try using autochop from the command line...

And I got this:



Any help?

[Madde]

I'm sorry in advance if this is not the right place to post this as I'm still using the 47.05 version of DF and DFhack, but I just can't seem to get item-trigger working at all.

I tried it with these two lines in onMapLoad.init:
modtools/item-trigger -itemType ITEM_WEAPON_SABRE -onEquip -command [ modtools/add-syndrome -syndrome "test syndrome" -resetPolicy ResetDuration -target \\UNIT_ID ]
modtools/item-trigger -itemType ITEM_WEAPON_SABRE -onUnequip -command [ modtools/add-syndrome -syndrome "test syndrome" -erase -target \\UNIT_ID ]

... but despite everything looking alright the game just crashes or closes to desktop during the loading screen.
It even happens if I just type in modtools/item-trigger and no further arguments, other commands seem to work fine.

[myk]

Edit: I hid the feature, but I see I'm still getting visitors who want to slay monsters.  Is there another flag I have to toggle to stop that?

The cavern is still visible too, which is fine, but I guess that's also controlled by other map data.

If the cavern is blocked off with natural walls, you could use revflood to hide them, but that won't work with constructed walls (by design). If you use tiletypes to add in natural walls, though, you could use revflood to hide the caverns again. That *might* help with the monster slayers, but I'm not sure.

I tried first by running gui/autochop, but there apparently weren't any options to exclude trees based on their products.

There is no global setting for protecting those types of trees. You have to define a burrow and set the protections on the burrow. This is true for the commandline as well. The error message you're seeing should obviously be better phrased, but the issue is that the command you ran has a syntax error. The syntax is:

autochop (protect|unprotect) <type>[,<type>...] <burrow>[,<burrow>...]

and you're missing the burrow specification at the end.

It even happens if I just type in modtools/item-trigger and no further arguments

modtools/item-trigger enables some EventManager events when it is run. My guess is that there is a crash bug in EventManager for one of those event types. What are you trying to build? This may be worth releasing a new 47.05 version of DFHack for.

[Madde]

modtools/item-trigger enables some EventManager events when it is run. My guess is that there is a crash bug in EventManager for one of those event types. What are you trying to build? This may be worth releasing a new 47.05 version of DFHack for.

I tried with a few older versions of DFhack, 47.05 r8 and r5 crashes when an item-trigger script is run, while r2 seems to work fine.
I didn't test r3 and r4 yet, as r2 seems to suffice for the few scripts that I need.

As for what I'm trying to make, I have been working on a Bloodborne and Darkest Dungeon inspired conversion mod for quite a while now, and I'll probably make use of the item-trigger and reaction-trigger scripts here and there to bring some variety into fort mode and adv mode gameplay.
One such thing would be the Moonlight Basin, a workshop where infused wax idols could be used to summon various ethereal creatures depending on the current phase of the moon.
I've already tried it with the boiling rock syndrome method and it seems to work, but I think using DFhack to more consistently grant the syndrome and make the building OUTSIDE_ONLY would be great.