Setting an Attribute to a Specific Value (ie. "Feeblemind" spell)

[GodPole]

Greetings all,

I have been experimenting with entering many of the Buffs and "Snuffs" (negative Buffs, ie. "Bane") spells as Conditions accessible via the Adjustments tab. I have found this a great way to let HL calculate ALL of the effects of a Buff/Snuff on an ally or enemy.
However, I have run into a snag when trying to implement the spell "Feeblemind". I have had no problem up to this point applying bonuses or penalties to existing stat values, but this spell is requiring me to hard-set the character's INT and CHA to a value of 1; regardless of what bonuses may or may not be there.
I know I have screwing the syntax up somewhere, but there isn't really anything in the docs or tutorials detailing how to do this; everything there focuses on bonuses and penalties.
Has anyone done this and can give me some pointers?
Thanks!

-GP

[bodrin]

I don't have hero lab in front of me at the moment so I'm only guessing! Have a look at an undead template, Zombie, skeleton these set Con to no score as undead don't have constitution. Maybe the info contained can shed some light for you.

[Mathias]

Phase/Priority: Pre-attributes/any

 
hero.child[aINT].field[aNormForce].value = 1
hero.child[aCHA].field[aNormForce].value = 1

[Kaelryk]

You should be able to achieve the result you want with something like this for an eval script:

~ If we're in output mode, don't do anything
doneif (state.isoutput <> 0)

~ If we're not enabled, get out now
doneif (field[pIsOn].value = )

~ Set INT & CHA to 1
hero.child[aINT].field[ModCirc].value = 1
hero.child[aCHA].field[ModCirc].value = 1

You may need to fiddle with the 'phase' & 'priority' settings to get it to work properly.


Oops! I type too slow!

[GodPole]

You people are AWESOME!!!

Mathias, is this documented somewhere that I missed?
I've looked all over the docs that I know about and can't find any reference to "aNormForce".


Thank you very much!!!

-GP

[Mathias]

It was originally added for the INT of arcane familiars, but was ditched in favor of a minimum INT, so there's nothing else in the files that actually uses this mechanism, which is why it isn't documented anywhere.

Here's the only way I know of to find it (without access to the raw files) (and this is a useful tool in other situations, anyway):
In the debug menu, make sure that the first option, "Enable Data File Debugging" is checked.
Then, right-click on the INT attribute on the basics tab (or the basics summary panel), and choose "Show debug fields for Intelligence" - that will show you all the fields that exist for intelligence, and their final values.

You can also use the floating info windows option at the bottom of the debug menu, then "Show Selection Fields" to get at the same list of fields (this becomes important when you're looking at the fields of a class - there isn't anything on a character you can right-click when trying to figure something out in that case).

[GodPole]

...speechless.



This is the Holy Grail.


Thank you!!!
Thank you!!!

[GodPole]

Ok,

The help you guys have given me has been great, but I have run into a small snag.

Apparently, the aNormForce modifier worked great at setting the INT and CHA to 1 when I select the Feeblemind condition, however, when I unselect it, the INT and CHA don't go back to what they were before; they stay at a value of 1.
Now, I think this is because the aNormForce actually changes the value and doesn't actually act as a "modifier". Is this a correct assumption, or is there some setting I am omitting to get that to work.

In the meantime, I was trying to work out a script that would actually calculate the correct penalty to drop someone's INT and CHA to 1 so that unselecting it would "undo" the penalty, reverting the INT and CHA back to their original values.
Here is what I have so far:


~ If we're in output mode, don't do anything
doneif (state.isoutput <> 0)

~ If we're not enabled, get out now
doneif (field[pIsOn].value = 0)

var feebpenINT as number
var feebpenCHA as number

feebpenINT = (hero.child[aINT].field[aFinalVal].value - 1)
feebpenCHA = (hero.child[aCHA].field[aFinalVal].value - 1)

#applypenalty[Penalty, hero.child[aINT], feebpenINT]
#applypenalty[Penalty, hero.child[aCHA], feebpenCHA]

It works exactly as I expected, but it doesn't decrease the attributes by their original value (aFinalVal?) minus 1, it only decreases the value by 1. So if my INT/CHA is 10, then when I check Feeblemind, it only reduces them to 9. Something must be wrong with my feebpenINT and feebpenCHA variable calculations but, for the life of me, I can't see what.
Can I have a 2nd set of eyes look at this and tell me what I am overlooking?

Thanks.

GP

[Mathias]

You're right about aNormForce - it forces the user value to that value, which doesn't reset.

rather than using #applypenalty, you'll have to modify aFinalVal - by the phase and priority that aFinalVal has been calculated, Penalty has already been incorporated into aFinalVal, and isn't checked again.

Note: Penalty is a non-stacking field, so rather than using #applypenalty, which is used for those fields that do stack, just do it this way:

 
hero.child[aINT].field[Penalty].value -= feebpenINT

Or rather:

phase: Attributes, priority: 150000

 
~ If we're in output mode, don't do anything
doneif (state.isoutput <> 0)
 
~ If we're not enabled, get out now
doneif (field[pIsOn].value = 0)
 
hero.child[aINT].field[aFinalVal].value = 1
hero.child[aINT].field[aModBonus].value = -5
 
hero.child[aCHA].field[aFinalVal].value = 1
hero.child[aCHA].field[aModBonus].value = -5

Sorry for not thinking of this script earlier

[GodPole]

Thanks Mathias!
This worked perfectly.

Just out of curiosity, is there a reason the #applypenalty script didn't work?

-GP