List view
Prepare a release branch, finalize any pending tasks. Tag the main branch as v1.0 upon release. Add the first official release to the Releases section on GitHub, including any release notes.
No due dateWrite comprehensive documentation in the README. Document each class with comments and explanations for key methods. Conduct a code review to ensure readability and adherence to standards. Add a section on assumptions and potential improvements Final testing and debugging to polish the gameplay experience.
No due dateTest navigation across rooms and boundary cases (e.g., moving in a direction without a door). Make sure game is initalized correctly. Fix any identified bugs, especially those related to game flow and user interaction.
No due dateDevelop the "InputHandler" class. Valiadate input for direction and provide feedback on invalid options. Add prompts to users to understand game moves and commands. Implement error messages (try-catch) where necessary.
No due date•2/2 issues closedImplement playGame() and setupGame(), define end and start conditions, add basic user prompts and feedback to guide player actions, make game replayable without having to restart and able to terminate (quit game) from within the program.
No due dateLoad room descriptions from text file so that each room with corresponding door is automatically created. Might be overkill. If so, just hardcode a "setupGame() method to initialize the rooms and doors.
No due dateGoal: Implement the player’s ability to navigate between rooms. Game shouldn't be playable yet. - create a basic text-based interface for navigating. - implement player class so it can keep track of where it is. - make door class connected to rooms. - make room class so each room has an uID and a description
No due date•4/4 issues closedGet the main classes populated! Make github branches, think of features and in which order each one should be developed.
No due date•4/4 issues closed