Sometimes, a slave-monster pairing will give birth to a monstergirl. Monstergirls refuse to have sex with monsters, but will have sex with the player character. The trick is, monstergirls' stats follow the same rule as monster stats, and they will usually end up having better stats than their mother.
As you breed a monstergirl with player character, you will get slaves that are better than wild ones.
This is the way.
There's just one problem - player character has stats too, but they're hidden, and they're no better than those of wild slaves. So you will often have to breed player character a lot to get slaves with really good stats. It becomes more of a problem as your monsters and slaves become stronger.
It's not +1, but some percent modifier. It seems to be Lowest stat-highest stat, if highest stat, some chance to be 1.25ish time that stat.
The Range is (Mother, Father +1). After checking you have the max or min in the range (which can fail, since you can get a theoretical +1 over the range checked) it checks to make sure the value is a number that isn't zero from both parents. This is the variable a.
Then, it checks if it is randomly uncapped. This is by seeing if the computer rolls a number between 0-100 below the uncap chance. . . which is currently 3 as set in the playsettings.txt file. So you have a slightly smaller than 3% chance if the number
The Default script doesn't have the number, so for now I'm assuming the location is the playsettings.txt file.
Anyway, if you have passed the roll, you get to go into the uncap factor (50, same deal as above) * .01f * absolute(a). This variable is called num2 in the code. Or 50% of the value of a.
So if your number wants to be smaller, like deployment cost or sex time.
Return a-num2.
If bigger is better,
Return a+num2.
So it should always return a number closer to 50% better than the best. It also automatically rounds because it returns an Int.