• 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

Does this look right?

ErinRigh

Well-known member
Just looking at a line of code

Code:
        ~ Count the number of times manually added
        field[abValue].value = field[abValue].value + hero.tagcount[HasAbility.cGldIgPain]

where abValue is the number of times that cGldIgPain has been taken

my question is, is this expression correct or am I missing something?
 
Nothing logically wrong with that math. Other than "HasAbility" tags are not placed until really late in Final or Render phase even. Its not very useful for doing much with the tag.

You would need to use Ability.cGldIgPain tag instead. But that goes on to the hero as soon as the Pick becomes live and does not care about being enabled or disabled or any other logic.
 
I've had that problem before, its annoying.
Generally, I create a dummy special then that counts the number of times I've taken a class custom. And then you can use the class custom to remotely change the abValue of the dummy special.


hero.childfound[someclassspecial].field[abValue].value =+ 2

That way each time you add the class special it simply adds to the dummy special, sneak attack and many special attacks use that method. It works well for purely display, situational and skills. Less well when the value is needed by other things such as attacks and saves, but can be very effective.
 
If you really need to be counting something its most likely better to just place a custom tag on the hero yourself. That way your ability Things can easily set the tag when its valid or not. Tag counting is very efficient and can be used in ALL logic where a Pick's value is limited.
 
@TobyFox2002 I was re-thinking about this and your most likely correct in that using another Pick's field value would be easier than tags when starting out. Good idea! :)
 
Back
Top