-
Notifications
You must be signed in to change notification settings - Fork 0
Home
This wiki will contain documentation on the various systems within KeyWave and how to utilize them to make awesome game content.
If you're a programmer, you may first want to check out the High Level Code Overview before jumping into the codebase.
If you're a designer, writer, etc, you can learn how to add content to KeyWave (such as emails or contacts) without having to write a line of code.
Because this game's technical design is intended to allow a lot of flexibility for behavior while lowering the barrier to add content, the game systems rely heavily on string comparisons. Assume unless otherwise noted that naming conventions must be exactly correct or the game may not function properly. This means when you call things in code, use yarn commands, edit JSON files, add files to the game, you must make sure that all of them are using the same name. If something asks for the name of an assignment or character, use the exact name. If certain files need to be named a specific way, ensure they are done so. Also make sure the names of objects in the Unity inspector matches with the names you use for them everywhere else.
I've tried my best to include as many exceptions and debug messages as I can to help with debugging these kinds of issues.
If all this seems confusing now, it will make more sense once you see it in the context of actual game content.