load_conversation should be able to tolerate speaker objects and warn on unreadable objects instead of crashing #79

New issue

Open

opened 2026-10-20 02:05:53 +00:00 by Roboticy3 · 0 comments

Roboticy3 commented

2026-10-20 02:05:53 +00:00

(Migrated from github.com)

In general, also, if the conversation loader encounters an object that it doesn't recognize in the json array, as long as the object can be separated from the remaining objects and doesn't corrupt the overall array structure, it's safe to just ignore it with a "warning" (non-fatal load error event).

One great feature from the old engine that hasn't translated yet is the feature of loading speakers from conversation files. These speakers would get added to the active config environment when the conversation is loaded into a context. This was easier in the gdscript implementation because the typing wasn't as strict. In general, also, if the conversation loader encounters an object that it doesn't recognize in the json array, as long as the object can be separated from the remaining objects and doesn't corrupt the overall array structure, it's safe to just ignore it with a "warning" (non-fatal load error event).