Make input configuration more device-aware

Aperta
#535 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
lua
Ambito
game-dev

Direzione di ricerca

Start by tracing how the existing key configuration assigns devices and handles gamepads, keyboards, and local multiplayer. The issue proposes device-specific configurations, keyboard exemptions, and restrictions for custom multi-device setups, but names no files, tests, or entry points. Done means those rules are implemented while preserving the stated multi-device use cases.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Client-side enhancement priority: 1 - middle

At the moment, if you connect two controllers, you have to configure both controllers individually in the key config to effectively gain 2 usable key configurations even if the controllers are the same (have the same GUID, should work with the same configuration but don't).

Applying input configurations by device instead of binding one or multiple devices to a single input configuration has various advantages:

  • For anything detected as a gamepad we can just apply the gamepad configuration straight up.
  • For gamepads, you no longer have the issue of only having stick OR dpad available.
  • configuration setups that don't make sense are no longer possible, e.g. binding from several devices or having the same input bound to multiple input configurations in local multiplayer
    • this includes making it more difficult to brick your input config to the degree that you have to delete the configuration file to start over.
  • Once per-keyboard inputs are available, people are almost immediately able to use the same keys on different keyboards

Keyboard inputs should initially be exempt from this to allow people in local vs to work together to set up a configuration with no friction until the aforementioned per-keyboard inputs become available.

Obvious disadvantage is that you couldn't use legitimate multi-device configurations, e.g. foot pedal + joystick or other complementary input devices.
But all things considered these could still be made available with the current mechanics under the following restrictions:

  • a device used in one custom configuration cannot be used in other special configurations
  • a device used in a custom configuration cannot be used as its own main device anymore
Lingua principale
Lua
Stelle
30
Fork
20
Merge medio
3g 15h
PR unite (30g)
17

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di panel-attack/panel-game

Tutte le issue di panel-attack/panel-game

Issue simili

Altre issue su Lua

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.