• 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

NPC with more than 25 levels, index out of range errors

Phyxion

Active member
I'm getting ready for an upcoming campaign set in Forgotten Realms but using Pathfinder rules. One of the things I'm doing is rebuilding all the NPCs I might need stats for. The problem starts with Elminster (as so many problems do) - apparently there's a limit of 25 class levels when building an NPC in Hero Lab, because the moment I add the 26th level, I get a big list of errors (see below). With all the high level characters in the Realms, I expect this will cause some issues down the line.

I understand this probably doesn't impact even a tenth of a percent of the HL user base, but does anyone know of a workaround, or would it be possible to raise the limit to, say, 40? Is this something the HL d20 gameset handles already, and if so, would that solution work here / could it be copied over? Is it something that could be implemented in a .user file (I suspect not, but just in case...)?

Thanks to anyone who can help out!

Error log:
Attempt to access out-of-bounds array index '26' for array field 'cmhPDCbyCR'
Location: 'label' script for Template 'scrAbilDC' (in Portal 'arrow') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhSDCbyCR'
Location: 'label' script for Template 'scrAbilDC' (in Portal 'arrow') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhGSbyCR'
Location: 'label' script for Template 'scrEstBot' (in Portal 'Fortarrow') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhPSbyCR'
Location: 'label' script for Template 'scrEstBot' (in Portal 'Fortarrow') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhGSbyCR'
Location: 'label' script for Template 'scrEstBot' (in Portal 'Refarrow') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhPSbyCR'
Location: 'label' script for Template 'scrEstBot' (in Portal 'Refarrow') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhGSbyCR'
Location: 'label' script for Template 'scrEstBot' (in Portal 'Willarrow') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhPSbyCR'
Location: 'label' script for Template 'scrEstBot' (in Portal 'Willarrow') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhHDmbyCR'
Location: 'label' script for Template 'scrEstMid' (in Portal 'Damage') near line 12
- - -
Attempt to access out-of-bounds array index '26' for array field 'cmhLDmbyCR'
Location: 'label' script for Template 'scrEstMid' (in Portal 'Damage') near line 12
 
During a conversion you should be changing rules to Pathfinder and Pathfinder does not have "epic" rules (ie past level 20). My advice is to use Pathfinder Mythic rules which are fully supported in Pathfinder.

The limit in HL for Pathfinder was always 20 single levels of a class so it was nice for LW to raise that to 25. So either add your level 26+ as another class or try out Mythic.

You can't get around the "index" limitation using the editor so no .user file will help in this case. :(
 
I understand (and agree with) the limit of 20 levels per single class. However, in this particular case, it's just that this dude has a total of 31 class levels (plus epic). Ftr1, Rog2, Clr3, Wiz20, Archmage 5, Epic 4. (Admittedly, Forgotten Realms is widely known for having a lot of super high level, rulebreaking NPCs). This doesn't seem to intrinsically break the PF rules that I can find.

I'm definitely going to be using PF's mythic instead of the 3.5 epic stuff, I was just hoping I could cram in all the "normal" levels as-is. It looks like from the error messages that maybe this is just a display issue, and it won't affect anything outside the "estimated CR" panel (which is basically all but useless for this sort of monstrosity anyway).

Maybe I can do something with templates or gestalt to make this work.

Thanks :)
 
I understand (and agree with) the limit of 20 levels per single class. However, in this particular case, it's just that this dude has a total of 31 class levels (plus epic). Ftr1, Rog2, Clr3, Wiz20, Archmage 5, Epic 4. (Admittedly, Forgotten Realms is widely known for having a lot of super high level, rulebreaking NPCs). This doesn't seem to intrinsically break the PF rules that I can find.
The above works fine in HL. I just inputted those levels and no issues. You can't go past level 20 in any "single" class but if you add multiple levels of different classes HL will let you do it. Except for the "Epic 4" as no such Thing like that exists to add. :(
 
You can also just level them to 20 and then use the adjustments to change anything that they would have received if the rules allowed levels beyond 20.
 
The above works fine in HL. I just inputted those levels and no issues. You can't go past level 20 in any "single" class but if you add multiple levels of different classes HL will let you do it. Except for the "Epic 4" as no such Thing like that exists to add. :(
Did you build him as a PC or NPC? The error messages seem to refer to the "CR estimate" panel.
 
Did you build him as a PC or NPC? The error messages seem to refer to the "CR estimate" panel.
Tried both and no errors. Its the "CR Estimate" panel that is tossing the error. If you turn that off the error goes away press (CTRL-K) to turn it off.

Hmm that is "maybe" an error you should report. But if you turn off the 'CR Estimate' panel at least you can make the error go away. :)
 
As long as the CR estimate panel is the only thing that doesn't like it, I'm good. After looking at what it does, I don't see how it could refer to entries past what are actually on the table anyway, and I think we all know how likely Paizo would be to extend the table.

Thanks anyway :)
 
Back
Top