Update 1.1f Error

[Lawful_g]

When I updated to the newest version a few days ago I started encountering an error when starting the program that prevents the use of my custom data files I have made...

The Error Reads:
All Classes.dat - 29 - Thing - Field 'cExtraLev' referenced but not defined

I've found that in order to fix it I have to delete the Class Helpers I have already made. I have went through, copying everything onto a new blank Thing and now the program is working again, but it sure was a pain in the butt. Did anyone else have similar problems?

I only had 4 custom classes done so it wasn't such a big deal for me, but I can imagine if you had a lot already completed it would take days using my method to duplicate everything and get it fixed. Does anyone know what caused this problem and a simpler/faster way to fix it next time?

[Culhwch]

I did have the same problem. I went into the XML files with a text editor and deleted the line that was causing the error, then restarted the Hero Lab editor and remade the class panel.

[Lawful_g]

I've also been getting quite alot of crashes since updating as well. In particular when adding or removing classes that the character does not meet the pre-requisites for. I do that a lot when testing prestige classes I am creating.

Also, for one particular class I made I notice that as soon as I add the last Custom ability available the program crashes. The first 4 are fine, and it doesn't matter which ability is left for last, the darn thing keels over. Have you had any similar problems Cullwch?

[Culhwch]

I've not tried adding a class where the character didn't meet the prerequisites since the last update. I'll try tonight and see if I get a crash.

I've only had the program crash once since the last update, and that was when I was adding a new custom ability in the editor (I think when I clicked the Save button). I went back in and added the custom ability just fine.

I'm pretty sure I have prestige classes with more than 4 custom abilites (I think I bootstrapped at least 5 abilities into the Champion of Corellon Larethian PrC). I'll double check tonight (I'm at work now, and thus away from my play computer. ;) ).

[Colen]

Lawful_g wrote:
>
>
> When I updated to the newest version a few days ago I started
> encountering an error when starting the program that prevents the use of
> my custom data files I have made...
>
> The Error Reads:
> All Classes.dat - 29 - Thing - Field 'cExtraLev' referenced but not defined


Oops! Sorry about that error. I thought it'd be safe to delete that
field, but apparently not. :(


I'll implement stuff to make sure that doesn't happen in future. Sorry
for the inconvenience.


--
Colen McAlister (colen@wolflair.com)
Chief Engineer, Lone Wolf Development
http://www.wolflair.com/

[Colen]

Lawful_g wrote:
>
>
> I've also been getting quite alot of crashes since updating as well. In
> particular when adding or removing classes that the character does not
> meet the pre-requisites for. I do that a lot when testing prestige
> classes I am creating.
>
> Also, for one particular class I made I notice that as soon as I add the
> last Custom ability available the program crashes. The first 4 are fine,
> and it doesn't matter which ability is left for last, the darn thing
> keels over. Have you had any similar problems Cullwch?


Could you please email me the data files you're having the crash problem
with, and tell me which class to add to reproduce it? It's possible that
your classes are doing something Hero Lab isn't handling properly.
Adding the "normal" prestige classes like the assassin, loremaster etc
seems to be working fine.


Please email the files to me at colen@wolflair.com. Thanks!


--
Colen McAlister (colen@wolflair.com)
Chief Engineer, Lone Wolf Development
http://www.wolflair.com/

[rob]

At 08:50 AM 6/7/2007, you wrote:
I've also been getting quite alot of crashes since updating as well. In particular when adding or removing classes that the character does not meet the pre-requisites for. I do that a lot when testing prestige classes I am creating.
This bug only occurred with a class that had just been spliced in from the editor. We located it and fixed it in the release that just went out.