Introduction
In this section you will be able to find relevant information regarding the code written for both Hangmath and The Great Goblin Chase. For the order of the information’s appearance please refer to the table of contents under the welcome page. Thank you for visiting our page!
User Manual
Program Description for Developers
Final Algorithm, Flowchart’s, or Pseudocode
Final Program with Comments
Brief Discussion
Team J initially started with the Hangmath code, we were under the assumption that this code would take only a day or two to write. However, we were quite wrong, small hiccups kept pushing back the completion date. The first obstacle we faced was organizing all of the for loops and i/if-else statements, we overcame this by simplifying some of the code and putting more spacing into the code. As we eventually began to wrap up the code, another issue we ran into was finding a method that allowed users to change the difficulty level of the game. Initially we tried buttons, however, that proved to be beyond our level of MatLab knowledge. Therefore, we simply inserted code at the beginning of the program that asked the user to type in the level of difficulty they wanted.
Once Hangmath was completed the group moved onto The Great Goblin Chase. As expected this game was a bear to code, however, it was worth the effort as it got our group nominated for the SDP game showcase. The coding began slow, and crept on at a snails pace due to the complexity. One of the first issues we ran into was figuring out how to design the game board. Though after reading through the supplemental information we found out how to use the simple game engine. Next we downloaded the sprite sheet and colored in the sprites to fit our game. The struggle began when we tried to get the sprites onto the board. After scouring the MatLab help forums we finally found something that pointed us in the correct direction. At this point the code was almost finished, all we needed to do was tie a few loose ends and debug.
During the game’s final testing they both performed spectacularly and reported no errors or bugs. As stated earlier, The Great Goblin Chase worked so well that our group ended up being nominated, and selected, to be part of the SDP game challenge.
Conclusion and Recommendations
Group J was tasked with designing a game through matlab. Group J programmed 2 separate games of varying difficulty. Our first game was the simpler game: Hangman. In hangman, after choosing from one of four different levels of difficulty. The words that are used for the game are based off of mathematics terminology, and you have up to six incorrect guesses until he is hanged. The other game was more complicated. Having a dungeon adventure style, The Great Goblin Chase tasks the layer with retrieving the crown of his king from the goblin’s dungeon. Along the way you will dodge various holes and attack the goblins to unlock the secret to defeat the goblin king and retrieve the king’s crown.
To increase the fun, hangman could be made using visuals. Adding on a body part with an incorrect guess, filling blanks with correctly guessed letters, or adding buttons for the user to select a difficulty level add to the user friendly nature and is more interactive. In TGGC, sequential levels that increase in difficulty and change the layout of the board would add more challenge and more adventure to the chase of the crown.
Throughout the creation of these games, our strategy was to have each pair work on one game and join forces once the easier game was finished and collectively finish the more difficult one as a group. In our case, the pair that made hangman finished first and joined the other pair in finishing The Great Goblin Chase. In each pair there was a programmer and a direct advisor. The programmer would punch in the code as the programmer and advisor discussed ideas for how to structure the code. This strategy proved to be effective with two very strong programmers and lots of creativity to go around. This strategy is recommended to any group for its effectiveness in dividing and conquering the workload. Evenly distribute the programming talent and creativity and consolidate forces at the end to close out the more difficult game to make this project short and sweet.
References
Software Design Project Procedure (provided)
MATLAB Answers – MATLAB Central, www.mathworks.com/matlabcentral/answers/.
Wahlin, Leah. “Fundamentals of Engineering Technical Communications.” Fundamentals of Engineering Technical Communications, ohiostate.pressbooks.pub/feptechcomm/.