PDA

View Full Version : Charges...



Ben Seeman
Sep 22nd, '03, 04:05 PM
I built a power that I want to have 2 clips of 16 charges. So I selected 16 charges and the clips option changed to 4, which is fine. I checked the box and then typed over the '4' with a '2'. But it got switched backto a '4'.

Am I missing something?

Simon
Sep 22nd, '03, 04:19 PM
Yeah...the number of clips are automatically calculated based on the advantage level.

16 Charges is a +0 Advantage. Every +1/4 on the Clips Adder gives you x4 the number of clips (since the overall value of the Charges is an Advantage), so HD is automatically assigning the 4 Clips.

If you want a number other than what is being assigned, you'll need to put that in the notes for the time being.....

Charges is something that is on my list of "things to work on"....when I do, I'll see if there's a more elegant/flexible way to handle the number of clips.

Simon
Sep 22nd, '03, 04:55 PM
OK...here's what I've got:

On just about any of the "dynamic" displays (things like Armor Piercing, which adjust their display to indicate the number of levels purchased), I've got it adjusting dynamically based on the levels <i>unless</i> you change the value. Once you change the value manually, it will stay where it is until you "re-sync" the value with the levels.

This should give people the best of both worlds....though it may be a trifle confusing for folks that are just messing around.

Charges are a bit of a different story, however. The deal with the number of clips is extremely tricky and really needs to remain the way it is (always being calculated by the program). The reason is that the number of clips needs to adjust its value based not only on the number of levels of clips purchased, but also on the rest of the structure/value of the Charges Limitation (since the multiplier changes from x2 to x4 when Charges turns into an Advantage).

This kinda throws a wrench in the whole works for "freezing" the value.

I'll keep looking at Charges for a bit and see if there's anyway to make it freeze the value when you change it manually, but I wouldn't plan on it at this point.