SIT153 – Assignment #1
GAME PROJECT – A Simple Console-based Game in C++
Assignment must be submitted by 11:59pm Sunday 9th August 2015 (end of Week 06)
The goal of this assignment is to allow students to demonstrate their understanding of the features of the C++ language through the design and development of a simple console-based game. To achieve this goal the student will be required to complete the following steps:
i. Design a simple interactive game (can be based on an existing game)
ii. Develop code to implement this game design (primarily your own, original code)
iii. Test your implemented game for functionality and bugs, and
iv. Document the design/implementation/testing process as well as a user/start-up guide.
There are two key dimensions to this assignment: (1) a demonstration of the software design and development process used by the student; and (2) the completed game that meets a minimum set of requirements. The assignment will require the submission of all documentation and source code for the game.
The following sections detail both the required/expected features of the game and the required documentation. A breakdown of marks to be awarded to each component is also given.
Demonstration of C++ Proficiency
To achieve the goal of demonstrating a sufficient understanding of the C++ language, the submitted game software must contain appropriate examples of the following C++ mechanisms and features:
• Demonstration of C++ programming (standard/basic) features. Appropriate use of:
o variable, constant and enumerator types o loops and branch statements o functions and modularisation
o appropriate use of references to variables and functions
• Demonstration of basic OO programming principles. Appropriate use of:
o class declarations to represent game and/or program entities o object instantiation and use
• Console and File I/O – appropriate use of:
o standard Library input/output streams
o accessing external data files for either input or output • Rigorous error checking and handling through:
o validation of input data
o error checking/validation of function arguments o error checking of function return values
The style and setting for this game is left up to you. The type of game you choose must be sufficient to demonstrate the programming features listed above. Our recommendation is for you to constrain your software to a console application using ASCII characters (text) for display. Games suited to this format may include: an adventure game; a simple simulation/strategy game; or a maze/platform style game.
Game Suggestion – Dice game ‘Pigs’
Pigs is a dice game of chance which involves two players trying to be the first to reach a score of 100 to win. The basic rules of the game ‘pigs’ is described below (as taken from Pig (dice) Wikipedia page):
Each turn, a player repeatedly rolls a die until either a 1 is rolled or the player holds and scores the sum of the rolls (i.e. the turn total). At any time during a player's turn, the player is faced with two options:
• roll – If the player rolls a o 1: the player scores nothing and it becomes the next player's turn. o 2 - 6: the number is added to the player's turn total and the player's turn continues.
• hold – The turn total is added to the player's score and it becomes the next player's turn.
The first player to score 100 or more points wins.
As you can see there are few rules to the game are and the gameplay is quite simple. An example of the playing of this game, showing only one round – that is each player having one turn – is shown below (also taken from Pig (dice) Wikipedia page):
For example, the first player, Ann, begins a turn with a roll of 5. Ann could hold and score 5 points, but chooses to roll again. Ann rolls a 2, and could hold with a turn total of 7 points, but chooses to roll again. Ann rolls a 1, and must end her turn without scoring. The next player, Bob, rolls the sequence 4-5-3-5-5, after which he chooses to hold, and adds his turn total of 22 points to his score.
The game pigs has a number of variations including the use of two dice. This could be implemented in your program through a menu choice ‘Options’ which sets the games parameters (i.e., number of dice, number of players, special Pig number [default is 1], or the winning score to end the game [default 100]).
Other Suggested Games
Some online examples of text-adventure like games that can be used for ‘inspiration’, include:
• Hammurabi http://www.hammurabigame.com/hammurabi-game.php
• Zork http://thcnet.net/error/index.php
• Star Trek http://www.vavasour.ca/jeff/level1/entry6_preview.html Also, think of some traditional games that may be used for inspiration:
• Cluedo http://en.wikipedia.org/wiki/Cluedo
• Risk http://en.wikipedia.org/wiki/Risk_(game)
• Battleship http://en.wikipedia.org/wiki/Battleship_game Card and dice games may also be considered:
• Cards – blackjack
• Yacht (dice game) http://en.wikipedia.org/wiki/Yacht_(dice_game) Word/text based games may also be considered:
• Word jumbles
• Word find
1) These games are only provided to give you some suggested ideas/themes, please feel free in creating a game of your choice – the requirement is that it must meet the generic features and functionality listed below!
2) Some of the games listed above require two players; in such cases it is not expected that students implement a complex “AI” computer opponent. It is sufficient for the second player can be controlled: manually using a different set of keys (or for each player to have a turn to provide input), or use of random moves/choices as performed in the lecture example of Tic-Tac-Toe.
Required Game Features/Functionality
In providing the required features (listed in the Demonstration of C++ Proficiency section above), the game must also support the following set of programming & gameplay features:
• Game Software Features o Implementation of an appropriate game loop o Changeable game states based on user input
• Basic/Simple User Interface o Accepts user input via keyboard input as commands/directions
o Is able to display/present the current game state in simple text based form (either as descriptive text or simple ASCII graphics)
• Multiple game (software) states o At least 3 game states – (1) menu/start; (2) play; and (3) end game states.
• A single, playable level o This may take the form of a single map/region/level/etc.
• Associated menu items:
o Options – allow the user to modify configurable features of the game (i.e., number of dice used, number of players, difficulty level)
o Instructions – present the player with a description on how to play the game, with the objective and user input detailed.
o Credits/software development process – a description on the design and development of the application. Present details on the variables used, the structure of your program (flow of execution) and the a reflection on the development process highlighting any issues you faced and how you over come them.
• File input/output o Loading of data related to the game (e.g., maps, a level, or descriptive text) o Loading & Saving of a high-score (like) data
• Features appropriate to the game genre o Dialogue to engage the player (interesting/funny) for an RPG style game o Potentially dynamic/random text (e.g., for a text adventure game)
Optional Game Features/Functionality – Bonus Marks
Additional features that you may wish to include for an additional 10% ‘bonus marks’ include:
• Use of dynamic memory allocation & pointers
• Advanced object oriented features such as hierarchies, polymorphism, etc.
• Use of log/error streams for debugging purposes • Multiple levels (game play advances once a level is completed):
o Levels have varied content (entities) or difficulties, for example:
? Level 1 – a single map
? Level 2 – 2 maps (passing through a doorway leads you onto the 2nd map)
? Level 3 – 5 maps in a cross pattern (centre map, with maps above/below and left/right) • Inventory – with collectable items. This will enable gameplay mechanisms such as:
o Collection of game items (e.g., gold, money, keys, swords, armour, etc.) o Ordering of items (e.g., you need to collect the key before opening the chest)
• Each file should contain a brief comment block at the beginning indicating the contents of the file, who authored it, date and student declaration, as shown in the example below:
/***************************************************************** * NAME:
* STUDENT ID: * UNIT CODE:
* ASSIGNMENT: * DUE DATE:
***************************************************************** * Plagiarism and collusion
* Plagiarism occurs when a student passes off as the student’s own
* work, or copies without acknowledgment as to its authorship, the * work of any other person.
* Collusion occurs when a student obtains the agreement of another
* person for a fraudulent purpose with the intent of obtaining an
* advantage in submitting an assignment or other work
* I certify that the attached work is entirely my own (or where
* submitted to meet the requirements of an approved group
* assignment is the work of the group), except where work quoted
* or paraphrased is acknowledged in the text. I also certify that
* it has not been submitted for assessment in any other unit or course.
* I agree that Deakin University may make and retain copies of this
* work for the purposes of marking and review, and may submit
* this work to an external plagiarism-detection service who may * retain a copy for future plagiarism detection but will not release * it or use it for any other purpose.
* * DATE:
* An assignment will not be accepted for assessment if the declaration * appearing above has not been duly completed by the author.
* Program Description * ...
• All code should be clearly commented with regards to the assignment question it answers and how it contributes to that answer.
• Please ensure that you “Clean” your solution in Visual Studio before submitting it (Under the Build menu, select “Clean Solution”).
• A 10 mark penalty will be applied if any of the submission requirements are not met.
This assignment must be submitted through the SIT153 CloudDeakin assignment dropbox and include:
• The Complete Source Code – a zip file that comprises the complete Visual Studio 2013 solution and project. This solution must contain the associated source code folders. It is expected that the source code is fully documented with relevant comments describing and explaining the features of the code.
Assignment is marked out of 100 and is worth 15% of your final mark. Breakdown of the marks is as follows:
1. successful compilation and execution of the game;
2. meeting the listed game requirements (minimum and additional features);
3. demonstrated use of the appropriate coding features (C++ features listed); and
4. sufficient commenting provided within the code, that is of adequate detail to explain the role and operation of the code statements.
An assignment rubric will be released shortly expanding on the above marking criteria.
PLEASE NOTE: It is expected that the majority of code provided for your assignment is your own, unique work. If you include code portions that are not your own, you must clearly reference the
original source. Both your document and your source code should provide a completed ‘student declaration’ form. In your code, this can be represented in a comment of your main code.
Students not adhering to these rules will receive a mark of 0 (zero)!