daid / daid/EmptyEpsilon

Enhancement - Weapons screen - separatley label shields controls from beam controls

Open
#2,642 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
869
Forks
222
Avg merge
18h 33m
Merged PRs (30d)
1

Description

The shields enable button and shields frequency selector do not have their own label, which makes it look like they are part of the beam controls. This was confusing for new players. I propose adding a "shields info" label to clarify that they are separate.

I also propose to change the word "info" to "controls".

If this sounds good I'll try opening a pull request (maybe two separate ones) in a couple days.

Example mockups:

Frequencies enabled Frequencies disabled
Current appearance Current appearance when frequencies enabled Current appearance when frequencies disabled
Proposed appearance 1: add "shield info" label Proposed appearance with added 'shield info' label when frequencies enabled Proposed appearance with added 'shield info' label when frequencies disabled
Proposed appearance 2: change "info" to "controls" Proposed appearance with 'info' changed to 'controls' when frequencies enabled Proposed appearance with 'info' changed to 'controls' when frequencies disabled

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Locate the weapons screen implementation and compare its current shield and beam controls with the proposed mockups. Done means the shield controls are visibly separated and the requested label wording is applied consistently in the game UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.