• 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

Error in loading the New version of Pathfinder 1.1.2

Nikmal

Well-known member
This is what happened.


The data files could not be loaded due to errors. Hero Lab will now attempt to lad them in recovery mode. Once loaded, you can access the editor as normal to correct any errors.

The following errors occured:

Syntax error in 'eval' script for Thing 'cPUDevaTou' (Eval Script #1) on line 9
->Error in right-side expression of assignment
Syntax error in 'eval' script for Thing 'cPWP1MrHI' (Eval Script #1) on line 14
->Error in right-side expression of assignment
 
I don't believe either of those things are part of our files, check your community stuff, perhaps?
 
I don't believe either of those things are part of our files, check your community stuff, perhaps?
So how come the #levelcount[] macro can't be used in a String operation anymore?

The errors are showing for the following line:
Code:
field[abText].text = #levelcount[PWBtlTmpl] & " + 1d4/maneuver level HP"

This is not uncommon code. So what happened to the macro that its now suddenly invalid?
 
levelcount now counts Classes tags + LvCountAs tags, which is a new tag group the unchained classes add for counting as their CRB equivalents for the purposes of the levelcount macro. This was a fix for the stunning fist feat not calculating charges correctly for unchained monks (as well as others).

I think since it is now more than a single tagcount it won't work in string expression like that. How common is that in community stuff? I'd think that it would be relatively rare because most things have fields to store their level instead of having to count tags.
 
How common is that in community stuff? I'd think that it would be relatively rare because most things have fields to store their level instead of having to count tags.
Yeah the ones I fixed never should have been using it but it's still a major change in HL scripting logic. So I can't tell you the full cost of the change to the macro is. Still not really understanding how adding more tags to count causes it to be unusable. Isn't it still just returning a "number"?

Currently I have the 3PP Pack fixed again and released. You are correct that a Class Special should not be using #levelcount[] instead of field[xAllLevel].value but not every person doing HL stuff knows that. :)

Macros to me are like the base building blocks of HL. Similar to the core methods of Java. Its not cool to drastically change that logic on people. Sorry had a LONG LONG night with real work issues. Little grumpy today...

Thanks for the Answer....
 
Continued Error

Yeah the ones I fixed never should have been using it but it's still a major change in HL scripting logic. So I can't tell you the full cost of the change to the macro is. Still not really understanding how adding more tags to count causes it to be unusable. Isn't it still just returning a "number"?

Currently I have the 3PP Pack fixed again and released. You are correct that a Class Special should not be using #levelcount[] instead of field[xAllLevel].value but not every person doing HL stuff knows that. :)

Macros to me are like the base building blocks of HL. Similar to the core methods of Java. Its not cool to drastically change that logic on people. Sorry had a LONG LONG night with real work issues. Little grumpy today...

Thanks for the Answer....

ShadowChemosh, I think you've fixed the 2 errors first noted above. I was getting it and am not getting it anymore. But now I'm getting this error. Can this one be fixed too?

Field 'wCustMonNm' is no longer associated with pick 'MythSource'
 
ShadowChemosh, I think you've fixed the 2 errors first noted above. I was getting it and am not getting it anymore. But now I'm getting this error. Can this one be fixed too?

Field 'wCustMonNm' is no longer associated with pick 'MythSource'
Just FYI these are not from the Community Packs. I searched everything for both wCustMonNm & MythSource. So this was a LW change in the last 11.2 update.
 
I too am getting errors after updating today. So far I have gotten these two:

The data files could not be loaded due to errors. Hero Lab will now attempt to load them in recovery mode. Once loaded, you can access the editor as normal to correct any errors.

The following errors occurred:

File: COM_GMPack_Frumple - Giants.user (line 0) - Error reading file: /Users/scottbeeh/Library/Application Support/Hero Lab/data/pathfinder/COM_GMPack_Frumple - Giants.user

File: PFRPG_Jade_Regent_AP49.user (line 0) - Error reading file:
/Users/scottbeeh/Library/Application Support/Hero Lab/data/pathfinder/PFRPG_Jade_Regent_AP49.user


And yes, I realize one of them is a Community Pack.
 
I too am getting errors after updating today. So far I have gotten these two:

The data files could not be loaded due to errors. Hero Lab will now attempt to load them in recovery mode. Once loaded, you can access the editor as normal to correct any errors.

The following errors occurred:

File: COM_GMPack_Frumple - Giants.user (line 0) - Error reading file: /Users/scottbeeh/Library/Application Support/Hero Lab/data/pathfinder/COM_GMPack_Frumple - Giants.user

File: PFRPG_Jade_Regent_AP49.user (line 0) - Error reading file:
/Users/scottbeeh/Library/Application Support/Hero Lab/data/pathfinder/PFRPG_Jade_Regent_AP49.user


And yes, I realize one of them is a Community Pack.
Both are community files from the GM Pack. I would go with something went wrong with the download or install. Do a fresh download of the GM Pack or Mythic Pack (not sure which one you have) and install again.

See if that resolves the issue...
 
Back
Top