isXander / isXander/Controlify

Allowing configuration of the displayed glyphs per controller and glyph fallback.

Open
#341 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
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.

When using generic controllers, or controller scheme emulation, for example in a situation like this, the shown glyphs may not match the actual controllers glyphs, or just the users' preferred glyphs.

Furthermore, in some cases (Dualsense Edge emulation) the detected glyphs may not encompass the entirety of a controllers input scheme, causing some glyphs to be missing:
image
^image depicts an assigned right paddle input for an action with PS glyphs which shows as a rectangle.

Describe the solution you'd like

Option in the settings to switch between available glyph sets (or maybe choosing glyphs for each and every input?) and fallback to other glyph sets for a button input with a missing glyph.

Describe alternatives you've considered

@isXander suggested on the Discord server making a resource pack as a workaround, which is better than nothing, however not very user friendly.

Another alternative could be showing both types of glyphs for an action like done in some games (I can't remember of an example, sorry ☹️).

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

Start by tracing how controller schemes are detected, how glyphs are selected in settings, and how missing glyphs are handled for generic controllers and emulation. Compare the requested per-controller glyph choices and fallback behavior with the existing resource-pack workaround; done should cover the affected inputs without displaying missing-glyph rectangles.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.