>>56820492Yeah, I agree, it's frustrating to use a pseudo, legendary or even something like Slaking with a cool Pokemon for whatever reason only to see the BST drop far below 100 of what the original had.
>>56820406 I tried something with this example, where if two Pokemon's stats are within a certain threshold, you simply take the average between the two, then if one of the two stats is outside of that average, I weighted the final towards the higher stat, so my math ended up like this for Bastiodon(head)/Gardevoir(body), using a threshold of 30.HP = (60[head] + 68[body]) / 2 = 64
ATK = (52 + 65) / 2 = 59
DEF = ((168 * 2) / 3) + (65 / 3) = 134
SPA = (47 / 3) + ((125 * 2) / 3) = 99
SPD = (138 + 115) / 2 = 127
SPE = (30 / 3) + ((80 * 2) / 3) = 63
BST Total = 546
For the weighting, I used the same formula IF uses, but for a first pass, this makes the resulting fusion represent the qualities of both Pokemon comprising it much better than arbitrarily tying stats to the different parts of the fusion. The only issue would be to find a way to statistically distinguish between the two fusions, but I really don't care as I try to go for cool factor with the sprites anyways. But at the same time I don't want to go out of my way to edit game files to swap sprites, giving me the illusion of using a fusion that looks cool and is a statistically good Pokemon. Like, look at how many Aggron head fusions look badass but are dogshit because they won't inherit his two best stats.
