Junior Member
Join Date: Sep 2016
Posts: 2
|
Any ideas on this error?
|
#1 |
Senior Member
Join Date: May 2007
Location: Durham, NC
Posts: 1,747
|
|
#2 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729
|
You have the OLD version of Modern addon and it no longer works. You need to either a) remove it cause you don't need it or b) upgrade to the latest community Pack.
1) Follow FAQ#1 to remove the addon. 2) If you don't need Modern anymore follow FAQ#11 to remove the messages about 'Sources' you now get when opening a character. 3) If you do want a working version of Modern install the latest "Community Pathfinder Pack" to get access to it again. Hero Lab Resources: Pathfinder - d20pfsrd and Pathfinder Pack Setup 3.5 D&D (d20) - Community Server Setup 5E D&D - Community Server Setup Hero Lab Help - Hero Lab FAQ, Editor Tutorials and Videos, Editor & Scripting Resources. Created by the community for the community - Realm Works kickstarter backer (Alpha Wolf) and Beta tester.- d20 HL package volunteer editor. |
#3 |
Senior Member
Join Date: Sep 2015
Posts: 435
|
Hm.
Wouldn't it be nice if the error message actually said, "Loaded from ..." so that users could tell which add-on they needed to disable/update? |
#4 |
Senior Member
Join Date: May 2015
Posts: 830
|
|
#5 |
Senior Member
Join Date: Sep 2015
Posts: 435
|
But it knows the filename, right? It could at least report that! And I'm guessing that there's a comment/descriptive area inside each file where the author can describe the content ... why not print that, too?
Anything to make it easier for the customer, right? |
#6 |
Senior Member
Join Date: May 2015
Posts: 830
|
It actually doesnt know the file name. What HL does is loads all .user files compiles a list of objects to use. and then references those objects in the .por files. That is why you can have a .user file with ThingA that replaces ThingB without having to know what .user it is in. Also makes writing packages easier because once something grows big enough it can be split off into its own .user.
|
#7 |
Senior Member
Join Date: Sep 2015
Posts: 435
|
Quote:
So I suggest a feature enhancement: when reading .user files, keep track of the name in the same data structure that contains the information about the Thing. That way there will always be a reference back to the original source file. Hm, that could be particularly handy when ThingB screws up and the developer thinks it's in file A when it's really in file B. |
|
#8 |
Junior Member
Join Date: Sep 2016
Posts: 2
|
Thank you.
No more error. |
#9 |
|
|