Shatterbound
Work with your past (and future) selves to solve puzzles. Shatter your obstacles, be your own platform, and more in this time-looping puzzler where YOU are your own solution!
Contributions
As a testing lead and artist for this game, I:
-
Used black box testing to test both the necessary features of the game and any possible action that could potentially break the game.
-
Designed the particle effects for some of the power actions the player performs.
-
Created a small capsule for the game (for marketing the game on Steam)
Tools​
-
Google Sheets​
-
Unity
-
C#
-
HacknPlan
-
GitHub
-
GitKraken
-
Krita
​
Lessons Learned
-
The Importance of the Sanity Checks
-
When starting the development of Shatterbound, I created a sanity check, a spreadsheet that checks if the game's main mechanics work as intended. ​
-
-
The Importance of Full Test Suites​
-
Along with the sanity check, it was important to create a full test suite, a spreadsheet used to record every possible action in the game that could potentially end up breaking it.​
-
-
Prepare the important guidelines before creating test cases​
-
When creating a sanity check and/or full test suite, it's best to set up important questions. For testing Shatterbound's development, those questions were the following:​
-
Name of the mechanic​/action​
-
Description of what the mechanic/action does
-
Inputs on how to activate the mechanic/perform the action
-
Expected Result
-
Actual Result​
-
-
-
Always check if a mechanic works on both the editor of the engine and the build of the project​​
-
Sometimes, the results of an action performed in the engine's editor don't always match that of the final build.
-
For example, during Shatterbound's development, jumping and ground pounding simultaneously would cause the game to break; sometimes, this bug would happen on the Unity engine, and other times, it would happen in the build. Therefore, cleaning the build of the game was crucial after you tested a(n) action/mechanic in the engine's editor. This action is done so that, if there's a bug found in the game, it's both the editor and build.
-
