rsr427
commented
2 years ago From the RD Thread: First, I believe just one other class would be best, to not fudge with the XP and AI adjusting. With 4 classes, you'd could be last but 5th in your class. (Reminder to add the recommended # of opponents in the opponent section. 25? I grew up watching F1 with 26 cars and that always "felt right")
We could give the user most of the control and suggest one faster class and one slower class that could be included. Leave it up to the user. So if the user is racing GT3, they could add LMP2 and be the slower class, or GT4 and be the faster class.
If you think this is fair, I can go through the car list and select the 2 MC classes per car class.
If you want me to create a cross reference matrix that gives you a whole slew of options from which the program could pick so that its different each time, I'm willing to do that too. In that form, GT3's could race against GT4, LMP1, LMP2, LMP3 or DPi. Some cars would have no MC options. Though Formula Truck and FVee could probably work... :p
You know better how to handle these types of arrays.
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: