isXander / isXander/Controlify
Have taps, double-taps and holds as separate bindable inputs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 341
- Forks
- 97
- Avg merge
- 1h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Building on bug report #541 which mentions you cannot hold buttons down for modded features that require held down buttons. Might also be connected with #226, which suggests adding input combinations.
It would be nice if taps, double-taps and button holding were counted as separate inputs. Would vastly expand how many possible inputs can be used. Would be useful with mods - for example, when using Xaero's Minimap and Xaero's World Map, hold on D-Pad Left would enlarge the minimap, while a single tap on D-Pad Left would open the fullscreen map.
Describe the solution you'd like
When binding the inputs, user could tap, double-tap or hold down the button in order to bind that specific input to the action.
Describe alternatives you've considered
Rework of the binding system, so it's a reverse of the current one. Requires a lot of work but honestly might work better. Instead of having a list of action and binding buttons to them, have list of inputs (maybe even visual representation for supported controllers?) and bind actions to them.
Additional context
Consider Fortnite's controller bindings.
For example, when using D-Pad Left, the possible inputs are:
- tap: places a regular Map Marker
- double-tap: places a temporary Enemy Marker
- hold: opens radial menu for all Marker types
Similarly, some face buttons can have two variants if Gyro Pause is set to them. There's even a bind that resets Gyro in Y-axis when tapped and pauses gyro when held
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current input-binding system and the related issues #541 and #226. The work is complete when users can bind taps, double-taps, and holds as separate inputs, including the controller examples described in this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100