I'm not sure what other games implement an Elo based match making system where the individual player has to 'unlock' actual performance enhancing abilities and also has access to such a disparate range of playing tools.
I think most would agree that they personally perform better in a fully elited/mastered mech than they do in its stock variant so everytime one chooses to play a new mech variant for any given weight its going to be a given that your entirely reliant on your teammates to carry you for the difference in capabilities of your mech from 0XP to elite.
Ergo one expects to lose more against a properly Elo rated team when unlocking new mech chasis abilities.
Ergo one expects it to take longer to get the required XP to get the full unlocks.
0
Elo Matchmaking Pain
Started by Joe Luck, Feb 21 2013 10:43 AM
26 replies to this topic
#21
Posted 21 February 2013 - 12:43 PM
#22
#23
Posted 21 February 2013 - 01:21 PM
I still make the argument that ELO is only half of what needs to be measured. We would need a combination of ELO and Battle Value-like system to measure the effective use of a mech instead of just it's weight class.
So a pilot's ELO score would be 50% and his mech would be 50% of the score. Of course unlocking mech skills, upgrading the chassis (DHS, Endo, FF) will add more to a BV score and in turn would match tuned mechs vs tuned mechs and trial mechs vs trial mechs.
Right now the current mix of using a trial into a drop where there are 4-man's and other optmized mechs is only making the problem worse and throwing ELO scores off. Piloting a trial K2 vs a dual AC20's K2 will make an impression where today a trial Cicada can be put in with a maxed out Hunchback 4SP and selected as equivalents if the ELO scores are close enough.
It would also solve the problem of new chassis being introduced and ELO scores going all over the place as people get use to the new mechs.
-S
So a pilot's ELO score would be 50% and his mech would be 50% of the score. Of course unlocking mech skills, upgrading the chassis (DHS, Endo, FF) will add more to a BV score and in turn would match tuned mechs vs tuned mechs and trial mechs vs trial mechs.
Right now the current mix of using a trial into a drop where there are 4-man's and other optmized mechs is only making the problem worse and throwing ELO scores off. Piloting a trial K2 vs a dual AC20's K2 will make an impression where today a trial Cicada can be put in with a maxed out Hunchback 4SP and selected as equivalents if the ELO scores are close enough.
It would also solve the problem of new chassis being introduced and ELO scores going all over the place as people get use to the new mechs.
-S
#24
Posted 21 February 2013 - 01:38 PM
Hey Splinters, they just might do that in the future. However, first they need to do the mech's BV or figure out a way to figure out a pilot's Piloting/Gunnery score. In a way ELO does the Piloting/Gunnery thing. So perhaps down the line, they'll tweak the system more and work in BV for the mechs themselves.
#25
Posted 21 February 2013 - 01:54 PM
Working fine for me. Winning alot now because I always PUG and after 6 months of PUGing premade teams my elo is very low at the moment. I am sure it is also moving me up in the brackets everytime my team wins so seems like a good job.
There are the odd imbalances like placing every ECM mech (like 5 of them) on one team, but, so be it.
There are the odd imbalances like placing every ECM mech (like 5 of them) on one team, but, so be it.
#26
Posted 21 February 2013 - 03:04 PM
Felder, on 21 February 2013 - 12:07 PM, said:
Don't know if ELO affected it, but i was just in a match where opponent had couple atlases and stalker - our heavies mech was ilya and couple catapults. No need to say that we were quite badly butchered there.
Anyway, i thought that teams should be somewhat balanced tonnagewise (or at least assault vs assault.)
Anyway, i thought that teams should be somewhat balanced tonnagewise (or at least assault vs assault.)
… 'Cause you couldn't cap on 'em?
6 user(s) are reading this topic
0 members, 6 guests, 0 anonymous users