Sprint 1: See, there's your problem.
Unity confuses and terrifies me. I like languages without memory management, modern conveniences, garbage collection, and robust libraries exclusively for Game Development. I know; I picked a wonderful major. Chances are I'll never have the need to build a game engine from scratch using C, even if I'd love to walk the path of John Carmack, so, better cope with it and get used to what Unity offers. My role for this sprint was primarily setup. Everything has to be a good foundation for the designers; I am taking the responsibility to make sure they don't have to touch a single line of code, and have the capability to change values in a way that's easy to understand and gives them the most flexibility possible. This divides my job into three important tasks: - Create legible Inspector code (using headers) - Provide console feedback whenever something happens (or goes wrong) for the sake of easily debugging i...