Print

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

[Roses]

Thats good to hear, I guess I will just ask him then and see if the interactions user is stored anywhere. If it is, great!, if not I will jury rig something with announcements and put a big asterisk on all the things that require the users id.

EDIT: Contacted Mr. Adams, he said that the information of who caused the syndrome is not stored anywhere. I will continue to try and make the announcements method more reliable, and make mention of all the flags what require the users id.

[Roses]

Preview:

This example will increase the strength of every Automaton in a 10x10 square by 100 + 10*#Automatons. These types of scripts can be used to create buffs that depend on number of units and such.
wrapper \UNIT_ID script@changeattributes args@STRENGTH;!UNIT;fixed;!VALUE value@stacking;allowed;100;10 radius@10,10,2 acreature@AUTOMATON;BASIC,AUTOMATON;LEADER

Almost ready to put out my new scripts, but there are a couple more additions. For those interested full details on the wrapper script can be found here. There are lots of new features and a lot of new possibilities.

[Meph]

Reminds me of the Slivers of MtG. Each one has a ability and gives this to every other Sliver... one is weak, a few are strong, a lot are unstoppable.

[Roses]

Thats sort of where my idea came from. I wanted my Automatons to have a leader class that could link multiple nearby units to vastly improve combat performance. Kill the leaders and the rest become much easier.

EDIT: Here's another fun one I just finished

changebody temperature \UNIT_ID category/HAND+category/FEET fire

This will set a units hands and feet on fire. Similarly if you change the fire to a number, it will set the units hands and feet to that temperature. Punch with fists as cold as ice!!! (Note that I haven't actually done any testing with this yet in combat, I don't know if a punch from a unit with hands on fire will set an enemy on fire)

[Meph]

"Your" automatons? What are you working on?

[Roses]

"Your" automatons? What are you working on?

I decided that instead of using MWDF's automatons I would create my own. They differ from other races by each class having a specific role. You will want to choose between taking out the leaders to stop the buffs, the creators to stop new automatons from being built, the salvagers to stop the repairing and enhancing of nearby automatons, or just go after the fighters. Hopefully it all works out as I am imagining. I have had to write a lot of scripts and expand the functionality of my wrapper script. But so far almost everything is working.

[Meph]

Sounds a lot better than what I made. Are they designed as a purely hostile race? You might also check the older Automaton Fortress for ideas.

[Godlysockpuppet]

Could I have an example interaction in which a minimum amount of FOCUS and WILLPOWER are needed to use an interaction? I'm no good with this Thanks

[Putnam]

Could I have an example interaction in which a minimum amount of FOCUS and WILLPOWER are needed to use an interaction? I'm no good with this Thanks

That would have to be an interaction that a creature uses on itself repeatedly until the syndrome finally procs due to the sufficient focus and willpower, at which point they will be able to use the interaction.

[Godlysockpuppet]

Could I have an example interaction in which a minimum amount of FOCUS and WILLPOWER are needed to use an interaction? I'm no good with this Thanks

That would have to be an interaction that a creature uses on itself repeatedly until the syndrome finally procs due to the sufficient focus and willpower, at which point they will be able to use the interaction.

I was thinking more along the lines of, all creatures of a race have an interaction, but only those with say, a willpower AND focus => 2000 can use it. I was thinking of something this; from the first post;

Spoiler (click to show/hide)

[SYN_CLASS:selected]
[SYN_CLASS:\UNIT_ID]
[SYN_CLASS:script@changefixed,changepercent]
[SYN_CLASS:args@exhaustion;UNIT;10000,blood;UNIT;-25]
[SYN_CLASS:radius@circle;5,5,2]
[SYN_CLASS:aclass@GENERAL_POISON]
[SYN_CLASS:mental@max;WILLPOWER;2000]

unless you meant something else? If so, I'm not following :p

[Putnam]

All creatures of that race have an interaction that gives them a syndrome when used on theirself. This syndrome has the proper SYN_CLASSes for "min willpower and focus" and gives them the interaction you want them to be able to use.

[Roses]

Sounds a lot better than what I made. Are they designed as a purely hostile race? You might also check the older Automaton Fortress for ideas.

Yeah, they are a kill all organics race. No pets, no trade, just sieges. I have been looking through various peoples robot-type creatures and entities for ideas about ethics and such, as well as balancing. Right now I am thinking about how best to incorporate worn items and such, since the calculations for combat give a severe handicap to anyone not wearing clothing, even if it is just a tiny amount.

Could I have an example interaction in which a minimum amount of FOCUS and WILLPOWER are needed to use an interaction? I'm no good with this Thanks

The exact request is a little complicated. It depends on if are wanting the interaction to target yourself or someone else, and what you want the interaction to do. Let me know more about what you would like from the interaction and I can make you an example.

EDIT: I missed the replies, sorry. Yes Putnam is correct, the easiest way to do it would be to use two interactions, one structured with

Code: [Select]

[SYN_CLASS:\COMMAND]
[SYN_CLASS:selected]
[SYN_CLASS:script@addsyndrome]
[SYN_CLASS:args@!UNIT;NAME_OF_INORGANIC_WITH_SYNDROME_TO_GIVE_INTERACTION]
[SYN_CLASS:mental@min;WILLPOWER;2000,min;FOCUS;2000]
Then your inorganic with the syndrome will have a CAN_DO_INTERACTION tag that would behave exactly like normal.

[Godlysockpuppet]

That looks perfect! Thank to you both!
Okay, last thing. I'm trying to make a boil away stone, that will be created in a reaction. This stone should have the syndrome so that if a creature inhales it they gain an interaction, and if their willpower/focus is high enough, this interaction gives them another interaction which is a combat spell they can use from then on. Will this work?

Spoiler (click to show/hide)

[INORGANIC:TEACHSPELL]
    [USE_MATERIAL_TEMPLATE:STONE_VAPOR_TEMPLATE]
    [STATE_NAME_ADJ:ALL_SOLID:Teach spell]
    [STATE_NAME_ADJ:LIQUID:Teach spell]
    [STATE_NAME_ADJ:GAS:Teach spell]
    [SYNDROME]
    [SYN_CLASS:\COMMAND]
    [SYN_CLASS:selected]
    [SYN_CLASS:script@addsyndrome]
    [SYN_CLASS:args@!UNIT;TEACHSPELLSTONE] > The stone that gives the creature the final "combat spell" interaction
    [SYN_CLASS:mental@min;WILLPOWER;1000,min;FOCUS;1000]
    [SYN_NAME:teach spell]
    [SYN_CONTACT]
    [SYN_INHALED]
    [SYN_AFFECTED_CREATURE:DWARF:MALE]
    [DISPLAY_COLOR:4:4:1][TILE:'*']
    [MELTING_POINT:0]
    [BOILING_POINT:0]
    [SOLID_DENSITY:55520]
    [MATERIAL_VALUE:0]

[Roses]

If you are already using DFHack, you might as well through a [SYN_CLASS:\AUTO_SYNDROME] in before the \COMMAND one. That will make sure that the unit will get the interaction without having to worry about the difficulties of boiling rocks. Also, I forgot to include a [SYN_CLASS:\WORKER_ID] which should come right after [SYN_CLASS:selected] (\WORKER_ID if being performed in a reaction, \UNIT_ID if being performed in an interaction)

[Godlysockpuppet]

If you are already using DFHack, you might as well through a [SYN_CLASS:\AUTO_SYNDROME] in before the \COMMAND one. That will make sure that the unit will get the interaction without having to worry about the difficulties of boiling rocks. Also, I forgot to include a [SYN_CLASS:\WORKER_ID] which should come right after [SYN_CLASS:selected] (\WORKER_ID if being performed in a reaction, \UNIT_ID if being performed in an interaction)

Yeah, I added autosyndrome already Thanks for the help.
Oh, could I also be given a quick example interaction using the "propel" script, which throws units away from the user?