-
Notifications
You must be signed in to change notification settings - Fork 1
UML Diagram of playerProfileDisplay.java

Explanation of the UML diagram elements and its relationship with the evitation menu:
-The getPlayerPofile() function will return the current items within the JSON file -In the addActors() function, there is a loop which will iterate all the items returned by the getPlayerProfile() function -In the loop, it will preprocess the required information before plugging into the function to get the answers and show it on screen. -After preprocessing, it will plug in the preprocessed values to calculateAvgTi() and calculateAvgAtm(), so we get required info. -After getting all the required info, it will display all the information on the UI.
Relationship between playerProfileDisplay and the Eviction menu: -The eviction menu decides the win/lose result , which will affect the data record on the playerStatsInfo.json -When the player win or lose the game by selecting the traitor in the eviction menu, it will change the result value in json, it can be 1 or 2. -The playerProfileDisplay class will grab this result value and decide the total win and total loss. -Both the eviction menu and player profile class will share the remaining time value in the json file . -The errorNum variable in the eviction menu is equaivalent to attempt in the JSON. The playerprofile and eviction menu will share the attempt value in playerStatsInfo.json
- Uniform Pixel Grid Resolution
- Storyline
- Instruction
- NPC info
- NPC Communication Script
- Inventory-System-and-Consumables
- Storyline User Test
- Traitor Clues
- Game Characters
- Player Profile User Test
- Player Eviction Menu Sprint1: User survey (Team 7)
- Player Eviction Menu Sprint2: User survey (Team 7)
- Sprint3 - Win/lose Condition: User survey (Team 7)
- Sprint4 - Polishing-tasks: User survey (Team 7)
- Transition Animation/Special Effects/Sound Effects: Feature Overviews
- Transition Animation and Effects: Design Process & Guideline
- Sprint 4 User Testing
- Transition Animation & Effect: Code Guideline-Sprint4
- Sound effect when players complete npc tasks and hover over npc cards
- Fixing the clue bug
- Music Test
- Player Eviction Menu: Design Process & Guideline
- Player Eviction Menu (Feature Overviews)
- Player Eviction Menu: Code Guideline - Sprint1
- Sprint 1 User Testing
- Detailed Eviction Card: Design Process & Guideline
- Detailed Eviction Card: Feature Overviews
- Sprint 2 User Testing
- Player Eviction Menu: Code Guideline - Sprint2
- Sprint 2 Inventory System and Consumables Items User Testing
- Sprint 2 Inventory System and Consumables Items Functionality
- NPC interaction testing plan sprint3
- NPC interaction testing results sprint3
- NPC Dialogue Scripts
- Code Guideline
- Win/lose Condition: Design Process & Guideline
- Win/lose Condition: Feature Overviews
- Sprint 3 User Testing
- Win/lose condition: Code Guideline - Sprint3
- Enemy List
- User Testing 1: Enemy Image Filter
- User Testing 2: Enemy Animation and AI
- User Testing 3: Basic Attack