Team 1 (Sprint 1) - Unit Selection Display/UI #2
Labels
approved
documentation
Improvements or additions to documentation
feature
New feature or request
Sprint 1
team 1
Milestone
Description
In an RTS game, one of the key points is to be able to interact with the things on screen. Most notably, you want to be able to select the buildings and characters or even interactable entities (resources that can be gathered) on the ground in order to give them orders or get additional info on their current state or even upgrade/level them up depending on the game.
This selection logic usually relies on two types of actions for the player: either drag a box around the things you want to select, or click on some of them more specifically.
During the game process, whenever the player hovers over an interactable element/entity, it will highlight it indicating that the user can select it. When it clicks or selects a legal element, the game will read their various attributes and generate a fixed-position box to display information to the player which options of either moving or upgrading/leveling up.
Other types and information of Unit Selection UI can including:
Examples
Information Box: This box will contain the core information of the selected element. Such as health, defense, faction, etc...
Information Box: This box will contain options such as upgrading/leveling up the selected element if possible.
Hover Selection: This box or outline will inform the user whether that element is interactable or not.
Legal Targets: Generally speaking, legal targets include buildings, creatures, and resource points. This range will change as the game is further developed.
Dependencies
The layout of the information box: This element needs to occupy a part of the area in the overall UI construction (#xxxx).
Buildings, Enemies and Friendly Creatures: This feature must select the generated objects to get their variables and properties for display (#xxxx).
Milestones
Completion Deadline: Aug. 30
Extras (optional)
Documentation
Members
The text was updated successfully, but these errors were encountered: