• 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

Making Edges cost two advances?

Hi,

the day after ragnarok introduces a new concept where certain edges (arcane Backgrounds) cost two advances (lvl ups) instead of the usual one.

Any idea how to implement this in Hero Lab?
 
I'm going to modify the core SW data files to accommodate this automatically.
 
So you want each increase to cost two slots during creation, but how would this be handled during advancement?

I'm not sure this will be possible to do automatically due to the different way in which attributes are advanced versus edges. Let me know exactly what you want it to do and I'll see what I can make happen.
 
There are hindrances that make you pay two slots during creation and two advancements during the game to raise the linked attribute.

You could just do something similar with edges.

How is advancement internally solved - does it provide some kind of currency that can be spend on the different options?
 
There are hindrances that make you pay two slots during creation and two advancements during the game to raise the linked attribute.

I'm aware of hindrances that cost two slots during creation. But I'm *not* aware of any that require two advancements to raise an attribute. Where are they defined? I'm not sure that the current structure would allow for that to be handled without some re-work.

How is advancement internally solved - does it provide some kind of currency that can be spend on the different options?

Yep. Everything has a "currency". Hindrances and rewards have their own currency that offset one another. Experience translates to a number of advancement slots, which is a form of currency that gets consumed by the selection of advancements.

I've only seen advancements that consume one slot so far, hence the current limitation within the data files.
 
More and more Settings use that unfortunately (MARS, Runepunk, (I think) Hellfrost etc.). It is one mechanism to balance race traits from the SW toolkits and has found a lot of users due to that.

Being able to include that would be really really useful.

So far, I have only seen attribute raises taking two advances, but it would be possible to imagine Edges or double priced Skill-ups as well.
 
OK, the imminent update will include the ability to charge two slots for edges and have a race (or other mechanism) cause an attribute to cost two slots.
 
To have a racial ability cause an attribute to cost two slots, you'll need to write a one-line script, and the script must occur *before* the Effects phase. For example, let's assume we have a "Scrawny" racial ability that causes Strength to cost two slots. The resulting racial ability definition might look like the following:

Code:
<thing
  id="abScrawny"
  name="Scrawny"
  compset="RaceAbil"
  isunique="yes"
  description="blah blah blah">
  <eval index="1" phase="Setup" priority="5000"><![CDATA[
    hero.child[attrStr].field[trtCost].value = 2
    ]]></eval>
  </thing>

That's all there is to it. Give a holler if you run into any problems putting this stuff to work.
 
Okay, since I am working on Ragnarok rules, I finally realized I needed to address this very problem. Arcane Backgrounds cost two slots. So I read through this thread and I see Rob mentions a fix for this. So the question is, how do we accomplish this? I looked around the editor, there isn't a nice field to put in Slot Cost for an edge.

I tried an Eval Script:

perform #resspent[resEdge,+,field[edgCost].value += 2

That gave me errors. So, how do we double the slot cost for an Edge? :)
 
Try this: (It would charge an extra point)
Code:
perform #resspent[resEdge,+,1,"Name of Edge"]
But the better way would be: (This would make it cost one more)
Code:
field[edgCost].value += 1
 
Both of the suggestions by CapedCrusader will work nicely. However, the key limitation of both those suggestions is that the edge needs to be fixed up via a script, which means you need to worry about timing. You can also change the basic cost directly on the *thing* definition via the Editor.

To do this, bring up your edge in the Editor. At the top right, click on the Fields button. Click the button to add a new field to the list. Enter the field id of "edgCost" and a value of "2", then click the OK button at the bottom. Now save your edge and test it. This should give it a cost of 2 slots.

Hope this helps....
 
Thanks Rob, that did it.

And thanks to CapedCrusader as well. That would also work.

I am seeing the end to my Ragnarok file finally :)
 
Back
Top