Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trusts: Lua runtime error: Unexpected character line 7 #1083

Open
Millercan66 opened this issue Dec 29, 2021 · 7 comments
Open

Trusts: Lua runtime error: Unexpected character line 7 #1083

Millercan66 opened this issue Dec 29, 2021 · 7 comments

Comments

@Millercan66
Copy link

Downloaded Windower 4.3 stable version. Trust addon is useless. Checked the internet on how to fix problem, no luck. I'm not a coder I'm just a FFXI player. I don't understand the whole Lua thing but this problem has prevented me from saving trust sets, listing trust sets, and recalling them. If you could sent me instructions on how to fix this I would be grateful. gncmill@gmail.com.

The whole line in the BG console reads:

Trusts: Lua runtime error: libs/config.lua:99: XML error, line 7: unexpected character '#'.

@Nifim
Copy link

Nifim commented Dec 29, 2021

What is the name you tried to save the set under? it looks like you probably saved a set with a # in it and that is not a legal character for a set name. you can delete your settings file located in the addon/trust folder and then try saving the settings again using a simple name like ddparty or supportparty

@RubenatorX
Copy link

yeah, you corrupted your settings file by using special characters in your set name. keep it simple and it won't break itself

@Millercan66
Copy link
Author

Millercan66 commented Dec 29, 2021 via email

@RubenatorX
Copy link

/path/to/windower/addons/trusts/data/settings.xml

@z16
Copy link
Member

z16 commented Dec 29, 2021

This is really a config issue. It's not serializing special characters correctly, but it should. The XML library handles that case correctly, but the config library only uses that library to read settings, not to write them, because it wouldn't support keeping certain formatting structures (like comments).

To fix this, we would need to change a few lines in the nest_xml functions to escape the values they're formatting. It's not super trivial but can be done in a short ish time if someone wants to take a stab at it. Poke me if you want to and need some pointers.

@ghost
Copy link

ghost commented Mar 31, 2023

im having this issue how do i fix this??

@RubenatorX
Copy link

RubenatorX commented Mar 31, 2023

im having this issue how do i fix this??

delete the addon's settings file and reload the addon, and don't use special characters such as < or > in your set names

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants