Azurency / Azurency/CQUI_Community-Edition
Overhaul keymapping experience
- Dominant language
- Lua
- Stars
- 397
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
**Issue by [chaorace](https://github.com/chaorace)**
_Saturday May 20, 2017 at 20:29 GMT_
_Originally opened as https://github.com/CQUI-Org/cqui/issues/536_
----
Currently, we offer only a few options for key bindings and the majority are completely hardcoded. We need to reimplement so that the majority of binds can be configured from an in-game UI. This feature won't be a main focus until more pressing issues like #514 and #271 are resolved, probably post-beta release
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the existing hardcoded key bindings and the current in-game options UI, then determine which bindings and configuration flows are in scope. Done means the majority of bindings can be configured reliably from the in-game UI, with the final scope agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- frontend, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100