-
Notifications
You must be signed in to change notification settings - Fork 11
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
Bug: New Script Format Not Supported #425
Comments
Looks like this will be a database update, should support both IDs to not break old scripts. Alternatively, could ignore underscores in IDs all together (this is what bra1n has said the official app does - have not confirmed myself lol) |
Thanks for the report. I was completely unaware of this change. I know both formats have been valid for a while and I was mostly ignoring the problem as the format of the existing characters didn't change so it was only really an issue when people manually hacked them in some way (usually when a new character was released an not officially supported). It's not possible to simply ignore underscores since all the existing JSONs are stored with the original IDs and so things like search won't just work without a mapping backwards to the originals (something has to know that if you search for That's what I originally proposed for the It'll probably be a few days until this gets resolved. It's not really causing any harm from a functionality perspective beyond search by character and just cause general ugliness. |
I have migrated the database to remove special characters and now character usage everywhere is without special characters. |
Describe the bug
The script format has changed so that ids for characters with multiple words in their name no longer have an underscore. For example, the Fortune Teller used to be
fortune_teller
and is nowfortuneteller
.These characters are not showing up properly in the character list.
To Reproduce
Is this problem reproduceable, if so, please provide the steps required to reproduce the behavior:
Screenshots
The text was updated successfully, but these errors were encountered: