• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Sub-Charges problem

Lawful_g

Well-known member
I am trying to set up a special that has 3 different forms, so I created the special (Blessings of Kord), created the 3 sub specials (+2 Luck bonus to Saves, +2 bonus to Strength, or +10 to speed), and tried to make it so that using one of the lower ones uses the charge of Blessings of Kord.

The template I was using for this are staffs, which have specials bootstrapped with something under the tag button, a [ChargeUse.X] tag.

I bootstrapped the subspecials with a [ChargeUse.1] tag to the main special, but it is not working. Using a charge of any of the lowers does not use the higher.

I noticed that the old Staves all have subspecials that use the 50 charges of the main staff, but those subspecials were made using the "charges" tab in the editor, that has since been removed. Newer staves, like the ones from Pathfinder, do not even attempt this. Has something changed in HL? Is this no longer possible?
 
The problem with the ChargeUse.? tags is that the mechanics for that are incorporated into the staff component - they're not a general mechanism.

Ignore staves in Pathfinder for now - I'm in the process of switching them over to a new mechanism.

If all three specials cost 1 charge of the ability, I'd suggest just leaving out the charges on the special. If the user can't remember to subtract one use of the main thing each time they use an ability, they're "forgetting" (air quotes there) to use up arrows and wand charges, too.

If the user must pick only one version, just put the charges on each version.
 
I got it working by an Eval script that counts the number of times the ability was used and then adds that to the parent special's hChildUsed field. This example uses Turning for it's charges.

field[hTotal].value = hero.childfound[xTurning].field[hTotal].value

var used as number
used = field[hUsed].value

hero.childfound[xTurning].field[hChildUsed].value += used

if (hero.childfound[xTurning].tagis[Helper.ShowSpec] = 0) then
perform delete[Helper.ShowSpec]
perform delete[Helper.ShowCharge]
endif
 
Having just worked a lot with the Pathfinder charges, I made a mistake in my earlier post - the reason adding your thing with a ChargeUse.? tag didn't work is that it only functions to connect something to the thing that bootstrapped it. So, you'd have to have the turn undead on Cleric, and Paladin, and any other class that was added with turn undead, bootstrap all of your turn undead specials, and then figure out a way to turn them on and off depending on other picks.

The way you went about it was the way to go.
 
Back
Top