Teralitha, on 23 November 2012 - 04:05 PM, said:
The problem with matching mech for mech, it doesnt do for very dynamic matchups.
MWO's weight class matching is a bit more dynamic than a straight mech for mech matching, but I agree that it lacks a certain amount of interesting dynamic, and that I feel that it causes trouble because it means if a player picks a mech at the low weight end of the class' spectrum, they could be loosing their team 20 tons of mech...
Teralitha, on 23 November 2012 - 04:05 PM, said:
So basically.... your wrong,(Byran Ekman) basing matchups by tonnage is more fair (and fun/interesting)than matching mech for mech. I have played both tonnage limits(MW4 NBT, and mech for mech(MWO) And I still say tonnage matchups were better.
Khavi Vetali, on 23 November 2012 - 06:51 PM, said:
No, he's not wrong, you are completely misinterpreting his statement. He is stating that with just tonnage requirements, and even if you matched players up mech by mech, that skill would still be the determining factor. He is not making the case to have a matchmaker that matches people up mech to mech. He is making the case for a skill based ELO matchmaker that also takes into account tonnage.
I agree that skill is always going to be one of the strongest factors in match results, but I think tonnage is the wrong additional factor to use when trying to make matching close to even. BattleTech used to use tonnage as its primary method of getting two sides even while still having neither mirrored mechs, or mirrored weight classes, but after a while FASA (probably primarily due to the advent of Tech 2, and later Clan Tech) trying to get two sides to have roughly equal forces based solely on tonnage was no longer as good a plan as it used to be. So eventually they came up with Battle Value, which allows for many more and varied factors (including Pilot quality) than just tonnage to go into determining a value that is a better method of comparing if the two sides are roughly equal.
Comparing BVs of some stock mechs and a customized gausskat (-G2) that has dropped all the weapons for two Gauss Rifles with 5 tons of ammo, standard ten heatsinks, 10.5 tons of armor (half a ton more than the standard -K2) and a standard 195 engine.
Atlas AS7-K - BV 2,175
Atlas AS7-D - BV 1,897
Awesome AWS-8Q - BV 1,605
Awesome AWS-9M - BV 1,812
Catapult CPLT-K2 - BV 1,319
Catapult CPLT-G2 - BV 2,020
Hunchback HBK-4G - BV 1,041
Hunchback HBK-4P - BV 1,138
Jenner JR7-D - BV 875
Jenner JR7-F - BV 1,011
Raven RVN-4X - BV 820
Raven RVN-3L - BV 710
If you match make by equal tonnage per side rather than weight class matching, you can get a 65 ton Catapult that has a more potent impact on the outcome of a battle than a 100 ton Atlas and still have left over tons to add a JR7-F to the side.
We should also be able to see that match making by weight class has its issues, compare the BVs of the Atlas AS7-K to the Awesome AWS-8Q, or the RVN-4X to the JR7-F, and it should come as little surprise that we see more Altases than Awesomes (though that can also be explained by the 20 ton difference) and more Jenners than Ravens... Though even if we had BVs, Jenners might still be more popular than Ravens due to hitbox and hardpoint imbalances, or maybe Ravens having access to more of the non-weapon tech (BAP, ECM, ETC) will balance it out.
Battle Value and Player skill would likely be the much better method of going about making matches seem more balanced, and would help with weapon balance issues were some of the weapons (Gauss BC 320) that just are supposed to be better get nerfs or calls for nerfs, while other weapons that are just supposed to be not so great (AC/2 BV 37) get buffs that make little sense and make them out perform standard workhorses (AC/10 BV 123).
Not really sure how to get BV to account for Lag shield though... but hopefully we should see some netcode improvements to bring the high speed, low weight, low BV mechs that are being uncharacteristically potent down to a more reasonable level.
Edited by Asatruer, 24 November 2012 - 07:52 PM.