Senior Production Blog 3

This past week had been a series of planning and frame work development. We have laid plans of creating data managers like the guns and especially the player. The ability of having player caching means that we can have the ability to save player progress. Saving player progress would mean that a player can come back on a later time and load in all the things that they had done in a previous match. This saving can also help with QA and debugging. Because player statistics are saved that means when the game breaks we have information on when it broke so instead of only having feedback on it breaking, we also know the game state when it did which can lead to further iteration that prevents bugs.

This week had been also a series of reinforcing previous code. This process is to check if the intended code can work under multiple circumstances. Making sure that the process still works is important so that the game doesn’t break if something unintended were to happen. To consider all possibilities, I had to try multiple ways of breaking my manager’s to see what would break it. If such thing were to happen then I would make improvements to it and adding additional layers.