Print

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

[Bogus]

im trying to implement the typical vanilla [FUEL] behaviour for a custom (dfhack-made) job. basically i generate a reaction with fuel tag at some point in time while the game is running and then issue a job for it. this works fine, except the [FUEL] doesnt - the job behaves as if there was no fuel needed. i dont know why this happens, presumably because the reaction didnt exist when the game was loaded first?

so i tried to add a bar of fuel to the job struct directly, which is possible, but the fuel will not be used up in the process. my dwarf will get a bar of fuel, use it in the reaction, and then the bar of fuel will remain in the workshop.

what can i do about this?

[CulixCupric]

--

could you have the reaction preformed at a smelter?

[Bogus]

not currently but it probably makes no difference, it doesnt seem to have anything to do with the building. (altho the workhop im using is not a furnace type, the script that does all this can only handle normal workshops at this point.)

[Bogus]

bump.

[Deon]

Is your workshop a "furnace" type? Try changing it to furnace if it's a workshop.
A bit more information could be provided by DFHack team themselves, I am not sure a lot of people out here know how dfhack scripting works >

[milo christiansen]

Do you need to set flags on the job item to make it be consumed? Do you set the required amount to "150"? (if the amount is not 150 it may work 150 times before consuming the fuel item)

[Bogus]

yeah its set to 150. not sure about the flags tho, but i dont think there are any of the sorts.

Spoiler (click to show/hide)

Code: [Select]


-- part of a bigger function
if reaction.flags.FUEL then
local fuel = {
item_type=df.item_type.BAR,
mat_type=df.builtin_mats.COAL,
  mat_index = -1,
  quantity = 150,
  min_dimension = 150
}
job.job_items:insert('#', reagentToJobItem(fuel, reaction.index, numReagents + 1))
end

-- this turns above table into a job item struct
local function reagentToJobItem(reagent, react_id, reagentId)
    local ret_item
    ret_item = utils.clone_with_default(reagent, ws.input_filter_defaults)
    ret_item.reaction_id = react_id
    ret_item.reagent_index = reagentId
    ret_item.new = true
    return ret_item
end


the fuel is added at index n + 1 in the reaction reagents struct, n being the number of reagents used in the reaction.

[milo christiansen]

I have never really done much with job items, so I can't really help. Sorry...

[Quietust]

Have you analyzed a manually-added smelter job to see what its fuel job_item looks like?

[Bogus]

not yet, but thats a good idea. thanks.