-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No. Keep using the same personal it140-projects repository created for
Project One.
Project One submits:
game_storyboard.mdgame_map.drawiomove.pseudoget_item.pseudo
Follow the current D2L What to Submit instructions for the exact submission process.
No. The milestone directions provide a small three-room dragon dictionary for the graded prototype. Your Project One movement pseudocode is a useful design reference, but the milestone uses the specified sample scenario.
move_between_rooms.py according to the current milestone instructions.
It can provide useful movement, loop, branching, validation, and debugging experience. You may reuse/adapt appropriate ideas in Module Seven.
However, the final game must return to your own Project One world and add the requirements that the milestone intentionally omitted.
No. The milestone uses exit for its simplified ending. Project Two ends when
the player wins or loses according to the final project requirements.
text_based_game.py according to the current Project Two instructions.
They are optional working files in this repository and are not graded submissions unless your instructor specifically tells you otherwise.
Yes. The SDLC is iterative. If instructor feedback or implementation work reveals a problem, update the design so the final code remains consistent with it.
The workflow evaluates the current graded checkpoint. During a checkpoint, a required file may still contain starter TODOs or may not yet differ from the starter state. Review the workflow details and finish the checkpoint before expecting all checks to pass.
No. The workflow checks basic repository structure and completion signals. It does not grade design quality or prove every unique game path works.