08052022

Implemented loading screen and timer for CPBE, a few structural changes to scripts.

A long day of work, with only a handful of forward-facing changes to show for it. In terms of the few that did end up getting done: the CPBE now has a loading screen to load into the test itself, as well as the starting prompt of the test. The rest of the work was backend stuff: a huge chunk was writing the actual questions, and figuring out the best way to structure them so that they’d serve a dual purpose of actually tutorialising. The other part was figuring out the best way to handle the questions (and more specifically, the answers) with the current input and save/load functionality of the game. I ended up going with a CSV to load in the questions (and creating a template for loading in multiple CPBEs, based on the current in-game day) as well as the response times for each question. I’ve yet to build the questions themselves – that’s work for tomorrow – but hopefully it shouldn’t be too much of a struggle…

I also went and condensed a whole bunch of free-floating, miscellaneous scripts into unified scripts with many individual functions. I’m not sure yet the effect of it, which is to say whether this was even worth it at all, or if there’ll be any unintended side effects; but the overall folder structure is a bit “neater”, at least notionally. I actually somewhat preferred having all the functions listed as separate script assets, as it made browsing them (especially when sorted alphabetically) a lot easier, but we’ll see. If anything, it’ll be a learning lesson for how to go about the question of asset organisation in future projects.