Junior Member
Join Date: Jan 2012
Posts: 14
|
So I recently started working on a cleric of Wee Jas but I didn't have time to finish it the night I made it so I saved it and exited out. When I loaded it up the next day I get the following errors.
Usage pool 'jCP' has been orphaned for pick index '0' Usage pool 'jGP' has been orphaned for pick index '0' Usage pool 'psiPPUsed' has been orphaned for pick index '0' Usage pool 'jXP' has been orphaned for pick index '0' Usage pool 'jSP' has been orphaned for pick index '0' Usage pool 'jPP' has been orphaned for pick index '0' Anybody have any idea what this means? |
#1 |
Spy
Join Date: Jan 2011
Location: Van Nuys, California
Posts: 1,220
|
All I know is that it is referring to money (CP, SP, GP, PP), experience points (XP), and psionic power points. These are fields found in the Journal tab for adding to the totals, which is usually indexed. I have no idea why the error is occurring though without more information.
|
#2 |
Senior Member
Volunteer Data File Contributor
Join Date: Feb 2009
Location: Virginia
Posts: 364
|
Quote:
I'm now doing a line-by-line comparison of my printed character sheets to see what other additional items may have gone away. Thank goodness for having hard copy to peruse & not just relying upon the electronic version of the character. Nigel Fogg, aka The Wayfarer Last edited by Nigel Fogg The Wayfarer; January 2nd, 2012 at 04:19 PM. |
|
#3 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729
|
Just an FYI but some of those using Pathfinder are reporting the same error. So it's got to be HL itself not the data set.
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. |
#4 |
Spy
Join Date: Jan 2011
Location: Van Nuys, California
Posts: 1,220
|
I've now encountered that error as well. It's the first time I've created a brand new portfolio since the release of 3.9. The error only occurs during the reloading of the portfolio, and only seems to make its presence known on loads of portfolios, but otherwise is not being an issue. Again, seems to only occur on newly created portfolios, as I did try to resave an old portfolio, reloaded it, and didn't have any errors crop up.
|
#5 |
|
|