Print

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

[scourge728]

Is there any way to disable the thing when you're selecting materials to build things and it automatically pulls up the one you used last?

[Bumber]

Is there any way to disable the thing when you're selecting materials to build things and it automatically pulls up the one you used last?

Remove the line "enable automaterial" from dfhack.init.

[scourge728]

Is there any way to disable the thing when you're selecting materials to build things and it automatically pulls up the one you used last?

Remove the line "enable automaterial" from dfhack.init.

So, can I just copy the contents of the example into a file named dfhack.init in order to create one or...?

Also, remove-wear isn't working for me, I don't get any errors, but nothing is happening, adding -all to it does nothing as well... is it borked in the 44.11 alpha?

[Putnam]

Or rename init-example, as I'm pretty sure it suggests.

[lethosor]

Is there any way to disable the thing when you're selecting materials to build things and it automatically pulls up the one you used last?

Remove the line "enable automaterial" from dfhack.init.

So, can I just copy the contents of the example into a file named dfhack.init in order to create one or...?

Or remove the line "enable automaterial" from whatever file it's in...

Also, remove-wear isn't working for me, I don't get any errors, but nothing is happening, adding -all to it does nothing as well... is it borked in the 44.11 alpha?

From checking the docs, it takes "all", not "-all".

[scourge728]

Well look at that, it DOES work when you use "all", it's confusing, since some commands accept "all" some accept "-all" 

[lethosor]

Upon closer investigation, that script is utter trash. I fixed it so that (a) it's actually readable, (b) it follows sane coding conventions, (c) it's significantly faster with large numbers of items, (d) it produces error messages when you give it bad arguments, instead of silently failing, and (e) it accepts "-all" as well. You can find the fixed version at https://github.com/DFHack/scripts/blob/master/remove-wear.lua

Just want to double-check - was that the only issue you were having with remove-wear? (Or were there issues with passing it individual item IDs?) In any case, issues with it probably aren't 0.44.11-specific, but do feel free to report other weirdness with scripts that you encounter.

[scourge728]

That was in fact the only issue I was having

[Jazz Cat]

Just letting you know, the link on the first post of this thread that says "Alpha 44.11 alpha-1" leads to the the 44.10 alpha-1 release.

[lethosor]

Thanks, fixed (I remembered most of them, just not the link...)

[Rumrusher]

hmm I probably should look into finding out how to give labors to units who end up with the "No labors available" screen

edit: oh it seems there's no unit_flags1.dead flag in this alpha
edit: or got a name changed to inactive?

[Clément]

"dead" has been renamed "inactive" since 0.44.10-r2.

[PatrikLundell]

hmm I probably should look into finding out how to give labors to units who end up with the "No labors available" screen

edit: oh it seems there's no unit_flags1.dead flag in this alpha

"dead" has been renamed "inactive" since 0.44.10-r2.

And the reason for that is that flags2.killed is the one that tells if a unit is dead. All killed units are inactive, but all inactive units are not killed (e.g. inbound/outbound). Also consider whether you actually need to access the flags directly, or can use the Units.isKilled/.isActive/.isMerchant etc. functions instead.

[Rumrusher]

oh hmm I probably should have refresh the page before editing the post. oh well this means modifying my heal scripts to fit the new changes then.

[Saiko Kila]

I have a problem with function dfhack.units.getVisibleName() in lua script.

When I want the script to show real name, I use simply

Code: [Select]

string.gsub(unit.first_name,"^%l",string.upper)
When I wanted to show fake name, I tried this:

Code: [Select]

string.gsub(dfhack.units.getVisibleName(unit).first_name,"^%l",string.upper)
However, the last code still shows the same real first name as the first one (and thus reveals an identity of a vampire). According to description the function  should show the fake name, right? So why would it show the real one?

And the reason for that is that flags2.killed is the one that tells if a unit is dead. All killed units are inactive, but all inactive units are not killed (e.g. inbound/outbound). Also consider whether you actually need to access the flags directly, or can use the Units.isKilled/.isActive/.isMerchant etc. functions instead.

After the rename I just changed the names of flags in my scripts from "flags1.dead " to "flags1[1]", so they will work with both names under different dfhacks. Problems with functions is that you need to test them first, because they are not always working as expected. Using a flag is quicker and less stressful, if you know what it's supposed to do.