Open Jesseable opened 2 years ago
Score screen implemented the way we desired with file readers and writing incorporating the multiple levels present. Also redesigned the home screen and made a new ButtonsInsert class that decreases code duplication. Disposing of the statusEffect entity and calling the death screen has been tidied up however disposing of the statusEffect entities still needs to be fully implemented.
Redesigned the MainMenuDisplay to a neater, more user friendly version. Made sure changes were implemented across all screens.
Designed a suitable scores screen. Aldo designed a suitable levels screen. Also added a working clock in the centre of the screen displaying your game time while playing
Unit tests added for the score calculation. Unit tests also added for the status operations
Had issues trying to minimise the collider components for the level buttons as they are overlapping at the moment
We decided to increase the Juiciness of the game by having certain title images change image when hovered over. We also brainstormed the possibility of having them do animations when clicked although that would be an implementation for sprint 4
Created new design for hovered title on the main page. When hovered, title turns to blue with a few changes on the font design. Animations needed in future sprint
Created new design for the score box in the scores page. We made sure the design style is consistent with the concept of the game, which adapts the 'technology' theme. And we decided to darkened the background for the scores page to increase readability
Status effects will go through an implementation revision for added depth of gameplay and code optimization. However, it is still very much a work in progress, as the code remains unstable under recent changes. It will be fully implemented in the next sprint and may be partially implemented in this sprint.
Description
Team 1 will be implementing multiple assets to the game in this sprint. These will include fixing up bugs from our previous sprints (such as disposing of the statusEffect entities). In addition, our main feature to implement will be an intuitive score display screen that updates the players score for each level. We will optimise the code already implemented, decreasing code duplication in other classes. We will also redesign certain colour schemes to fit with the game level displays. UML diagrams, sequence diagrams and multiple Unit and User tests will also be written.
Sub-feature/component (Bug fixes)
Sub-feature/component (score display)
Sub-feature/component (redesign Images)
Sub-feature/component (UML and Sequential diagrams)
Examples
-Inspirations:
-Improvements:
Milestones (all at 1600 AEST)
Completion Deadline: Sep. 15 Submission Date: Sep. 16
Extras
Documentation
Members