This assignment does not count toward the final grade.
PA submission: Text Adventure Game Level 1
- 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 1 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 10 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 program poses at least five (5) 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
|
|
||
|
branching is used appropriately to handle the player's choices
|
|
||
|
invalid player input causes an error message to be displayed and the program exists OR a loop is used to reprompt until valid input is provided
|
|
||
|
some amount of randomness is involved
|
|
||
|
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
|
|
||
|
|
|||
