-
Notifications
You must be signed in to change notification settings - Fork 1
Debug Terminal
The debug terminal is for developers to run commands while the game is running. When visible, the terminal is displayed in the bottom-left of the screen and commands can be typed into the terminal using the keyboard.
The terminal uses the Command Pattern to action commands entered into the terminal.
-
Terminal - Maintains the state of the terminal and actions commands:
Terminal
. -
Terminal Input Component - Processes input and triggers state changes in the terminal:
KeyboardTerminalInputComponent
. -
Terminal Display - Displays the terminal's UI:
TerminalDisplay
. -
Command - Defines actions to be taken when the command is triggered: e.g.
DebugCommand
.
The terminal can be toggled in and out of view using the F1
key.
Commands are composed of a name and an instance of Command
and must be added to the commands map in Terminal.java
using addCommand()
.
The following is an example for adding a debug command:
addCommand("debug", new DebugCommand());
When the name of the command followed by valid arguments is entered into the terminal, the command is actioned. As an example, the "debug" command accepts the arguments "on" and "off". So debug on
or debug off
would be valid commands.
- 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