• 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 on load.

Jyiiga

New member
Any ideas on this error?

GTvifAo.jpg
 
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.
 
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?
 
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?

Because the main HL system doesnt know where .user files come from or which .user file something should be in.
 
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? :D
 
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? :D
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.
 
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.
Ah.

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. ;)
 
Back
Top