Print

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

[Roses]

Those spawnflows look interesting to me. I know the first number is the type and the fourth number is the size, but I thought the second and third number were material type and subtype. Won't that make the dust and such spawned different for each persons raws?

[Warmist]

Those spawnflows look interesting to me. I know the first number is the type and the fourth number is the size, but I thought the second and third number were material type and subtype. Won't that make the dust and such spawned different for each persons raws?

They are used only for some types of flow. But yes in principle you need to get materials from raws (i.e. using dhfack.matinfo)

[Raidau]

Roses, could you please add position.code and profession conditions to your addsyndrome script?

I scanned your code but thats too complicated for me. Im currently working on quests and equipment generation for important units in adventure mode, but my own scripts are a bit.. unoplimized, since syndrometrigger has troubles handling many syndrome additions per a single frame

[Roses]

What do you mean position.code and profession conditions?

[Raidau]

What do you mean position.code and profession conditions?

add to this list of arguments

Code: [Select]

[SYN_CLASS:affected class]
[SYN_CLASS:affected creature]
[SYN_CLASS:affected syndrome class]
[SYN_CLASS:required tokens]
[SYN_CLASS:immune class]
[SYN_CLASS:immune creature]
[SYN_CLASS:immune syndrome class]
[SYN_CLASS:forbidden tokens]
following:

Code: [Select]

[SYN_CLASS:affected noble position]
[SYN_CLASS:affected profession ID]
where affected noble position is compared with dfhack.units.getNoblePositions(unit)[1].position.code
since nobles dont get several positions in worldgen, checking only [1] must be sufficient

and affected profession ID is unit.profession

[Roses]

Yeah I can look at adding those checks. I should probably start to think about a better way to pass arguments into the function though. Right now it already wants 12 inputs, which I think is already too many.

Maybe I can make it so you don't need to fill them in with NONE if you want to ignore them. (Something like putting AC_blah for affected class and such)

[Putnam]

I think it'd just be better to check for all positions.

[IndigoFenix]

Has anyone managed to propel a creature upwards, in an arc?  Giving the z-velocity value a negative or a positive number seem to do the same thing.

[Raidau]

I have an error when i try to use addsyndrome with radius:

Code: [Select]

Invoking: addsyndrome NB_SYN_PANIC 18 100,100,0 all NONE NONE NONE NONE NONE NONE NONE NONE
...ckr4\Dwarf Fortress 0.34.11\hack\scripts/addsyndrome.lua:265: attempt to call a userdata value
stack traceback:
...ckr4\Dwarf Fortress 0.34.11\hack\scripts/addsyndrome.lua:265: in function 'effect'
...ckr4\Dwarf Fortress 0.34.11\hack\scripts/addsyndrome.lua:287: in main chunk
(...tail calls...)
When radius is -1,-1,-1 it works

[Roses]

Has anyone managed to propel a creature upwards, in an arc?  Giving the z-velocity value a negative or a positive number seem to do the same thing.

I thought I had tested it out (getting a dwarf to move up in z levels and then come crashing down), but I might have been mistaken. Have you even tried with very large z values?

I have an error when i try to use addsyndrome with radius:

When radius is -1,-1,-1 it works

Error on my part, I fixed it in the -1,-1,-1 case but forgot to fix it in the other case. If you want to fix it yourself you can just replace line 265 with line 255. Will upload the fixed version shortly

[IndigoFenix]

Has anyone managed to propel a creature upwards, in an arc?  Giving the z-velocity value a negative or a positive number seem to do the same thing.

I thought I had tested it out (getting a dwarf to move up in z levels and then come crashing down), but I might have been mistaken. Have you even tried with very large z values?

Yeah, it does the same thing with large positive z values as it does with large negative ones - slams the creature into the ground hard, but doesn't give it any air time.  I was hoping to use this script together with a soft, padded landing area to make an 'aerial transport' system.  Doesn't work though.

[Roses]

Hmm, interesting (and unfortunate). Maybe there is another tag somewhere that needs to be set? Do dwarves ever get air time in vanilla for any reason? I suppose you could just transport them up a few z levels and then give them a velocity in the x or y direction.

[IndigoFenix]

Dust attacks can propel creatures into the air, so it must be possible.

[Raidau]

I think i have some progress, i created a script based on changefixed, but now  it checks unit's noble position and then adds item of specified type, subtype and material in inventory to a specified bodypart:)
test interaction for source of that script looks like this:

Spoiler (click to show/hide)

Code: [Select]

[INTERACTION:LOOT_SOURCE_CIV]
[I_SOURCE:CREATURE_ACTION]
[I_TARGET:A:CREATURE]
[IT_LOCATION:CONTEXT_CREATURE]
[IT_CANNOT_HAVE_SYNDROME_CLASS:LOOT_GIVEN]
[I_EFFECT:ADD_SYNDROME]
[IE_IMMEDIATE]
[IE_TARGET:A]
[SYNDROME]
[CE_SPEED_CHANGE:SPEED_PERC:100:START:0:END:1]
[SYN_CLASS:\COMMAND]
[SYN_CLASS:multicmd]
----LORD---- {
script [SYN_CLASS:condloot]
function [SYN_CLASS:posloot]
unit id [SYN_CLASS:\UNIT_ID]
radius [SYN_CLASS:1000,1000,1000]
not used [SYN_CLASS:1]
target [SYN_CLASS:all]
affected class [SYN_CLASS:NONE]
affected creat [SYN_CLASS:NONE]
affected syn cl [SYN_CLASS:NONE]
required tokens [SYN_CLASS:NONE]
immune class [SYN_CLASS:NONE]
immune creat [SYN_CLASS:NONE]
immune syndrome cl [SYN_CLASS:LOOT_GIVEN]
forbidden tokens [SYN_CLASS:NONE]

item type, [SYN_CLASS:WEAPON]
subt, [SYN_CLASS:ITEM_WEAPON_SWORD_LONG]
mat, [SYN_CLASS:STEEL]
minq, [SYN_CLASS:5]
maxq, [SYN_CLASS:5]
npos, [SYN_CLASS:LORD]
sharp,optional [SYN_CLASS:1]
bp,optional [SYN_CLASS:22]
use,optional [SYN_CLASS:1]
[SYN_CLASS:;]}
----MONARCH---- {
script [SYN_CLASS:condloot]
function [SYN_CLASS:posloot]
unit id [SYN_CLASS:\UNIT_ID]
radius [SYN_CLASS:1000,1000,1000]
not used [SYN_CLASS:1]
target [SYN_CLASS:all]
affected class [SYN_CLASS:NONE]
affected creat [SYN_CLASS:NONE]
affected syn cl [SYN_CLASS:NONE]
required tokens [SYN_CLASS:NONE]
immune class [SYN_CLASS:NONE]
immune creat [SYN_CLASS:NONE]
immune syndrome cl [SYN_CLASS:LOOT_GIVEN]
forbidden tokens [SYN_CLASS:NONE]

item type, [SYN_CLASS:ARMOR]
subt, [SYN_CLASS:ITEM_ARMOR_BREASTPLATE]
mat, [SYN_CLASS:GOLD]
minq, [SYN_CLASS:5]
maxq, [SYN_CLASS:5]
npos, [SYN_CLASS:MONARCH]
sharp,optional [SYN_CLASS:1]
bp,optional [SYN_CLASS:0]
use,optional [SYN_CLASS:2]
[SYN_CLASS:;]}
----CUSTOM_BANDIT_LEADER---- {
script [SYN_CLASS:condloot]
function [SYN_CLASS:posloot]
unit id [SYN_CLASS:\UNIT_ID]
radius [SYN_CLASS:1000,1000,1000]
not used [SYN_CLASS:1]
target [SYN_CLASS:all]
affected class [SYN_CLASS:NONE]
affected creat [SYN_CLASS:NONE]
affected syn cl [SYN_CLASS:NONE]
required tokens [SYN_CLASS:NONE]
immune class [SYN_CLASS:NONE]
immune creat [SYN_CLASS:NONE]
immune syndrome cl [SYN_CLASS:LOOT_GIVEN]
forbidden tokens [SYN_CLASS:NONE]

item type, [SYN_CLASS:TOOL]
subt, [SYN_CLASS:NB_ADV_CLOSED_BACKPACK]
mat, [SYN_CLASS:RUSTY_IRON]
minq, [SYN_CLASS:1]
maxq, [SYN_CLASS:3]
npos, [SYN_CLASS:CUSTOM_BANDIT_LEADER]
sharp,optional [SYN_CLASS:0]
bp,optional [SYN_CLASS:0]
use,optional [SYN_CLASS:2]
[SYN_CLASS:;]}

/SYN_CLASS:printArgs]
/SYN_CLASS:\UNIT_ID]
/SYN_CLASS:"loot source performed"]
/SYN_CLASS:;]

[SYN_CLASS:addsyndrome]
inorganic [SYN_CLASS:NB_SYN_LOOT]
[SYN_CLASS:\UNIT_ID]
radius [SYN_CLASS:1000,1000,1000]
[SYN_CLASS:all]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:LOOT_GIVEN]
[SYN_CLASS:NONE]
[SYN_CLASS:;]

[SYN_CLASS:addsyndrome]
inorganic [SYN_CLASS:NB_SYN_LOOT]
[SYN_CLASS:\UNIT_ID]
radius [SYN_CLASS:-1,-1,-1]
[SYN_CLASS:all]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:NONE]
[SYN_CLASS:LOOT_GIVEN]
[SYN_CLASS:NONE]

Yeah it would use some optimization

[Roses]

What I think I am going to do is put a check in the arguments section, if it sees you have all the arguments listed it will just take them as they are (basically it behaves exactly as it does now, so that it is backwards compatible). Then if there are less arguments than expected it will figure out which are which by some tag and set all others to NONE. That will make all of those SYN_CLASS:NONE tags unneeded.