fODaddenem - produces errors in debug datafile mode

I originally thought there was an error with official sources, and I bug-reported, but LWD reported back to me that it looks like its a custom object.

This was the message i included:

>When I add the antagonize feat, i get an error: Attempt to access
>container from script with no ability to do so for thing fODaddenem
>near line 2

It only seems to happen when I do antagonize on a barbarian. Does anyone know what "fODaddenem" comes from?

mirtos said:

It only seems to happen when I do antagonize on a barbarian. Does anyone know what "fODaddenem" comes from?

Click to expand...

It does not appear to be a naming convention used that I am aware of. Do you have any .user files you got from PDFs?

Do you have a any text search tools? I use TextPad actually and that allows me to search everything in a the data folder of type .user for specific text. Something like that makes it really quick to figure out which file that a "unique ID" is from.

That would be he Additional Favored Enemy feat from Open Design's Expanded Spell-less Ranger files. Can you PM me with the details on what's happening?

I use NotePadd++ and JEdit But yes, that would make sense, as im using spell less ranger, but im fairly sure i got it from chiefweasel, even though i did purchase the pdf. although its possible, that for a short period of time i was using the one from Open Design.

I will PM you tonight.

TArcKnight - have PM'd you. Others (I know some others have been sent here) if you turn off data file debugging the errors dont present themselves.

an addendum to my PM, it happens when i have data file debugging and i select any feat.

It will probably happen if you just open the feats tab and "Additional Favored Enemy" is one of the feats that's currently shown, even if you don't actually select a feat while you're on that table.

It's probably an error in the prereqs, so it would be generated any time Hero Lab tries to process the prereqs on that feat. But, it won't be reported as an error until you've left the feat selection form.

Data File debugging does also turn on certain error messages that normal users won't see - cases that aren't technically correct, but that the program can easily work around or ignore.

P.S. for data file authors - one of my final testing steps before release is to open the select feat form, and scroll all the way through it (so that Hero Lab executes the prereq scripts of everything in that list), and make sure that no error messages are reported once I close it. (I do this on the Archetypes, classes, and traits tables, too).

I've seen a post on the Paizo boards, where the ESR file has been updated with the most recent HL data....

So if anyone is having this issue, may want to re-download it if got it from there.

Although, it looks like I still missed this an issue with the prereq on the Additional Favored Terrain:
if (hero.picklives[resTerrSel] <> 0) then
validif (hero.childfound[resTerrSel].field[resMax].value >= 1)
endif

This is giving an error in line 2.

The exact same statement is on Additional Favored Enemy, but it doesn't give an error.

Thoughts?

Ok, great thanks. ill give it a try. (I was the person on the paizo board asking for the update)


nope same thing. I feel like perhaps it hasnt been updated. I get the same errors, but i think the whole reason it was being updated on the paizo boards was i was asking for archetypes, and i still dont have them. no complaints about the archetypes, but if it was updated, wouldnt they be in there?

Anyway, i think the bigger issue is the errors?

I can tell you that these are the stats of the file: Modified August 02, 2012, 1:39 AM
File size 42,516 bytes.

(created today on my system)

I've been able to resolve the issue.

The solution: I was able to separate into two different checks:

AFE:
Expr-req: hero.childlives[resEnemSel] <> 0
pre-req: validif (hero.childfound[resEnemSel].field[resMax].value >= 1)

The Terrain one is the same but referencing resTerrSel.

V1.2 of the ESR .hl file has been emailed to Wolfgang and once it's gone through their testing, should be updated in the PDF download. In the meantime, if you want to fix it yourself, you can add the above statements in the editor to both feats.

I want to apologize for missing this and promise to be more careful next time.

Thanks!
Thomas