yes.
He's now asking himself if he's been using it wrong this whole time and maybe he could do more if he had more skill with it.
wp |
|
The Premade vs randoms problem is a direct result of using an ELO in the first place, because matchmaking.
The game client should match populations of premade to premade first, then filter them on ELO within that result to find a match.
It should not then start hoovering randoms in when no suitable premade matches are found, because this then makes the match premade vs random.
It should keep searching instead until another premade team is found.
For bigger game modes, e.g. 4v4 when 2 players are a premade within team1: match with another 2-player premade within opponent's team first, then backfill with randoms.
The reason ELO rank sucks for matchmaking are numerous in coh2:
1. people use drophacks regularly to change their standings
2. lag and distance from the servers reduces ones ELO artificially
3. premades smurf to get easy wins
4. the quality of randoms you get are diverse, yet nearly always terrible because of how broad the ELO search is
5. the game client can crash, people can quit during load etc, nobody wants these errors as any part of their matchmaking ELO experience (I'm not sure if the game writes any ELO data changes in these scenarios but it really shouldn't because the players didn't actually get to play)
6. the ladder system doesn't make sense nor provide any meaningful way to evaluate someone's skill because the quality of data its using to put people at their rank is bad
TLDR, the ELO method is gross in any game where you can get premades vs randoms. These are 2 different game modes and the client as well as the matchmaking service need to treat them as separate cases entirely. |
|
Sounds more like something to do with your graphics control panel, e.g. GeForce Experience, if you're using that. |
Vaz and operator09 know what they're talking about 
Cost though: Aws wouldn't be cheap and relic would need some way to bring steady income in to sustain all availability zones. Might be dlc, subs, etc.
I'd be fine with it if it meant localised match making |
The point of the post was that I chuckled when it happened because I saw in real time what Gachi was talking about, however at no point was the unit itself OP. The opponent refused to change their strategy and paid for it which seems to be part of the problem. A lot of people don't want to deviate from what they are used to.
Sounds like you deserved the win |
Was thinking about you during an earlier game today. Had double mortars against a Ost turtler 1v1, I got cocky and in the middle of bombarding him he got me with a rifle nade. Mortar survived and retreated while I pushed him back.
And if it had died... would you have been able to go back and re-crew it?
These silly situational examples are the bane of this forums' balance talks. |
Of course they will use COH2 engine. It's a well developed engine truth be told. If they iron it out and optimize it, I don't see why not. Also, the network part of the engine can be rewritten. Usually for these parts of the game, you implement different methods and strategies so that adding sh** to it is easier (similar to factory in Java, etc.).
I highly doubt everyone will connect to one server like in COH2. I'm pretty sure they will implement something new.
Hope so. I've lost more units to lag than inattention - the lag lasts longer than a grenade fuse.
The ability to match with geographically close players is very high on my wish list. |
Situation from my game that happened yesterday:
Flanked 120mm by 2 squads of PGrens, grenades out and CQC. 120mm team really dont give a f...k about 2 PGrens, just retreating.
I think, that mortar, which better in range, damage, abilities than stock 82mm team, must havent survivability like a god damn terminator. Strong long range unit virtually immortal for flanking by Axis assault units! If we imagine same situation, when GrW or ISG get flanked by 2 squads of conscripts - it well be death sentence for artillery team.
Were not interested in playing in your head games mate. |
|
Relic has the opportunity to implement cloud-based shards of on-demand servers that spin up to accommodate players' physical location and then start matchmaking them from there. e.g. AWS regions for those who want to do more reading.
If they don't do this, then we're all still royally fukd when coh3 comes out.
Will Relic embrace modern day cloud networking and matchmaking for coh3? doubtful, because they're using the same coh2 engine and I saw a vid where a dev proudly said 'we started coh3 immediately using the coh2 engine' - and I thought, that's a big FU to your international players already.
Let's see if they do a big dev reveal post about their networking tech. Absence of that says it all. |
|
Bofors is nothing compared to the flak HQ. It's easy to kill.
However I don't think the Flak truck is OP at all.
Both buildings are trivial to deal with. |
0
yuenchey
Relic Entertainment
NiteNite 
