Just finished an intense two-week pre-production phase, and I'm happy to report the following ::
👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁
⌨️ Nothing has Changed | Everything has Changed
As is the case when sanitizing codebases , it's been a rather dry two weeks of refactoring, restructuring, and documenting the Unity3D project where the Apotheorasis game comes from.
The result looks (or rather, sounds) the same from the player's perspective ; but I am now able to work much faster when implementing new features. It's also less stressful when something breaks, as finding what's wrong when everything follows a similar pattern is much easier.
👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁
📔 Narrative Designer Appreciates Thoughtful Programmer
Okay I'll admit I'm both people in this headline (which makes it kinda trippy) but there's no denying that the part of my brain responsible for doing the creative writing of Apotheorasis is definitely happier after the logical (?) side of me created a few neat parsers.
In a (hopefully not too technical) nutshell, I wrote a little program which reads in my Script, breaks it down in Lines (giving them an ID and noting who speaks) and stores it both as a lightweight .csv file (which a Voice Actor can print out and read from) and as a code file (.cs), giving me instant access to those lines in Unity so I can prepare the logic behind when they're called, who speaks them, etc.
👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁 👁
Stay Tuned and share your thoughts on the apotheorasis channel 🙂