• 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

How do I do this? (Pathfinder)

Most error messages in Hero Lab will let you right-click them and copy them.

I am SO glad you told me that! Because the usr errors are gone and now I have these:

Linkage pick 'table' not located for current context
Location: 'field calculate' script for Field 'xTotalLev' near line 7
- - -
Linkage pick 'table' not located for current context
Location: 'field calculate' script for Field 'xTotalLev' near line 8
- - -
Linkage pick 'table' not located for current context
Location: 'field calculate' script for Field 'xTotalLev' near line 9
- - -
Linkage pick 'table' not located for current context
Location: 'eval' script for Component 'BaseCustSp' (Eval Script 'Calc xIndex') near line 95
- - -
Linkage pick 'table' not located for current context
Location: 'eval' script for Component 'BaseCustSp' (Eval Script 'Calc xIndex') near line 95
 
So, if you're copying error messages like that, and they're about code that you've written, we can't help you diagnose the error unless you include all the code - that way, we can count lines and see what's on line 7, which is the first step in figuring out why there's an error near line 7.
 
So, if you're copying error messages like that, and they're about code that you've written, we can't help you diagnose the error unless you include all the code - that way, we can count lines and see what's on line 7, which is the first step in figuring out why there's an error near line 7.

I figured as much. This is what you guys developed for me so far (I wish I knew how to code like this!). It's the Eval Scripts for the Custom Ability I call Studied Foe (works the same as Favored Enemy, the name change is to avoid confusion if possible). I found the only way to add another copy of Favored Enemy was to go through the Custom Ability tab, since FE doesn't appear at all under the Class Special tab, which is what I usually use to add new class features or copy and work on existing ones.

Script follows:

~ First check all classes on the hero for one with favored enemies
var foundone as number
var validclass as number
var i as number
var currlevel as number
var searchexpr as string

foreach pick in hero from Class
~We subtract 1 because arrays start at 0, so 1st level is 0 in an array.
currlevel = eachpick.field[cTotalLev].value
currlevel -= 1

~This is awkward because the number is in an array field, so we have to "walk up" the array, checking each cell (up to the current level) for a non-zero value.
for i = 0 to currlevel
if (eachpick.field[cFav1Tot].arrayvalue <> 0) then
validclass = 1
endif
next

if (validclass <> 0) then
foundone += 1

~ We also note down which classes are valid choices, for later
searchexpr = splice(searchexpr, tagids[Classes.?], " | ")
endif

~validclass has to be reset to 0 for each new class, so we can know if this class should be choosable. Otherwise, once a valid class was found, all future classes would also be valid
validclass = 0
nexteach

~stop if we did not find an appropriate class
doneif (foundone = 0)

~Now define our candidate expression. It should be mostly built in the previous foreach, we just need to add a bit onto the beginning and enclose the rest in parenthesis.
field[usrCandid1].text = "component.Class & (" & searchexpr & ")"

~If we haven't chosen any class to benefit yet, stop
doneif (field[usrChosen1].ischosen = 0)

~Since we got this far, add our own class levels to the chosen class.
~Note that since we are running this script before Levels phase, we can't rely on our normal level fields.
field[usrChosen1].chosen.field[cFav1Level].value += #levelcount[RLMonHunt]
 
Actually, I think the error doesn't lie in the code itself - there's something wrong with how you're bootstrapping things.

Check how you've organized things. Have you done any of the following (which aren't allowed):

Created something on the "Custom Ability" tab, and then bootstrapped it to anything else (Custom Abilities may only be added by the user. They may never be bootstrapped - use a Class Special instead if you want to bootstrap it).

Bootstrapped a Class Special to anything other than the following: A Class, an archetype, a Custom Ability, or a Cleric Domain
 
Actually, I think the error doesn't lie in the code itself - there's something wrong with how you're bootstrapping things.

Check how you've organized things. Have you done any of the following (which aren't allowed):

Created something on the "Custom Ability" tab, and then bootstrapped it to anything else (Custom Abilities may only be added by the user. They may never be bootstrapped - use a Class Special instead if you want to bootstrap it).

Bootstrapped a Class Special to anything other than the following: A Class, an archetype, a Custom Ability, or a Cleric Domain

You got that exactly right. Since I couldn't add this as a Class Special (it wasn't coming up on the list) I had to Bootstrap it to the pclass. Once I removed the bootstrap all the errors vanished.

How can I add the Custom Ability to the Prestige Class then without getting errors? I'm not sure where to go from here.
 
Mathias: I think he is talking about the custom special ability table not showing his custom special ability in the list to add. He probably forgot to give it a specsource tag matching that of his class.

Quistar: My advice is not to use a Custom Special, remake the ability as a Class ability and bootstrap that to your class instead.
 
Mathias: I think he is talking about the custom special ability table not showing his custom special ability in the list to add. He probably forgot to give it a specsource tag matching that of his class.

Quistar: My advice is not to use a Custom Special, remake the ability as a Class ability and bootstrap that to your class instead.

Correct. Now I get to learn what a specsource tag is! :-D
 
That's the tricky part. Favored Enemy is a checkbox ...hm, it WAS a checkbox on the Class tab. Now all I see is the "Favored Enemy Count" which lets me choose which levels I advance that ability. That being the case, should the script we've been working on go here? Or do I need to rewrite the Favored Enemy into a Class Special? Cause I have no idea how to do that and figured it was easier to work with existing script.
 
Alright, I think I am confused. I thought what you were trying to do was have your PrC stack with another class that has favored enemies? If that's not the case, what are you trying to accomplish?
 
Correct. Now I get to learn what a specsource tag is! :-D

When you make a custom special ability, the first button is "Available to Class(es)". The boxes you check there all apply SpecSource tags of the listed thing.
 
That is correct Aaron. Trying that now...yes, that is already checked for Monster Hunter. Will try adding Ranger and Slayer to that list since they share the same ability (Favored Enemy) and see if that helps.

No, no change. I'm getting "Too Many Upgrades: 1 of 0 (1 Overspent)! Same thing.
 
That is correct Aaron. Trying that now...yes, that is already checked for Monster Hunter. Will try adding Ranger and Slayer to that list since they share the same ability (Favored Enemy) and see if that helps.

No, no change. I'm getting "Too Many Upgrades: 1 of 0 (1 Overspent)! Same thing.

Mind you, now the program is ALLOWING me to add the upgrade, I just get the red error message. Worst comes to worst, this is good enough.

In the meantime, any more thoughts on Soul of Burnished Bronze? We never finished that one.
 
Mind you, now the program is ALLOWING me to add the upgrade, I just get the red error message. Worst comes to worst, this is good enough.

In the meantime, any more thoughts on Soul of Burnished Bronze? We never finished that one.

You never answered my question on that one.
 
That is correct Aaron. Trying that now...yes, that is already checked for Monster Hunter. Will try adding Ranger and Slayer to that list since they share the same ability (Favored Enemy) and see if that helps.

No, no change. I'm getting "Too Many Upgrades: 1 of 0 (1 Overspent)! Same thing.

I still think you're adding the ability in the wrong way, but whatever man. If you're happy, I'm happy.
 
Soul of Burnished Bronze fixes

The error message tells you the problem is on line 1. What is on line 1 which might be the issue?

Duh! Sorry, I missed this question.

The line reads:

field[listname].text = "Soul of Burnished Bronze +" & (field[xIndex].value * 2)

Error message below

Hero Lab was forced to stop compilation after the following errors were detected:

Syntax error in 'eval' script for Thing 'cRLSoulBrz' (Eval Script '#2') on line 1
-> Error in right-side expression of assignment
One or more timing errors were identified. Please review the timing report and correct the errors. You can access the report under the 'Develop' menu or by clicking this link.
 
Favored Enemy stacking

I still think you're adding the ability in the wrong way, but whatever man. If you're happy, I'm happy.

I'd rather have it work properly, it depends how much trouble you think it is at this point.

And my overtired brain finally figured out what you've meant...take the new script and use it in a new Class Special for the pclass. Did that. I bootstrapped it to the pclass and added ClSpecWhen tags for levels 1, 3 and 5 (when the ability is gained).

I'm just not sure if the script you developed for me just allows the stacking of Favored Enemy with other classes, or if it actually grants the benefits of Favored Enemy as well. If not, then we need to add that as well. I hope this helps.
 
Duh! Sorry, I missed this question.

The line reads:

field[listname].text = "Soul of Burnished Bronze +" & (field[xIndex].value * 2)

Error message below

Hero Lab was forced to stop compilation after the following errors were detected:

Syntax error in 'eval' script for Thing 'cRLSoulBrz' (Eval Script '#2') on line 1
-> Error in right-side expression of assignment
One or more timing errors were identified. Please review the timing report and correct the errors. You can access the report under the 'Develop' menu or by clicking this link.

Right, so look at that line. Try and think about how you've seen text fields set in the past. What is different about it here and is presumably causing the problem?
 
Something new...in addition to adding a selection for a new Favored Enemy on the character sheet for the pclass Monster Hunter tab, there is also what appears to be an army ability Favored Enemy available under the Special Abilities button. That pull-down menu includes a ton of stuff that is NOT usually available for a FE selection, and gives me the following error if I make a selection with it:

Syntax error in dynamic 'candidate' tag expression
- - -
Attempt to access field 'cFav1Level' that does not exist for thing 'tpAnimal'
Location: 'eval' script for Thing 'cRLStudFoe' (Eval Script '#1') near line 42
- - -
Attempt to access field 'cFav1Level' that does not exist for thing 'tpAnimal'
Location: 'eval' script for Thing 'cRLStudFoe' (Eval Script '#1') near line 42

Hope that helps. All I can say is, I don't envy you guys for having to work this stuff out every day!
 
Back
Top