-
Notifications
You must be signed in to change notification settings - Fork 2
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 entered commands.
-
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 can be triggered by typing into the terminal and pressing enter
. When the name of the command followed by valid arguments is entered, 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.
Commands must be added to the commands map in Terminal.java
using addCommand()
. They are composed of a name and an instance of the Command
interface. The following is an example for adding the debug command:
addCommand("debug", new DebugCommand());
Inventory System
Scoring System
Food Recipes
Level System
Player Actions
Ordering System
Stations
Items
Map Design
Customers
Pause Menu
Upgrades
End of Day Display
Day Night Cycle
Moral System
Debug Terminal
Game Interactions Tutorial
Backstory Cutscenes
Entities and Components
Input Handling
Game Screens and Areas
Fire Extinguisher Handler Component
MainGameActions Create Docket Triggers
Main Game Order Button Display
BackstoryCutsceneDisplay Test Plan
Test Plan for MainGameOrderTicketDisplay
Test Plan for MainGameOrderBtnDisplay
Test Plan for DocketLineDisplay
Test plan for RandomComboService
Test plan for SpeedBoostUpgrade
Test plan for DancePartyUpgrade