• 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

rSpec2ndSi

Frodie

Well-known member
I working on this code

Code:
    ~ If not human get out now
      doneif (#hasrace[rHuman] = 0) 

     ~set our focus to the hero's race
      perform hero.findchild[BaseRace].setfocus
      doneif (state.isfocus = 0)
      ~ Give one Nationality
      focus.field[rGiveSp2nd].value +=1
      perform focus.assign[Helper.OptCustom]
      focus.field[rSpec2ndSi].text = "Nationality"

It gives the bonus fine, but it will not change the name and I get this error:

Syntax error in 'eval' script for Thing 'mechFGMPNa' (Eval Script '#2') on line 1
-> Only derived fields can generally be modified via scripts (field 'rSpec2ndSi')

It's just a text field, any ideas?
 
Ok, seems weird, you change all the others, just not that one. Maybe it's a bug. I'll send it in.
 
Well, I heard back from tech support, and they said that is a closed field. Seems weird that you can re-name rSpecSing, rSpecName and rSpec2ndNm but not rSpec2ndSi.

Anyway they told me to ask here for help. So seeing rSpec2ndNm works but will not show. Any ideas how to fool HL into thinking it multiples and not single abilities so it will use the multiple name?
 
I'd build this as a configurable bootstrapped from a mechanic, rather than trying to use the racial fields.
 
Yea, didn't really want to do that. I thought about just moving them to the primary slot, (I can rename the field there). But I couldn't find a good way to hide all the Ethnicity with a loop.
 
Even if you could use the 2nd racial custom table, there is still several common races (Tiefling and Aasimar) which can use both so you'd run into the same issue as with the primary. Configureable is the way I'd go too.

That said, we'll switch the field from static to derived so that it can be affected by scripts.
 
Even if you could use the 2nd racial custom table, there is still several common races (Tiefling and Aasimar) which can use both so you'd run into the same issue as with the primary. Configureable is the way I'd go too.
Yep ran into this myself with the Eberron setting where I was trying to only allow Eberron Ethnicities. I accidentally removed the ability for the Tiefling/Aasimar to pick there heritages which is in the same place as Ethnicity.

A Configureable is the safest route as future changes/books won't destroy what you do.
 
Back
Top