isXander / isXander/Controlify

Mod should give a chance to try an unknown controller before asking if it works.

Open
#320 0 comments 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 an unknown controller is being configured for the first time, controlify asks the user if they would like to submit the controller info to be considered for proper support in future versions, and crucially, it asks if the controller works with controlify, despite the user not being given a chance to test it first, this pop-up never shows up again if you choose to skip sending the info.

Describe the solution you'd like
Show a small controller in the corner, highlighting what buttons controlify detects are being pressed, so the user can confirm that all of the buttons are being detected properly.

Describe alternatives you've considered
Either make sure the user is in game when they open the settings before showing the pop-up, or until they save and quit after having tried the controller, I feel it could get complicated detecting when the pop-up should be shown with these options however.

Additional context
The relevant pop-up:
image

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 locating the unknown-controller configuration pop-up shown in the issue and trace how controller input is surfaced during setup. Define the small corner visualization around that flow, then verify that it lets users confirm detected button presses before being asked whether the controller works.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.