Print

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

[expwnent]

If you don't use PRESERVE_ROCK that won't be a problem. It deletes the rock by default to prevent that.

I'll play around with it when I get a chance and see what's happening.

In the mean time, you can get rid of all the SYN_INJECTED, SYN_INHALED, SYN_CONTACT stuff. You don't need it. The plugin doesn't even check for it.

[Gahagan]

I'm having trouble getting the tweak subcommands to work, things like military-training and stable-temp. I'm entering "tweak stable-temp" for example, and it's just telling me how I'm supposed to use the tweak command. What am I doing wrong?

I'm running dfhack 0.34.11 r3 and df 34.11.

EDIT: Fixed this. Turns out that I had installed r3 incorrectly. Reinstalled and it works now.

[Heimdall86]

So, I've got an interesting problem that I'm hoping DFHack can fix.  During a swarm of mod critters attacking my fort, I ended up with the last one stuck in a projectile state in the air above my fort, but was motionless.  Absolutely no idea how that happened, but I couldn't get my military to kill it in that state.  So, I did something that was probably a terrible idea and removed the projectile flag from the creature.  That let it fall to the ground where the military could kill it.

Trouble is, I'm getting massive spam in the combat logs about it slamming into an obstacle at the spot where it was originally stuck, even though it is long dead (I don't recall if it was doing that before I removed the projectile flag, but it was stuck there).  Any ideas on how to fix that?  Is there a feature of the map tile I need to configure?   Will setting a flag on the unit help?  Will just atomsmashing its body fix the problem?

Easy fix just type slayrace into the dfhack console and see the list of all the creatures in the area, when you figured out what the modded creature is called just type slayrace creaturename

[WillowLuman]

Does slayrace kill everything (of that creature type) on the map, or in the entire world?

[Rose]

Just in the fort

However, you can also type "slayrace him" to just kill a single unit.

[Meph]

I do have s suggestions to make, which probably helps people unfamiliar with dfhack quite a lot. With all the new plugins, scripts, and endless possibilites in the dfhack init, if would be very nice if people could read the hotkeys ingame. I would suggest an addition to the ingame menu that says: Press "whatever button here" to show dfhack hotkeys.

Like this:


I just think that many people dont use dfhack to the extent they could, simply because its inaccessable and requires reading the readme, memorizing hotkeys or altering the dfhack init themselves, and no ingame help. Thats why falconnes plugins get such great feedback, he puts attention to the user interface and accessability.

[Askot Bokbondeler]

i support that, but shift - D is already depot access. i'd suggest crtl - shift - H

[Aerval]

I just think that many people dont use dfhack to the extent they could, simply because its inaccessable and requires reading the readme, memorizing hotkeys or altering the dfhack init themselves, and no ingame help.

Seriously? That's exactly what DF itself is about

[Meph]

Its an example ^^ I still stay with the principle though.

I have 21 hotkeys in my init atm, and without a visual reminder now and then even I have to look them up, and I am the one who wrote them in the init. I cant expect players of the mod to simply remember them from reading them once on the release post.

[Telgin]

Easy fix just type slayrace into the dfhack console and see the list of all the creatures in the area, when you figured out what the modded creature is called just type slayrace creaturename

Thanks, I'll try that.  It's already dead though, will this help in ways that just killing it didn't?

[Undeadlord]

Its an example ^^ I still stay with the principle though.

I have 21 hotkeys in my init atm, and without a visual reminder now and then even I have to look them up, and I am the one who wrote them in the init. I cant expect players of the mod to simply remember them from reading them once on the release post.

I second this! DFHack is amazing, but man I barely use half of it just because I forget that functionality is there.

[Rumrusher]

Its an example ^^ I still stay with the principle though.

I have 21 hotkeys in my init atm, and without a visual reminder now and then even I have to look them up, and I am the one who wrote them in the init. I cant expect players of the mod to simply remember them from reading them once on the release post.

I second this! DFHack is amazing, but man I barely use half of it just because I forget that functionality is there.

hmm I think Dfhack has hit the point where the power it can do is far over the heads of the people. Like only folks like the good folks who hang out at the irc daily maybe me could write up a mod and do magical things with it. I'm still having a mind overload on how to implement some of these scripts into a mod, also the new r3 being completely different and breaking half of the new scripts that never pop up in r2 that I had in pre-r3.
though I don't use all or most of what dfhack has outside of Dfusion/lua and Gm-editor/scripts. also I kinda worried that most of the new scripts are interrupting each other leading to new bugs.

[smakemupagus]

Is the temperature threshhold for autoSyndrome still 9000?  I find that my wood/bone buildings still get destroyed by temperature damage even when using a boiling stone at 9005 urists.

Although 9005 is below the colddam point for wood, this destruction didn't happen pre-DFHack r3 (or even much colder temperatures are still safe if  I 'unload all' at the DFHack terminal).  So I infer that autoSyndrome is responsible for somehow more thoroughly applying the damage to the workshop.

Do you think it is possible to undo the building destruction aspects, at least for the 9005 temperature materials but ideally for everything?  It would be nice to be able to use bone/wood for buildings, but if it is impossible I will try to work around it.

edit.
Shoot, sorry... I don't think it's autoSyndrome after all.
unload all -- they don't damage
unload autoSyndrome -- still get damage

any thoughts what else is new in DFHack r3 that can be causing this?  Or is it more appropriate for me to ask Meph what changes there have been in the scripts he loads in Masterwork?

[expwnent]

Again, unless you use PRESERVE_ROCK it won't be an issue.

Also, it looks at the boiling temperature, not the default temperature that it has when it's created, however that works.

[Meph]

I didnt change any scripts. I said its my change to the stone_vapor_template. If it isnt, I am just as dumbfounded as you. No idea what else could be the cause.