AMS Talent File Editor 1.1.2

Changelog v1.1.1

• Added functionality for adding vehicle-files that contain two drivers.

Changelog v1.1:

• Fixed Property-List not resetting itself when reaching the end and going to the next driver.
• Fixed various bugs related to Drivers not being assigned to a Team.
• Added Buttons to add and Delete Drivers and Teams.
• Added a Button to assign a Driver to a new Team.
• Added the ability to quickly randomize Min-and Max-Values for Drivers and Teams. The tendency will be overwritten and in-between those values.
• Added the ability to Add Season, Vehicle, and RCD-Files to the already existing List in order to not have to re-create the Talent-and Season-Files when starting a new season (i.e. for adding additional Drivers, Teams, Classes, etc.)

Changelog v1.0:

• Added sorting capabilities for both Drivers and Teams, independently of one-another.
• Added optional "Tendency"-Property. The idea is that drivers and teams gravitate around this value, while never going above Max or below Min.
• Added "Leniency"-Property in connection with the "Tendency"-Property. The higher the Leniency for each driver's or team's Tendency-property, the more fluctuation will be seen in the values.
• Added some functionality that would allow to pinpoint which drivers or teams are getting irregular values.
• Fixed a bug where values above 100 or below 0 would be allowed when creating rcd-files. The code was already, there, but I forgot to reference it properly...

Explanation of Tendency: To use the new feature, check Enable Tendency for Drivers?" and/or "Enable Tendency for Teams?". Now you can assign the Tendency and Leniency for each driver (and/or team) and its property, which is the actual value that will be used when randomizing.
However, the randomizer will never allow for a value that is above the max or below the min. So, when your Tendency is way above the max, and the leniency is very low, you will get lots of values that will be rejected. At some point, the program breaks out of the progress and lets you know about the driver/team that it can't get acceptable values for and ask you to change the tendency and leniency for that driver.
All other drivers that are not causing a problem will be properly randomized.

For each driver or team, make sure to test the tendency and leniency for a bit to make sure you are getting the values you'd like!
In general terms, Leniency should, on average, provide a one-to-one range to the values you should get. This means that if Leniency is set to 1, and tendency 10, you should get a range from 9 to 11. If Leniency is 10 and tendency 10, range should be 0 to 20, and so on.

I implemented the tendency-property because I was feeling like a general randomization between min-and max-values was too simple, as I wanted a more detailed system. This way, over the course of a couple of seasons, you can increase the tendency bit by bit, as the "Driver" gets more experienced, while never exceeding their actual potential. This gives the entire process, in my opinion, a bit more of a "real" feeling.

I have implemented backwards-compatibility with Season-Files from the 0.9-Version, so you should be able to use the updated tool without any trouble!