Print

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

[spikeof2010]

Needs the SYN_NAME.

Code: [Select]

[INORGANIC:DFHACK_ITEMSYNDROME_MATERIAL_GASATE]
[USE_MATERIAL_TEMPLATE:METAL_TEMPLATE]
[SYNDROME]
[SYN_CLASS:DFHACK_ITEM_SYNDROME]
[SYN_NAME:long sword]
[CE_SPEED_CHANGE:SPEED_PERC:200:START:0]
Still doesn't work. I'm very sorry for pestering you, I'm just rather confused as to why it doesn't work.

[Putnam]

[SYN_NAME:long sword] All creatures with long swords will be affected by this syndrome.

It needs to be named "boot of speed", not "long sword"

[Roses]

Did you read the example? The syndrome goes in a material, not in the item.

Whats the difference between the [SYN_CLASS:DFHACK_ITEM_SYNDROME] and using [INORGANIC:DFHACK_ITEMSYNDROME_MATERIAL_]? I thought the first was what went in items (so that that item, no matter what its made of, will give the unit the syndrome) and that the second went in the inorganic (so that any item made of the material, no matter the item, will give the unit the syndrome).

[Putnam]

Nothing goes in the item ever.

The SYN_CLASS goes in the syndrome under the item. Read the entire example, not just part.

To answer your question, [SYN_CLASS:DFHACK_ITEM_SYNDROME] means that any item made of that material will have the syndrome; using [INORGANIC:DFHACK_ITEMSYNDROME_MATERIAL_X] will make it so that the specific item made out of any [/i]material[/i] will give the syndrome.

[narhiril]

Alright, I'm tearing my hair out here.  Just upgraded to the r4 version, and I'm having two problems...

1) When the game loads, itemsyndrome prints "itemsyndrome enabled," but starts disabled, despite being enabled in the dfhack init.

2) Even once it's enabled, itemsyndrome isn't actually applying syndromes.  Turning debug on shows a bunch of unit and item checks, but none of them actually get the syndrome.

Code: (dfhack.init) [Select]

##########LFR v0.21 init file##########

##binary patches to fix vanilla bugs##

binpatch apply deconstruct-heapfall #prevents buildings from killing or injuring dwarves when deconstructed#
binpatch apply deconstruct-teleport  #prevents items from teleporting around when a building is deconstructed#
binpatch apply hospital-overstocking #makes hospitals actually obey their stock limits#
binpatch apply custom-reagent-size #allows for partial use of reagents with dimensions in custom reactions - not used in LFR, but doesn't hurt#
binpatch apply training-ammo #allows marksdwarves to pick up and use training ammunition even if their quiver is full of combat ammo#
binpatch apply armorstand-capacity     #doubles the capacity of armorstands#
binpatch apply weaponrack-unassign #fixes weapon racks - works together with the "fix armory" plugin#

##tweaks##

tweak patrol-duty #dwarves will not get negative thoughts for training sessions#
tweak stable-cursor #cursor remembers its position between menus#
tweak fix-dimensions #something involved with the custom reagent size fix#
tweak military-stable-assign #military position assignment list will no longer jump back to the start every time a unit is assigned#
tweak military-color-assigned #units already in squads will appear as a different color in the military assignment list#
tweak hive-crash #fixes a bee-related crash bug#

##plugins##

load autoSyndrome #required for ritual transformations and mechanical constructs#
autoSyndrome enable
load syndromeTrigger #required to make paragons work properly#
syndromeTrigger enable
load infiniteSky
infiniteSky enable #raises the map ceiling if you build up to it#

##scripts##

fix/growthbug enable #Fixes a bug with dwarves not growing to full adult size#
itemsyndrome enable contaminantsoff #Required for magical weapons#



Code: (material) [Select]


[INORGANIC:DFHACK_ITEMSYNDROME_MATERIAL_STONECRUSHER]
[USE_MATERIAL_TEMPLATE:STONE_VAPOR_TEMPLATE]
[SYNDROME]
[SYN_NAME:stonecrusher]
[SYN_CLASS:DFHACK_ITEM_SYNDROME]
[SYN_CLASS:DFHACK_WIELDED_ONLY]
[CE_CAN_DO_INTERACTION:START:0]
[CDI:ADV_NAME:pulverizing smash]
[CDI:INTERACTION:MATERIAL_EMISSION]
[CDI:MATERIAL:INORGANIC:GRANITE:SOLID_GLOB]
[CDI:TARGET:C:LINE_OF_SIGHT]
[CDI:TARGET_RANGE:C:3]
    [CDI:VERB:smash the stonecrusher into the ground, kicking up stone fragments:smashes the stonecrusher into the ground, kicking up stone fragments:NA]
[CDI:MAX_TARGET_NUMBER:C:8]
[CDI:WAIT_PERIOD:1300]
[CDI:USAGE_HINT:ATTACK]


[Putnam]

Does it output the "item itself has syndrome" message?

[narhiril]

Does it output the "item itself has syndrome" message?

Nope.  Using the latest code from github.

I feel compelled to note that this same setup worked with my old r3 version of itemsyndrome - the only thing I changed in the raws was removing the end times.

[Putnam]

Oh.

Oh.

"SC_WORLD_LOADED" should be SC_WORLD_LOADED.

Oy.

Fixed.

[narhiril]

Oh.

Oh.

"SC_WORLD_LOADED" should be SC_WORLD_LOADED.

Oy.

Fixed.

Got it, it's working perfectly now.  Thanks!

[narhiril]

Say, I noticed you altered the spawnunit code to use in reactions...

I could use this.

Just a question: how do I make the unit spawn in the workshop?

autosyndrome

Will spawnunit accept \LOCATION in place of a cursor position?  I'd like to be able to call it using syndromeTrigger to spawn a unit at the affected unit.

[Putnam]

Very much yes; I changed it specifically to allow for that.

Warmist's version is necessary for r4, mind; mine is just for r3. I'm not sure if Warmist's version has the location code in it, though.

[narhiril]

Very much yes; I changed it specifically to allow for that.

Warmist's version is necessary for r4, mind; mine is just for r3. I'm not sure if Warmist's version has the location code in it, though.

Alright, thanks.  Where might I find that?  I can only find the r3 one.

[Putnam]

https://gist.github.com/warmist/4296504

And no, this doesn't have the location code. Lemme just stick that in there, wait a sec...

EDIT: here it is

[narhiril]

Alright, here's what I get.

Code: [Select]

[DFHack]# spawnunit DWARF 0 Urist
...sktop\LFR DFHack r4 Test Copy\hack\scripts/spawnunit.lua:84: Cannot read fiel
d body_component_info.body_layer_338: not found.
stack traceback:
        [C]: in function '__index'
        ...sktop\LFR DFHack r4 Test Copy\hack\scripts/spawnunit.lua:84: in funct
ion 'CreateUnit'
        ...sktop\LFR DFHack r4 Test Copy\hack\scripts/spawnunit.lua:169: in func
tion 'PlaceUnit'
        ...sktop\LFR DFHack r4 Test Copy\hack\scripts/spawnunit.lua:233: in main
 chunk
        (...tail calls...)
[DFHack]#

Not as worried about this one, as I don't have any raws that depend on it yet, but I thought you guys should see it.

[Roses]

To answer your question, [SYN_CLASS:DFHACK_ITEM_SYNDROME] means that any item made of that material will have the syndrome; using [INORGANIC:DFHACK_ITEMSYNDROME_MATERIAL_X] will make it so that the specific item made out of any [/i]material[/i] will give the syndrome.

Can the [INORGANIC:DFHACK_ITEMSYNDROME_MATERIAL_X] be given multiple [SYN_NAME] tokens so that it applies to multiple items?

i.e.

Code: [Select]

[INORGANIC:DFHACK_ITEMSYNDROME_MATERIAL_TEST] Inorganic needs to be called DFHACK_ITEMSYNDROME_MATERIAL_(anything goes here)
[USE_MATERIAL_TEMPLATE:STONE_TEMPLATE] This is just a quirk of mine >_>
[SYNDROME]
[SYN_NAME:long sword] All creatures with long swords will be affected by this syndrome.
                [SYN_NAME:short sword]
                [SYN_NAME:bastard sword]
[CE_BODY_TRANSFORMATION:START:0]
[CE_CREATURE:TOAD:MALE] Syndrome turns creature into a toad.
So that all creatures with long swords, short swords, or bastard swords are affected by the syndrome? Or do I need a separate inorganic for each item?