Print

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

[Putnam]

I cannot see how that could possibly happen from changing the subtype of a single item. What exactly did you do for the short sword?

[lonjil]

Is it possible to use dfhack when running df in text mode?
It runs, but the only way to run commands is with dfhack-run, which is annoying.

[Youbo]

I cannot see how that could possibly happen from changing the subtype of a single item. What exactly did you do for the short sword?

I changed weight_fraction and everything in subtype(the entire ''folder'',not the similarly named value inside the folder that seems to be the ID)to exactly match what was on an existing long sword.

[lethosor]

Is it possible to use dfhack when running df in text mode?
It runs, but the only way to run commands is with dfhack-run, which is annoying.

Technically speaking, that is using DFHack.
The command-prompt plugin should work, but you'd have to invoke it with dfhack-run as well since DFHack keybindings (bound with the "keybinding" command) rely on SDL. It would be possible to modify the plugin to add a keybinding to the main fortress mode menu (or other screens, although they'd have to be implemented individually) - I'll look at including this in the next release.

[Max™]

Oh I think the short sword thing was kinda like duplicating raws by hand in game, I had the feeling it would mess things up so I didn't fiddle with it.

[StagnantSoul]

Um, did I miss something? I'm using the newest version of the starter pack, and rb_eval df.gametype = :DWARF_ARENA  no longer works. It says rb_eval is not a recognized command.

[lonjil]

Is it possible to use dfhack when running df in text mode?
It runs, but the only way to run commands is with dfhack-run, which is annoying.

Technically speaking, that is using DFHack.
The command-prompt plugin should work, but you'd have to invoke it with dfhack-run as well since DFHack keybindings (bound with the "keybinding" command) rely on SDL. It would be possible to modify the plugin to add a keybinding to the main fortress mode menu (or other screens, although they'd have to be implemented individually) - I'll look at including this in the next release.

Thanks.
For now I've settled on a bash script that loops dfhack-run. Unfortunaly this doesn't work with interactive commands.
Can the remote interface handle those? Then I might try to make something with it.

Edit: Here's a screengrab

[Max™]

Ok I've been looking over the lua api, various dfhack scripts, and screwing around for a while but I'm stumped.

How do you get something to add a new entry with the right tables linked in?

I was trying to do various stuff with df.global.world.artifacts.all, I tried :new(), :insert('#',foo), :assign(foo,bar) and so forth. I know I can open it up with gm-editor and alt+i insert an artifact_record manually but everything I've attempted with a script just leaves it as nil.

What am I derping out on that is super obvious and was probably right in front of my face this whole time?

[Warmist]

:insert('#',{new=true,<... other things to set>}) or  :insert('#',{new=df.some_type,<... other things to set>}) IIRC

[Max™]

I would like to mail you a hug but I don't know how.

[Rallor]

I'm interested in retrieving a dwarf's hairstyles and facial features using dfhack. After looking at the source code of stonesense I am under the impression these values are stored in "unit.appearance.tissue_style". At first I thought the values are in the same order as they appear in the white segment of the character description, but the values of dwarves that have the same styles do not match up. Could someone tell me how these values are matched to what you can read on the character description screen?

Spoiler: Dwarf 1 (click to show/hide)

Spoiler: Dwarf 2 (click to show/hide)

[scamtank]

I'm interested in retrieving a dwarf's hairstyles and facial features using dfhack. After looking at the source code of stonesense I am under the impression these values are stored in "unit.appearance.tissue_style". At first I thought the values are in the same order as they appear in the white segment of the character description, but the values of dwarves that have the same styles do not match up. Could someone tell me how these values are matched to what you can read on the character description screen?

Spoiler: Dwarf 1 (click to show/hide)

Spoiler: Dwarf 2 (click to show/hide)

It's weird, I grant you. The values of the properties themselves are visible in the string dump, in order:

(-1: nothing of note)
0: NEATLY_COMBED
1: BRAIDED
2: DOUBLE_BRAIDS
3: PONY_TAILS
4: CLEAN_SHAVEN

But just by looking at those makes my head hurt, even after some personal experimenting:

Bodyparts:
0 and 1: Both are sideburns?? One each for two specific properties? Length and color have their own bins.
2 and 3: Moustache and beard.
6 and 7: Both are hair, again??

[Rallor]

Thank you. But what did you use, or how did you figure out what was what?

[scamtank]

gui/gm-editor is the go-to for quick tweaks, especially when you're an illiterate dong who can't operate lua from the command line like me. K-cursor a dwarf and punch it in, it'll jump straight to the unit vector.

e: Oh and just plain deduction. One's 3 is double-braided and the other's is combed, find the 2 in one and 0 in the other.

[Warmist]

I have 2 text files with appearance research... Not sure how much is integrated changed (and am too lazy to even run df and see)

Code: [Select]

unk_4cc - tissue style
unk_4dc - civ_id
unk_4ec -??
unk_4fc -??
unk_50c - lenght?

bp_modifiers->caste.bp_appearance.modifiers[caste.bp_appearance.modifier_idx[k]]
And a script called "find_hair.lua"

Code: [Select]

local race=465
local modifiers={}
local modifiers_idx={}
local caste=df.creature_raw.find(race).caste[1]
local bp=caste.bp_appearance
local unit=dfhack.gui.getSelectedUnit()
for k,v in pairs(bp.modifiers) do
    if v.noun=='hair' then
        print(k,df.appearance_modifier_type[v.type])
        modifiers_idx[k]=true
        table.insert(modifiers,v)
    end   
end
for k,v in pairs(bp.modifier_idx) do
    if modifiers_idx[v] then
        print(k,v)
    end
end
for anyone who cares