Make input configuration more device-aware

Abierto
#535 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
lua
Área
game-dev

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Lua
Estrellas
30
Forks
20
Merge medio
3 d 15 h
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de panel-attack/panel-game

Todos los issues de panel-attack/panel-game

Issues similares

Más issues de Lua

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.