• 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

Odd error message on a character

H

Hirsute

Active member
Having another odd error here. On one of my wife's characters, we get the following error whenever we open the .por file, and any time text is typed in or cleared from a text box:

Invalid tag expression specified for 'findchild'
Location: 'eval' script for Thing 'ioPchPixDs' (Eval Script '#1') near line 12

I've searched around and not found it. Anyone have any ideas?
 
Best thing I can think of is removing the pouch of pixie dust and re-adding it to the character. And making sure that everything is up to date. I myself dont run into an error with the item.

Could either of you maybe upload a "bugged" portfolio to see if it might be related to other sources being active or not active?
 
Last edited:
Ah, that makes sense. Interesting. I've attached a bugged portfolio. I'll remove and re-add and see if that fixes it. I'll also report it as a bug.
 

Attachments

The error is definitely in the script

Code: 
        hero.findchild[BaseSpell,"thingid.spFaerFir1 & Helper.ItemSpell"]

is invalid, it should use an & and not &

and that is used through the script
 
Don't know what to tell you there Andrew it works just fine for me oddly enough. Even the character sheet provided by Hirsute (besides the 3rd party/custom content I don't have heh)

Also the &amp is most likely not what it is falling over. Seeing I have that entry as well. Either way the only way I could try to help
further now would be if someone could PM me the Eval code you guys have. Seeing it is working 100% on my end. If the code is the same then my last bet would be that 3rd party/custom
material is doing something to it
 
Last edited:
It's triggering at line 12 because that's where the else statement falls to. Add class levels it triggers earlier. Do you have the newest update from last night?

And needless to say, the bug just needs to get filed.
 
Yeah I saw that already and updated my post apparently while you were posting. But more trying to pinpoint it so that we might be able to get Hirsute a working version right now for it. I am fully up to date and tried it on all my machines and it is working fine. As I said the only difference I could think of is third party/custom related stuff at the moment (seeing I ain't using any). Cause I doubt there are differences between the 2 evaluation fields. But just in case I was asking for a pm version of the ones you guys had to check compared to my own.
 
Last edited:
AndrewD2 said:
The error is definitely in the script

Code: 
        hero.findchild[BaseSpell,"thingid.spFaerFir1 & Helper.ItemSpell"]

is invalid, it should use an & and not &

and that is used through the script
Click to expand...
Just FYI if anyone cares is that & is actually & in XML. Its called an escape character and if the script section is not wrapped in <![CDATA[ ]]> then & needs to be escaped from & to &.

In this case if your seeing & in the editor then most likely <![CDATA[ ]]> is present causing the error.

Yeah I get the same error using the above .por instantly.
 
Could the ones with the error try a character/portfolio without any third party/custom material. Cause that is the situation I am in and is working just fine.
 
ShadowChemosh said:
Just FYI if anyone cares is that & is actually & in XML. Its called an escape character and if the script section is not wrapped in <![CDATA[ ]]> then & needs to be escaped from & to &.

In this case if your seeing & in the editor then most likely <![CDATA[ ]]> is present causing the error.

Yeah I get the same error using the above .por instantly.
Click to expand...

Heh, that I did know, I'm just too lazy to explain ;-)
 
As I said though the item works just fine for me. So the only thing I can think of that is interfering here is the third party/custom material. I only have Paizo material and all is working fine.

That is why I was asking to see if turning of ALL third party/custom stuff won't trigger the error either for you guys
 
Togainu said:
As I said though the item works just fine for me. So the only thing I can think of that is interfering here is the third party/custom material. I only have Paizo material and all is working fine.

That is why I was asking to see if turning of ALL third party/custom stuff won't trigger the error either for you guys
Click to expand...

Nope that's not it. I've got a system with only Paizo books loaded (others disabled in the develop menu) and still get the error. The only reason I could think for you is if it's something that happened in 12.6
 
AndrewD2 said:
Nope that's not it. I've got a system with only Paizo books loaded (others disabled in the develop menu) and still get the error. The only reason I could think for you is if it's something that happened in 12.6
Click to expand...
Yep same here. I run a multiple data sets and one is 'core'. Besides no way I could cause a script error like that in a different Thing. Scripts just don't work that way.
 
AndrewD2 said:
Nope that's not it. I've got a system with only Paizo books loaded (others disabled in the develop menu) and still get the error. The only reason I could think for you is if it's something that happened in 12.6
Click to expand...

Well I am running 12.6 myself which is why I find this difference in result a bit remarkable. But well hope it will get fixed either way for others that are having this issue.
 
Togainu said:
Well I am running 12.6 myself which is why I find this difference in result a bit remarkable. But well hope it will get fixed either way for others that are having this issue.
Click to expand...
Do you have the develop/debug tools turned on? I know myself and Andrew would. With that turned off many error messages don't happen. Go to "Develop->Enable data file debugging" and then try the .por file again.
 
ShadowChemosh said:
Do you have the develop/debug tools turned on? I know myself and Andrew would. With that turned off many error messages don't happen. Go to "Develop->Enable data file debugging" and then try the .por file again.
Click to expand...

Ah yeah, I'm so used to that being on that I forget that not everyone has it on.
 
ShadowChemosh said:
Do you have the develop/debug tools turned on? I know myself and Andrew would. With that turned off many error messages don't happen. Go to "Develop->Enable data file debugging" and then try the .por file again.
Click to expand...

That indeed causes the error to show up. I actually forgot to set that setting up after doing a clean install because of the connection issue I was having within the Windows 10 fast ring (and installing a test client of hero lab for it).
 
You must log in or register to reply here.
Back
Top