Closed Zyllos closed 3 years ago
As mentioned by GenWilhelm and reviewed from the Tabletop Simulator API documents, JSON is just a static global that can be utilized.
As such, this means internal to TTS is where the issue lays and complicates a possible fix from our end.
Many secondary objectives have characters that are not ASCII, but unicode. See the "CHARACTER" word in Assassinate for Eternal War.
When the JSON.encode sends the save data into the file, some of these characters become //u003f. Then when loading from a save, the saved data will display ??? for those characters as it does not understand the encoding.