Odd error message on a character

[AndrewD2]

Originally Posted by ShadowChemosh

Just FYI if anyone cares is that &amp; 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 &amp;.

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

Yeah I get the same error using the above .por instantly.

Heh, that I did know, I'm just too lazy to explain ;-)

[Togainu]

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

[AndrewD2]

Originally Posted by Togainu

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

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

[ShadowChemosh]

Originally Posted by AndrewD2

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

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.

[Togainu]

Originally Posted by AndrewD2

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

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.

[ShadowChemosh]

Originally Posted by Togainu

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.

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.

[AndrewD2]

Originally Posted by ShadowChemosh

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.

Ah yeah, I'm so used to that being on that I forget that not everyone has it on.

[Togainu]

Originally Posted by ShadowChemosh

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.

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).