ucsb-cs56-projects / cs56-games-treasure-hunter

-
1 stars 7 forks source link

Fixed Issues # 50, 53, 54, 55 (and) 9, 26, 32, 51, 60, 61, 63 #62

Closed sangminoh715 closed 6 years ago

sangminoh715 commented 6 years ago

Detailed list of what we did:

Issue #50: Fixed the collision detection bug. Issue #53: Added javadoc comments for all methods and classes in the project. Issue #54: Removed javadoc from .gitignore and published the javadoc online. Issue #55: Created a pause screen (the GUI listens for pressing the "P" key and a pause menu shows up).

sangminoh715 commented 6 years ago

Note: The "F17-lab03.md" file was added to the base branch in the last pull request (from Lab03).

sangminoh715 commented 6 years ago

New improvements to the game since the first 500 Legacy Code project points were due:

Issue #9: Fixed input sensitivity. Issue #26: We improved the MessageThread class. If two treasures are found within 5 seconds of each other, the most recent message is still displayed for a full 5 seconds. Issue #32: A timer was added to the game. It counts down from a time (for now, it is specified within the code) and the player loses when the timer reaches 0. Issue #51 (Partially): We created a very basic main menu. For now, it literally just says "Main Menu" and has one button. However, the player no longer starts directly in treasure-hunting map. Clicking the button starts the game. Issue #60: The pause screen no longer glitches out and creates multiple "Pause" labels. Issue #61: We added a game loop. Issue #63: We refactored the pause logic. All of the visuals are taken care of in PauseAction.java and the logic is taken care of in GameComponent.java (because we need to update the timer accordingly).

Other: Refactored the tile-drawing and the treasure-setting (which was moved from GameGui.java to GameComponent.java) methods. As a result of the refactoring, it is possible to set the map randomly (grass, bushes, stones). In addition, we made it so that checking whether a treasure shares a location with a stone isn't hard-coded. In addition, we added more comments and updated the Javadoc accordingly.