Nice work! Some tips as I've promised to give:
- The category for vehicles like street cars that don't really fit anywhere is "OT", for "others", but in general any two-letter category is possible (it will just not be colored then).
- There's one issue that might arise with users using this: If combined with other racing games, one vehicle should be represented only once and then tagged with all games that it is included in (albeit the specific method used will be revised, so far only 4 games are implemented). In general, the software could just look for whether there is already an entry like this and then add Assetto Corsa to it as a game, if applicable, however, as soon as you get slight differences in the naming you will end up with effectively two times the same vehicle, named slightly different for different games. Some trickery might be necessary to get around this
- The race classes are relevant, in that each racing series has a tag for the class. This means: All vehicles that fit the class of the racing series are allowed to participate. In case of vehicle classes like GT3, this should be easy to correctly tag in the vehicles, however, in some cases you might need to split the classes up. If all racing vehicles are classified with the tag "race", they could only be used together, which is of course a complete mess
-> I can only suggest the following: As you can see in my full app, most vehicles are actually "their own class", so single-vehicle classes. I would try to implement some rules to tag "GT3" "GTE" and other vehicles alike, and if no actual class can be inferred, tag the vehicle as its own class.
Oh, i forgot to add the most important thing: Regardless of how far you will optimize it, this will already IMMENSELY help in pre-processing data, even for manual creation of CSV-files.
Best, Sönke
![Luca [OT]](/data/avatars/s/3235/3235113.jpg?1697196734){kind=avatar}
