Print

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

[Milksquid]

Im playing with the lazy newb pack and whenever I try to assign a labor to a dwarf with v>l it either will immediately unassign the labor or activate other labors in addition to the one I wanted to activate.  Im having the same problem with Dwarf Therapist.  If I try to commit the labor to a specific dwarf and then I "read dwarves" it shows the labors that I just committed not being activated. 

I figure its some sort of problem with DFhack but disabling things like automatic job assignments in the launcher doesnt seem to make a difference. I tried searching for other people with the same problem in the forum but I got hundreds of false results. What am I doing wrong?

Edit: After experimenting the problem seems to go away if I launch DF without the lazy newb pack launcher.  What in the launcher would be messing with jobs like that?

EDIT2: Definitly seems to be dfhack. If I launch DF with the dfhack option off I dont have the problem. If I launch with dfhack on then I do have the problem, even if all of the options in dfhack are set to off. Maybe its activating "automatic job assignments" even when I have it set to not and its messing with my jobs. I dont know if there is a way to turn that off from the dfhack console but I cant find it, so I guess Ill just go without dfhack until an alternative presents itself.

EDIT3: Solution found. Type "autolabor 0" in dfhack to disable autolabor.

[smeeprocket]

It has something to do with the lazy newb pack. I stopped using it because of that. It was forcing one dwarf to fish and not letting me assign any other fisherdwarves.

[PatrikLundell]

I'm using the PyLNP without having these problems. The symptoms definitely points towards automatic job assignments (something I've never used).
If I read DFHack correctly, it's called autolabor in DFHack, so typing "autolabor status" should give an error message that it's not enabled. "autolabor disable" in DFHack should turn it off if it's on (i.e no error message), but that's likely to affect the current session only.
However, I did have a problem with Workflow a while back: I enabled it, didn't like it, and disabled it, but it still started up, despite me disabling it in the PyLNP UI, so the changed setting was stored in some file, but not reflected nor affected by the UI thereafter.
I think the setting is game wide, which means that a move of the save, a reinstall of PyLNP, and a restoration of the save should get rid of the problem, if that is the cause.

[rjs71053]

http://www.bay12forums.com/smf/index.php?topic=145134.0;topicseen

I think this was the same problem, fix found.

[Milksquid]

So it seems like possibly lazy newb pack is just automatically activating autolabor for me even if I have it set to off I. Typing "autolabor 0" in the command prompt makes it go away.  Ill have to run it a few times to make sure thats exactly whats going on.

EDIT: So to sum things up, for Dwarf Fortress 40_16 Starter Pack r2, when I launch the game with DFhack activated, but "Automatic Job Assignments" set to off it seems to activate "Automatic Job Assignments" anyway. The way I fixed it was to go to the dfhack prompt and type "autolabor 0" which seems to turn it off.  Obviously you can turn it back on with "autolabor 1".