Print

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

[Putnam]

This readme

Do you mean with raws? Sorry, not yet. Soon. However, you can do this:

item.flags.garbage_collect = true

This works for projectiles, too. Doing that will make the item disappear soon enough.

[Deon]

I meant with LUA.

How would I... write it so that "projectile" has that flag set? As I said I am a total newbie when it comes to lua syntax yet.

Currently I have this:

Code: [Select]

events=require "plugins.eventful"
events.onProjItemCheckImpact.expansion=function(projectile)
if projectile then
local material = getMaterial(projectile.item)
if matExplodesWeb(material) then dfhack.maps.spawnFlow(projectile.cur_pos,8,0,0,50000) end
if matExplodesFire(material) then dfhack.maps.spawnFlow(projectile.cur_pos,7,0,0,50000) end
if matExplodesDragon(material) then dfhack.maps.spawnFlow(projectile.cur_pos,6,0,0,50000) end
if matExplodesSmoke(material) then dfhack.maps.spawnFlow(projectile.cur_pos,5,0,0,50000) end
if matHasScriptAttached(material) then
local script = getScriptFromMaterial(material)
dfhack.run_script(unpack(script))
end
end
end

[Warmist]

This readme

Do you mean with raws? Sorry, not yet. Soon. However, you can do this:

item.flags.garbage_collect = true

This works for projectiles, too. Doing that will make the item disappear soon enough.

Better use "dfhack.items.remove(item)". This way it hides it instantly and then game removes it later (it also may or may not include all the logic not to crash the game with missing references...)
@Deon:

Code: [Select]

    if projectile then
<..> stuff here<...>
        dfhack.items.remove(projectile.item) --hopefully this does not crash ;)
    end
Also Putnam you can use "table.unpack" instead of your own.

[Deon]

Thanks a lot, Warmist! What would we do without you <3.

[Deon]

Code: [Select]

events.onProjItemCheckImpact.expansion=function(projectile)
if projectile then
local material = getMaterial(projectile.item)
if matExplodesWeb(material) then
dfhack.maps.spawnFlow(projectile.cur_pos,8,0,0,50000)
dfhack.items.remove(projectile.item)
end
if matExplodesFire(material) then
dfhack.maps.spawnFlow(projectile.cur_pos,7,0,0,50000)
dfhack.items.remove(projectile.item)
end
if matExplodesDragon(material) then
dfhack.maps.spawnFlow(projectile.cur_pos,6,0,0,50000)
dfhack.items.remove(projectile.item)
end
if matExplodesSmoke(material) then
dfhack.maps.spawnFlow(projectile.cur_pos,5,0,0,50000)
dfhack.items.remove(projectile.item)
end
if matHasScriptAttached(material) then
local script = getScriptFromMaterial(material)
dfhack.run_script(unpack(script))
dfhack.items.remove(projectile.item)
end
end
endThis does not remove the item.

[Warmist]

Hmm plan b.
Checked projectile flags. Two thing might work: has_hit_ground and/or to_be_deleted.

Code: [Select]

projectile.flags.has_hit_ground=true --this might be enough...
projectile.flags.to_be_deleted=true --or this or a combination of the two.


[Deon]

It works perfectly, thank you sir!

[Deon]

This is weird.

Code: [Select]

[INORGANIC:IRENE]
[USE_MATERIAL_TEMPLATE:METAL_TEMPLATE]
[STATE_NAME_ADJ:ALL_SOLID:reinforced]
[STATE_NAME_ADJ:LIQUID:molten metal]
[STATE_NAME_ADJ:GAS:boiling metal]
[DISPLAY_COLOR:0:7:1]
[BUILD_COLOR:0:7:1]
[MATERIAL_VALUE:30]
[SPEC_HEAT:500]
[MELTING_POINT:12718]
[BOILING_POINT:14968]
[SOLID_DENSITY:7850]
[LIQUID_DENSITY:6980]
[MOLAR_MASS:55845]
[IMPACT_YIELD:1505000]
[IMPACT_FRACTURE:2520000]
[IMPACT_STRAIN_AT_YIELD:940]
[COMPRESSIVE_YIELD:1505000]
[COMPRESSIVE_FRACTURE:2520000]
[COMPRESSIVE_STRAIN_AT_YIELD:940] 160
[TENSILE_YIELD:430000]
[TENSILE_FRACTURE:720000]
[TENSILE_STRAIN_AT_YIELD:225] 200
[TORSION_YIELD:430000]
[TORSION_FRACTURE:720000]
[TORSION_STRAIN_AT_YIELD:215]
[SHEAR_YIELD:430000]
[SHEAR_FRACTURE:720000]
[SHEAR_STRAIN_AT_YIELD:215] no data, used 200
[BENDING_YIELD:430000]
[BENDING_FRACTURE:720000]
[BENDING_STRAIN_AT_YIELD:215]
[MAX_EDGE:10000]
[ITEMS_HARD]
[ITEMS_METAL]
[SYNDROME]
[SYN_NAME:power armor boost]
[SYN_CLASS:DFHACK_ITEM_SYNDROME]
[SYN_CLASS:DFHACK_ARMOR_ONLY]
[CE_MATERIAL_FORCE_MULTIPLIER:MAT_MULT:NONE:NONE:1:2:START:0:END:200]
[CE_PHYS_ATT_CHANGE:STRENGTH:150:1000:START:0:END:200]
[CE_PHYS_ATT_CHANGE:TOUGHNESS:150:1000:START:0:END:200]
[CE_SPEED_CHANGE:SPEED_PERC:120:START:0:END:200]
I get initial boost when I wear it, but then I cannot repeat it after it wears off.

[Deon]

Yeah, it does not refresh itself. Whenever I wear an armor, it applies the syndrome, but it goes away after a while and is never re-applied, even if I still wear the armor.

P.S. If I type "itemsyndrome force", it reapplies the syndrome. It does not do it normally though.

[Maklak]

I'm just wondering if your magma ammunition could have other things to implement balefire egg / mininuke launcher. Useful effects:
* Make the gun shoot the projectile with so much power that it pieces anything - this is easy, just inctease shoot force and max velocity.
* Spawn 1-2 magma in a 3x3 circle around the impact point. This would probably have to check for map boundaries.
* Spawn cave-in dust that pushes things around.
* Fire fire in circular pattern - by making fire cones in all 9 directions
* Spawn a radiation burst cloud, like ghouls. (Material emission with harmful syndromes)

[Deon]

Yeah, it does not refresh itself. Whenever I wear an armor, it applies the syndrome, but it goes away after a while and is never re-applied, even if I still wear the armor.

P.S. If I type "itemsyndrome force", it reapplies the syndrome. It does not do it normally though.

Okay, apparently SC_WORLD_LOADED is "false" during adventure mode... Any good idea how to check if the game runs in adv. mode too?

[Deon]

Here're the current issues I have with itemsyndrome so far:

1) With SC_WORLD_LOADED test it works in adventure mode only once (does not update).
2) When adventurer is ambushed, the gap for activation is too big. It would be awesome to trigger "itemsyndrome force" once the ambush happens.
3) When you call itemsyndrome in succession, the syndromes stack which often leads to broken huge numbers. There should be a check if a creature is already affected with the syndrome. Maybe even add a check for SYN_CLASS:DFHACK_CLASS_POWERBOOST etc to make mutually exclusive items possible.

[Meph]

Isnt SYN_IMMUNE_CLASS respected already? You could add syn_class:unique and syn_immune_class:unique to each mutually exclusive syndrome. Or I am mixing up syndromes and interactions again. ^^

[Deon]

SYN_IMMUNE_CLASS makes creature totally immune to a syndrome, that's not something I need.
And I want it not to stack the SAME syndrome.

Now every time a syndrome is refreshed, it stacks instead of checking if it's already there which leads to weird peaks.

[Deon]

I've found the problem with SC_WORLD_LOADED.

When you go into Travel mode, it stops counting dfhack.timeout which is supposed to repeatedly call the script, right?