• 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

Starting attributes at 0 with no CP refund?

EightBitz

Well-known member
With a new skeleton system, attributes have a minimum value of 1, and CP has a default value of 250.

I know how to change the minimum value of the attribute to 0, but this refunds CP points.

I would like a baseline of all attributes with a value of 0, and no CP refunds, so the CP value remains at 250.

Looking through the various dat files, though, I can't find where or how to change this. It's easy enough to change the starting CP value to compensate, but is that the best way? (If so, that's fine.) Or is there a way to baseline the attributes with no CP refund?
 
I think this should do it.....
<component
id="Attribute"
name="Attribute"
autocompset="no">

<!-- Attributes have a minimum trait value of 1 -->
<eval index="1" phase="Initialize" priority="3000"><![CDATA[
field[trtMinimum].value = 0
]]></eval>

<!-- Each attribute point above one that is allocated by the user costs 7 CP -->
<eval index="2" phase="Traits" priority="10000">
<before name="Calc resLeft"/>
<after name="Bound trtUser"/><![CDATA[
hero.child[resCP].field[resSpent].value += field[trtUser].value * 7
]]></eval>

</component>
The values should start at 0, and only Cost CP as increase. (before, the (field[trtUser].value -1) * 7 the Spent would be -7 for a 0, and since the the CP Cost is -Spent, it would add 7 CP instead. :)
 
Last edited:
I think this should do it.....
The values should start at 0, and only Cost CP as increase. (before, the (field[trtUser].value -1) * 7 the Spent would be -7 for a 0, and since the the CP Cost is -Spent, it would add 7 CP instead. :)

Nope. That was exactly the initial change I made to set the attributes to 0. It still refunds CP.
 
Back
Top