Print

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

[devek]

One funny thing reverb, is that when a barrel or bin is first made made, it is inside of a workshop (which is a container)

I made an exception for bins/barrels that have 1 "item" and +0x0c is 0. I think that is good enough?

I also made it so you could count just wooden bins by doing type="bin" material="organic"

This will probably be my last bug fix release until I have the manager structure done.. I am making good progress and just need another week or so. I have other stuff going on irl

[Reverb]

One funny thing reverb, is that when a barrel or bin is first made made, it is inside of a workshop (which is a container)

I made an exception for bins/barrels that have 1 "item" and +0x0c is 0. I think that is good enough?

I also made it so you could count just wooden bins by doing type="bin" material="organic"

This will probably be my last bug fix release until I have the manager structure done.. I am making good progress and just need another week or so. I have other stuff going on irl

Yeah, I had suspected that but hadn't had the inclination to check that yet. I'll have to check your update out.

I'm screwing around with figuring out what dwarfs are doing when they don't have a job pointer. I found the function for generating the text description on the screen but for this, it requires executing function pointers from the various data structures it looks at. It is probably just as bad as that item description function you found except that some of the branching is hidden by say call eax branches. Thankfully it doesn't have 60+ cases to check. I'm tempted to figure out how to call those functions from my code most likely through a remote thread but I haven't quite figured out the approach I'm gonna take. Any suggestions? I know you contemplated doing this with the text descriptions of items.

[devek]

To run DF's code, you're going to have to inject code, and that is going to set off people's anti-virus programs.

Executing function pointers it the same problem you run into finding out the information about an item's type. If you look at dfhack's dump item code you'll see where it is actually reading the code to figure out what to do. Maybe you can adapt that to what you are doing?

[Reverb]

I'm having trouble with plaster. If you get the string for it from your util, it says "Make Plaster Powder" in the job manager. However, I come back a little bit later and it says "Reaction" and my loom will have "Reaction" in it.

Ty for the suggestion about looking at the code. The prior way of reverse engineering the idle dwarfs wasn't working so I went with what DF uses to figure out the idle count in the top corner of the screen. The functions I have had to "call" are very basic and all I need to do is check what is being moved into the accumulator. Anyways, reversing this code sucked big time but I have something that seems to be returning the correct idle numbers . I don't think this code is going to survive an update unless I find a way to automate the several offsets I have found .

[devek]

Ya, plaster is a custom reaction and custom reactions are implemented totally different. The next version of Foreman probably won't support them at all while I make sure I have the standard reactions right.

The good news is that .13 seems easier to decompile.

[devek]

I got my stuff mostly working with .13..

I have also finished my analysis of the job structure and I am ready to implement the code for it.

DO NOT EVEN TRY TO USE CUSTOM JOBS, omg lol.

[forsaken1111]

Would it be possible/feasible/difficult to check dwarf labors when a job is assigned and if no dwarf has the required labor, pick the one with the highest relevant skill and enable it while disabling some/all of his other labors? (probably just hauling, removing all could cause problems I suppose).

[devek]

That would be possible with my next project, Dwarf Overlord.

Dwarf Foreman is a simple utility I plan to finish and open source soon.

[forsaken1111]

I could see this tying together all of the 3rd party utilities. You embark and run dwarf overlord. It digs out your fortress according to a quickfort diagram, manages production according to dwarf foreman specifications, and controls labor like Dwarf Therapist.

Mmm...

[devek]

Well, it will be a pluggable interface with triggers.

When X is true do Y.

Plugins, like a therapist plugin would add variations to X and Y. Other plugins could do things like help you designate/design your fortress. If things go well, you could even embed a visualizer such as stonesense and never have to look at the dwarf fortress screen again. I have big plans man

[devek]

Ok, the next release will fully support custom reactions now.

Just need to find the material and map block vectors for .13 and I can release 0.6, whee. 0.7 will be right after, because I have half of the code done in order to do standard jobs too.

Bad news is, I am about to go on a business trip to Texas, hrm. I will bring my laptop with me and pray I have time.

[devek]

Made a new release. This one fully supports custom reactions using the raw name for the reaction. Even ones you modded in yourself

This version doesn't support .13, and will possibly be the last version to support .12. I'm going to track a lot of new offsets for the next version of Foreman.

Would be nice if someone could test the custom reactions code, I found a crash somewhere in there(when you remove the manager job based off a custom reaction completely) but I never could reproduce it. If you can figure out a way to cause it, you get one free Internet.

[forsaken1111]

Now that therapist and foreman are updated for .13 I am actually moving to it. Will report any problems I find.

[devek]

Maybe I wasn't clear, I don't support .13 yet.

The next version will.. I was just dumping my old code before I totally abandoned .12

[forsaken1111]

Maybe I wasn't clear, I don't support .13 yet.

The next version will.. I was just dumping my old code before I totally abandoned .12

Yeah I misread that, sorry. I was all excited too.