Print

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

[Nahere]

uhh gui/gm-editor dfhack.gui.getCurViewscreen() at the calendar then change either the tick or a year to 0 and you will instantly jump to the adv menu.

"gui/gm-editor scr" does the same thing, by the way.

Thanks.

[ab9rf]

The auto-melt for stockpiles doesn't seem to do anything.. I let it run for a month or two. Auto-trade works though. I'm on alpha 4.

It works for me fairly reliably. Note that while auto-melt marks things for melting, it doesn't queue up melt object jobs at a furnace. You have to use some other mechanism to arrange for that.

[PeridexisErrant]

The auto-melt for stockpiles doesn't seem to do anything.. I let it run for a month or two. Auto-trade works though. I'm on alpha 4.

It works for me fairly reliably. Note that while auto-melt marks things for melting, it doesn't queue up melt object jobs at a furnace. You have to use some other mechanism to arrange for that.

Workflow (without a quota) will make repeat jobs suspend instead of cancelling when there are no inputs, and automatically resume when there are - which is perfect for automelt.

[milo christiansen]

Except last I knew that didn't work anymore... Maybe it was fixed.

[necrotic]

Except last I knew that didn't work anymore... Maybe it was fixed.

Workflow? It definitely works, even in 0.43.05. I use it all the time. I think it was partially busted when the new workorder system was added, but not for long.

[lethosor]

It wasn't ever broken, as far as I know. The keybinding was removed because there was concern that it would be broken or unnecessary, but I haven't seen any reports of that.

[necrotic]

Ah right. I knew there was something with workflow a while back.

[ab9rf]

The auto-melt for stockpiles doesn't seem to do anything.. I let it run for a month or two. Auto-trade works though. I'm on alpha 4.

It works for me fairly reliably. Note that while auto-melt marks things for melting, it doesn't queue up melt object jobs at a furnace. You have to use some other mechanism to arrange for that.

Workflow (without a quota) will make repeat jobs suspend instead of cancelling when there are no inputs, and automatically resume when there are - which is perfect for automelt.

You can also use DF's built-in job manager to get essentially the same effect now. Queue up a repeating "melt object" job with an input threshold on "meltable items" or something like that.

I haven't used workflow at all since 43.xx; the built-in manager can do almost as much and is in some ways better.

[lethosor]

A couple people have been reporting a Linux crash that was fixed a couple weeks ago, so I decided it would be a good time for another build:

https://github.com/DFHack/dfhack/releases/tag/0.43.05-beta1

Hopefully this one is more stable than others. We seem to have moved past the catastrophic issue stage, so this is now a "beta" build. Do keep checking for problems, though.

[Roses]

Question about item-trigger. I know having more than one condition on a single item-trigger call isn't supported (i.e. you can't have -itemType and -material defined), but what if I create two seperate item-triggers, one that triggers on equip of an item type and one that triggers on equip of an item material? If I have an item of the correct type and material will both be triggered?

EDIT: Follow up question, will using modtools/equip-item trigger an -onEquip modtools/item-trigger?

[lethosor]

A couple people have been reporting a Linux crash that was fixed a couple weeks ago, so I decided it would be a good time for another build:

https://github.com/DFHack/dfhack/releases/tag/0.43.05-beta1

Hopefully this one is more stable than others. We seem to have moved past the catastrophic issue stage, so this is now a "beta" build. Do keep checking for problems, though.

Update: Windows builds are now available, thanks to Quietust.

[Pwnzerfaust]

A couple people have been reporting a Linux crash that was fixed a couple weeks ago, so I decided it would be a good time for another build:

https://github.com/DFHack/dfhack/releases/tag/0.43.05-beta1

Hopefully this one is more stable than others. We seem to have moved past the catastrophic issue stage, so this is now a "beta" build. Do keep checking for problems, though.

Update: Windows builds are now available, thanks to Quietust.

Awesome. Many thanks to both of you.

[Roses]

Is it possible to pause a script at a certain line, let DF run for a given amount of frames, and then resume the script? I know I can use dfhack.timeout() to basically do what I want, but I was hoping for a smoother option.

[Putnam]

The script API allows that with script.sleep

[Max™]

Hmmm, I'm probably a tard because I couldn't find more info on the script.sleep stuff in any of the docs, but it gave me a reason to learn more about timeouts which let me get questport working even if you're not in travel mode when you pull up the quest log and use it, had to fiddle with the timing some but the brief flicker when it is first used on foot is a small price to pay for zooping around the quest log and ending up where you're looking. Dunno why I thought I could just put myself into travel mode and do an hour wait, can't pull up the log that way, and incidentally yes I do know about the dfhack.screen and sendInput options, call it superstitious but the timing on those didn't work as well as just slapping in the simulated inputs, and when I tried to clean up the code a bit I lost the ability to use it without being in travel mode first so I had to roll it back and figure it out again.

Code: (questport.lua) [Select]

local gui=require 'gui'
local qp=df.global.gview.view.child
local qmap=dfhack.gui.getCurViewscreen()
local qarm=df.global.world.armies.all
if df.viewscreen_adventure_logst:is_instance(qmap) then
local qx=qmap.cursor_x*48
local qy=qmap.cursor_y*48
local rx=qmap.player_region_x*48
local ry=qmap.player_region_y*48
df.global.ui_advmode.unk_1=qx
df.global.ui_advmode.unk_2=qy
if df.global.ui_advmode.menu==0 then
gui.simulateInput(qp.child,'LEAVESCREEN')
df.global.ui_advmode.menu=26
df.global.ui_advmode.travel_not_moved=true
gui.simulateInput(qp,'CURSOR_DOWN')
dfhack.timeout(15,'frames',function()
gui.simulateInput(qp,'A_TRAVEL_LOG') end)
-- print('Ready to teleport!') end)
elseif df.global.ui_advmode.menu==26 then
for k,v in ipairs(qarm) do
if v.flags[0] then
local my_arm=df.global.world.armies.all[k].pos
if (rx~=qx or ry~=qy) then do
my_arm.x=qx
my_arm.y=qy
qmap.player_region_x=qmap.cursor_x
qmap.player_region_y=qmap.cursor_y
     end
end
    end
end
    end
endOnly bug I know of atm is that you can't use it if you've gotten the "you cannot travel til you leave this site" message, not sure which flag or whatnot has to be flipped to fix that, but assuming you don't try to travel out before using it, the script will zoop you out just fine.