Print

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

[Roses]

Could anyone explain how I go about using item-trigger in the RAWs? I can't seem to find anything on it other than an explanation of its function. My apologies if I am missing anything.

EDIT: More broadly, are there examples or a how-to-use the modtools mentioned in the readme? Because the readme itself only explains what they do, not how to apply them.

The various modtools were discussed here. I don't believe that there has been much other information about them, but you basically don't modify anything in the raws, you put everything into onLoad.init now, example syntax from expwnent's post

Code: [Select]

# example syntax
modtools/item-trigger -material INORGANIC:GOLD -command [ devel/printArgs "gold item equipped!" ] -onEquip
modtools/item-trigger -material CREATURE_MAT:DWARF:SKIN -command [ devel/printArgs "dwarf skin item? gross. put it back down." ] -onEquip
modtools/item-trigger -itemType ITEM_WEAPON_SPEAR -onStrike -command [ devel/printArgs "spear strikes target!" ]

[expwnent]

Basically the only documentation right now is modtools/blah -help and the readme. Do you have any specific questions about how to use them? I'm not sure what you want.

[thistleknot]

Anyone know of some symbol offsets I can manipulate to emulate nanofortress?

Use "embark-tools".
Edit: To be specific, "embark-tools enable nano".

Code: [Select]

embark_site is not a recognized command.
Invalid hotkey command: 'embark_site nano'

actually... seems to not error out, but I still don't end up with a 1x1

I'm looking at how I used it in mw v5.10

dfhack.init

Code: [Select]

keybinding add Alt-N@choose_start_site "embark_site nano"

[lethosor]

I said "embark-tools enable nano", not "embark_site nano". embark-tools is a plugin new in r5 (an improved version of embark_site, plus a few other features).

[thistleknot]

I know what you said... [miscommunication on what I was stuck on.  I tried your command, and then looked at how pre version was implemented... then you noted the command line change]

It's working.

Pasting the command in, and resizing **down** my embark size seemed to work.

Glad to know the command line updates

[Teneb]

Basically the only documentation right now is modtools/blah -help and the readme. Do you have any specific questions about how to use them? I'm not sure what you want.

Just wanted to know how to use them. Thanks for the help.

Actually, another question:

Could anyone explain how I go about using item-trigger in the RAWs? I can't seem to find anything on it other than an explanation of its function. My apologies if I am missing anything.

EDIT: More broadly, are there examples or a how-to-use the modtools mentioned in the readme? Because the readme itself only explains what they do, not how to apply them.

The various modtools were discussed here. I don't believe that there has been much other information about them, but you basically don't modify anything in the raws, you put everything into onLoad.init now, example syntax from expwnent's post

Code: [Select]

# example syntax
modtools/item-trigger -material INORGANIC:GOLD -command [ devel/printArgs "gold item equipped!" ] -onEquip
modtools/item-trigger -material CREATURE_MAT:DWARF:SKIN -command [ devel/printArgs "dwarf skin item? gross. put it back down." ] -onEquip
modtools/item-trigger -itemType ITEM_WEAPON_SPEAR -onStrike -command [ devel/printArgs "spear strikes target!" ]

Where is onLoad.init located? Checked the dfhack files and couldn't find it. Assuming I have to create it, where does it go?

[lethosor]

data/save/regionX/raw/onLoad.init

[Teneb]

But if it only appears after genning a world, how can I, for example, set a specific god to be created for every world with moddable-gods?

[lethosor]

But if it only appears after genning a world, how can I, for example, set a specific god to be created for every world with moddable-gods?

You could create an onLoad.init in DF/raw, which should be copied to the 'raw' folder of new saves, but this won't apply to existing saves. I'm hoping to implement a global onLoadWorld.init in the next version of DFHack, but something like this should work for now (placed in dfhack.init, which loads onLoad.init in the main DF directory):

Code: [Select]

:lua dfhack.onStateChange.foo = function(state) if state == SC_WORLD_LOADED then print((dfhack.run_command('script onLoad.init'))) end end

[Roses]

Placing it in dfhack.init will work as a global onLoad.init, placing onLoad.init into the objects/raw/onLoad.init will mean that any world you generate will get a copy of it put into that worlds file.

[lethosor]

Placing it in dfhack.init will work as a global onLoad.init, placing onLoad.init into the objects/raw/onLoad.init will mean that any world you generate will get a copy of it put into that worlds file.

If moddable-gods needs to be run when a world is loaded, it won't work in dfhack.init (I'm not sure if this is the case, though).
Also, it's "raw/onLoad.init", not "raw/objects/onLoad.init" (see here). Assuming this was a typo.

[Teneb]

My thanks for your help. I think I understand now. Are there any side effects of both creating a onLoad.int in raw and placing the command on dfhack.init as well?

[expwnent]

It would run twice if you do it that way.

[vjek]

I'm looking for information regarding if it's possible to enumerate the effects of Evil biomes via DFHack, and/or if anyone has done any investigation into how this might be possible.

Specifically, I'm looking to determine, proir to embark, if a region/tile/area with an evil biome has blood rain, nasty clouds, re-animation, husking, etc.  Much the same way that prospect and probe provide information, today, ideally.

Even if there is currently no script or tool that does it, does anyone know of where in the structures one might start to look to enumerate or identify these effects?  Thanks in advance for any direction or advice.

[Teneb]

Apologies if I am overlooking something extremely simple, but I am having a problem with the moddable-gods script. More specifically, dfhack claims that "template god" is missing. This template, however, is nowhere to be seen, nor are there any hints of how to create it in the file. Keep in mind I tried to use the script both through onLoad.init as well as dfhack.init (not at the same time, however).