• 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

FATE Core bug?

EightBitz

Well-known member
Is this a bug, or am I missing something?

Part 1:
I create a stunt.
I set Uniqueness to "No" so multiple instances can be added.
I allow multiple ranks.
I leave the refresh cost at a default
I add an eval script with a timing of Pre-Traits, 100:
Code:
herofield[acRefrStnt].value -= field[stNumber].value

As you can figure out, I'm sure, this means that however many ranks I add on however many instances, the cost for this stunt is always 0. And this works. When I look at the top of my screen as I add ranks and instances, the "Refresh Rate" remains constant. And when I look at the bar above the stunts list, the refresh value remains constant.

But say I flip that around.
I configure the stunt to have a cost of 0, and a bonus of 1.
Then, change the eval script to:
Code:
herofield[acRefrStnt].value += field[stNumber].value

I would expect to get the same results, but I don't. The refresh rate at the top still remains constant. But in the bar above the stunts list, the refresh value goes further and further negative as I add ranks and instances.

I know I can set a stunt to cost 0 refresh, but that's not my goal here. I'm looking to make this part of a larger eval script.
 
The refresh bonus of a stunt is added directly to the base refresh rate, instead of offsetting the refresh rate reduction from stunts.
 
Back
Top