Seabound, the culmination of a 6-week group project, is a casual fishing game with a key focus on exploration. My role on the project was as a general programmer, and my contribution, accordingly, were the movement controller, settings backend (though not the UI), the camera controls, and the fishing ellispe. You can find my thoughts about these further down. ​ This project was perhaps the most challenging one I've faced yet, mostly due to the group environment; working in a group has been a new and enlightening experience for me, and I've learned a lot about how I work with others. ​ Another challenge with this one was the extremely short time period given to make the game; 2 weeks each for alpha, beta, and gold development, with 3 days per week to work on it. Essentially, it was like a big group game jam, and a lot of things ended up getting rushed because of that. ​ --- ​ Dispite having sunk most of my time into the player's movement, my absolute favourite piece of work that I did was the settings backend, allowing the user to set, get, save, and load settings of various types, stored as strings. It has some limitations (e.g. no variable type specification allows for accidental type mismatch, value must be convertable to and from strings), but overall the system works quite well. It uses an array to store [key:value] pairs, both of which are strings. ​ When a setting is stored, the manager searches through the array, looking for the provided key. If it is found, its value is replaced by a string representing the value passed in (converted using ToString), failing if the type of said value does not implement IConvertible. ​ When a setting is requested, the manager searches through the array for the provided key, and, if found, sets an "out" variable to the associated value (converted to the requested type using Convert.ChangeType) and returns true. Otherwise, if it finds nothing, or the conversion fails, it leaves that value at default and returns false. This is so that, if it fails to find a setting, whatever is interfacing with it can load a default value. Relative to the above, the saving and loading are extremely simple; using the default JSON library provided by Unity, they serialise and deserialise to and from a file respectively. This file is stored in "Application.persistentDataPath/settings.json" - Unity's reference to the correct path to store this kind of information for whatever system it's built for. ​ --- ​ With that extremely verbose exploration out of the way, there's not much more to talk about. We got a lot done in a very short time, and, though I wasn't particularly invested in the project itself, I am proud of my individual contributions, and the finished product is pretty good in itself.