23 replies to this topic

[SethAbercromby]

Okay, the first results are in. First, let me explain the fundamental rules that the simulation followed:

1) Any unit can hit any other unit
2) A unit is guaranteed to do damage in a turn it begins alive
3) Each unit selects a random target each turn

Spoiler

While the numbers showed a very balanced result, they also showed one very important thing: The first kill advantage is decisive. Not a single game was won by a team that ended up one or more kills down after the first round of casulties, the best result being a draw.

For those interested in how round 21 went down (puls how the simulation operated), have a look for yourself

Spoiler

Edited by SethAbercromby, 16 February 2015 - 11:59 AM.

[PhoenixFire55]

SethAbercromby, on 16 February 2015 - 11:52 AM, said:

While the numbers showed a very balanced result, they also showed one very important thing: The first kill advantage is decisive. Not a single game was won by a team that ended up one or more kills down after the first round of casulties, the best result being a draw.

Which is kinda obvious considering all your "players" are absolutely identical, which, again, obviousely never happens in MWO. One thing it might point to is why "underhive" matches seem to be far better balanced then top tier ones as people tend to do random stuff there ...

Also, just out of professional curiosity, what do you use for random number generator?

[SethAbercromby]

PhoenixFire55, on 17 February 2015 - 12:35 AM, said:

Which is kinda obvious considering all your "players" are absolutely identical, which, again, obviousely never happens in MWO. One thing it might point to is why "underhive" matches seem to be far better balanced then top tier ones as people tend to do random stuff there ...

Also, just out of professional curiosity, what do you use for random number generator?

This was to be honest more of a simulation of an underhive match though. Everyone did damage as long as they were alive, but there was no overall cohesion or commitment to any target.

Whenever I need a random number in C++, I usually do it like this:

#include <iostream>
#include <cstdlib>
#include <ctime>
 
using namespace std;
 
void main (void)
{
	srand((unsigned)time(0)); //Using time as seed for the RNG
 
	int random;
 
	random = (rand()%12); //Returns a number between 0 and 11. Modulo operation is weird.
}

[Hydrocarbon]

IMO the 3/3/3/3 format so many players screamed for is one of the big issues. That narrows the pool considerably. The fact that it builds 2 teams separately THEN matches 2 teams with roughly the same average ELO is what really leads to steamrolls. The n00bs throw themselves at the enemy like lemmings, or they hang back and let the enemy take first mech sticking out of the fox hole & so on. I strongly feel if they combined those 2 teams into 1 then pulled them back apart, you'd end up with 2 teams that are MUCH closer to being equal.

I can certainly say MOST matches I get tossed in with people with grossly mis-matched ELO's. Several players have appeared to be either fresh n00bs or very convincing trolls with their complete lack of basic game knowledge. I've seen several teammates with stock mechs (<2/3 are champs), and that's with MINIMAL spectating. I bet it's worse than I suspect - I'm usually in the last 4 to die so I don't get to see all of them. I do usually get a lock on at least 10 of the opfor and I see the same crap. I recently saw a dual AC2 firestarter with a STD engine, and when asked it did not appear he was only trying it for fun. One atlas had LRM's, large lasers, and machine guns - all were linked to group "1". When he'd fire his LRM's, his LL would fire if it wasn't already cycling, and both MG's would flicker for half a second. He was killed while overheating, caused from firing so many missiles under 180m at a light mech.

I got 1150 in a PUG match and 29xx in a CW match this week, so I highly doubt I have an ELO as low as someone who doesn't know how to change his weapon linking or know what pressing "R" does.