This assignment does not count toward the final grade.
PA submission: Text Adventure Game Level 3
- Due No Due Date
- Points 1
- Submitting a file upload
- File Types cpp
What should you submit here?
Your source code for the Text Adventure Game Level 3 for any of the following kinds of submissions:
- "50%" submission (at least a week before your completed submission)
- completed submission
- redo submissions
Rubric
Find RubricKeep in mind that 3 students have already been assessed using this rubric. Changing it will affect their evaluations.
| Criteria | Ratings | ||
|---|---|---|---|
|
the game starts with a message setting up the storyline
|
|
||
|
the player has a set of relevant stats (e.g., points, health, magic, time taken, etc.)
|
|
||
|
the player stats are displayed when appropriate during the game play
|
|
||
|
the player's stats are contained within a struct
|
|
||
|
the program poses at least five (15) questions to the player that affects the output of the game (hereafter called decision points) ("affects" can mean: changes player stats, changes what the next scene is, or stops the game)
|
|
||
|
the format for the decision point input expected by the program is made clear to the player
|
|
||
|
every possible path through the game ends in some defined way
|
|
||
|
a clear message is displayed when the game ends so the user knows how them game ended
|
|
||
|
some amount of randomness is involved
|
|
||
|
at the start of the game, the player can choose to start a new game or load a saved one
|
|
||
|
at the start of the game, if the player chooses to load a saved game, the user is prompted to enter the name of the saved game file and that file is loaded in
|
|
||
|
loading a file advances the player to the state where they left off and all variables are updated accordingly
|
|
||
|
the player has the choice throughout the game to save, which saves the decision point they are at and the value of the stats is written to a file of the player's choosing
|
|
||
|
branching is used appropriately to handle the player's choices
|
|
||
|
input is validated and the user is re-prompted until a valid option is input
|
|
||
|
loops are used appropriately and where necessary
|
|
||
|
the program is broken into reasonable and correctly implemented functions
|
|
||
|
the program compiles
|
|
||
|
the program runs without crashing
|
|
||
|
the program behaves as a "normal" player would expect
|
|
||
|
all output displayed by the program is well formatted and spaced nicely
|
|
||
|
the source code uses appropriately typed and named varaibles
|
|
||
|
the source code includes useful comments that clarify logical chunks of the program
|
|
||
|
the source code uses appropriate indentation
|
|
||
|
the source code uses appropriately placed blank lines to separate the code into chunks that hang well together
|
|
||
|
the source code includes a comment at the top stating whether you worked alone or with others, and if so, who you worked with
|
|
||
|
the source code includes a citation for any code not from the zyBook or from class
|
|
||
|
|
|||
