Multi-class races
- Lingua principale
- TypeScript
- Stelle
- 8
- Fork
- 3
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Let's add a field to the race setup section for "Opponents". By default we'll have "same class". Let's then define a dedicated dataset: a list of multiclass configurations. Each multiclass configuration is a set of classes. Any class may only be part of a single multiclass configuration. Whenever the race is in a class that's part of a multiclass configuration, we'll show the player on the race setup section which classes to set opponents to.
Alternatively, we could define multiclass configurations as:
* A set of (discipline, class) tuples. This allows a class that exists in multiple categories (say, GT3) to have separate multiclass configurations per discipline, at the cost of having to duplicate the entries for each discipline if we do not want them to be separate
* A set of (discipline, rank, class) tuples. This allows even more granular control, at the cost of even more duplication for cases where we do not want that control.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Look for the race setup section in the UI code and the data models for race configurations. Identify where opponent classes are currently defined and how to add a new 'Opponents' field. The multiclass configurations need a dedicated dataset; check existing data structures for disciplines and classes. Implementing this requires understanding how the UI interacts with race configuration logic.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- react, typescript
- Ambito
- game-dev
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100