• 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

Template Configurable Auto-Add Error

TobyFox2002

Well-known member
I have set up a mechanic to automatically add a new configurable, called "Vampire." to the hero EVERY time the hero adds the vampire template.

This all goes well and good right up until the moment goes to remove the template (and in theory the configurable bootstrapped to it.) However, if the user ever removes the vampire template the program throws a hissy fit.

See attached image for the list of errors.

The strange thing is, if I delete the character, and start again the program gives no errors or warnings.

Not sure whats happening with, but its bugging the heck out of me.
 

Attachments

  • Vampire Error.png
    Vampire Error.png
    435.4 KB · Views: 11
I have set up a mechanic to automatically add a new configurable, called "Vampire." to the hero EVERY time the hero adds the vampire template.
Can you define this within HL script? Let me see if I get this right. The Mechanic bootstraps the configurable. But how is the configurable logic setup to be displayed or not? Are you using a bootstrap condition?

This all goes well and good right up until the moment goes to remove the template (and in theory the configurable bootstrapped to it.) However, if the user ever removes the vampire template the program throws a hissy fit.
Sort of hard to tell from the errors. I think whatever is suppose to stop the configurable from displaying is not working. Meaning the configurable is still live even though the template is gone.

Need to see the timing/script logic of how your are controlling the bootstrap of the configurable.
 
How its being bootstrapped is a little complicated, perhaps more than it needs to be..

I have a configurable named, Template Configuration Tabs [meTempCfgA]. THis will be used to bootstrap additional options to several templates that modify core templates with additional options.

Bootstrapped to this mechanic is Template Cfg Bootstraper [raRVTemCfg]. raRVTemCfg has an eval script and a boostrap with a condtional.

First/100

Code:
      ~ If template doesn't exist, Get out Now!
      if (hero.childlives[tmVampire] <> 0) then
         field[abValue].value += 1
~         debug "we are a vampire"
      endif

Which bootstraps cfgRVVamp Conditional: fieldval:abValue = 1 First/150.

Now, I had been using Racial customs. But I didnt like how the secondary custom abilities were being shown on the Background tab. So I switched to class custom abilities by editing the file by hand in notepad++ (changing the compset="" of the thing from Racial to Class).

Thats when I received the error. I'd rather have them as class customs, but ultimately I could not figure out a way to fix the problem so I had to switch it back.

I realize this is more information than I had, but, much of it I figured out after I posted. And havent been back to the computer until a bit ago. But thats what I have sofar.
 
After re-reading the error messages and your above post. I am thinking "maybe" I know what is happening.

Let me know if this is the steps:
1) New character add a vampire
2) The new configurable appears.
3) You select Class Custom Abilities X & Y.
4) You remove the Vampire template and HL toss you those errors?

If that is the case my guess would be that the Custom Abilities X & Y are still live on the hero but are no longer associated to a Live Configurable (ie no Pick). Meaning the "Focus" to the configurable pick fails and you get the errors.

Again if the above is all true you will need to remove the Custom Abilities X & Y BEFORE you remove the Vampire template.
 
All true.

I'd really rather not have that be the case. It seems like an unessisary step that is only going to invite confusion. If there is no way around it I may just hide all of this and wait to implement it when a better way comes along as much as it pains me to do it with the work that has gone into this.

If I could do a one time notify message to players when they pick the class telling them how to remove it, that would be one thing. But beyond that, its just asking for trouble to have that kind of error.

I'll figure a way.

On a semi-unrelated note, is there a way to hide a racial ability from the Racial, Template & Faction Abilities section on the Background Panel.
 
Back
Top