Forum

Quoted from Spike Himself

Maybe the easiest way to ‘fix’ this is just reload the map?

Well, it’s not intuitive (and its slow). I removed it anyway, and submitted a bug report.

Quoted from Beef

Which conclusion wouldn’t have favored either of the teams? I’m curious. There was always going to be one team upset by the outcome. In an alternate universe this thread would be called “How is this decision fair, we were robbed of a win”

I fail to see how replaying would exactly be unfair to Rehash: they hadn’t won when the config messed up and both teams are equally at fault for that. Would replaying the match be in favour of Proton? Certainly less in favour of them than the alternative of awarding a win to a team who didn’t actually win.

If the conclusion of the game isn’t beyond reasonable doubt, which judging by this thread it clearly isn’t, then there should be no cases where this kind of decision is made with neither team moreso at fault than the other. Bad sportsmanship from Rehash for running to the admins and a bad decision from the admins.

Edit: Seriously, did nobody who reviewed the demo notice that Rehash didn’t even win the 2nd round legitly? I’m not sure why but the round ends after B is capped during overtime despite there being 2:30 left on the stopwatch for Proton to push C (with a significant uber advantage). This might infact be the first ETF2L win granted to a team that didn’t legitimately win a single round.

Just reviewed the demo as well, and yeah, Vali is right: rehash shouldn’t have been awarded the 2nd round either (althought pt.con didn’t actually complain about this).

Judging by some of the in-game comments, I’d say some members of rehash were very aware that they won thanks to a wrong cfg/bug.

Poor decision by the admins.

Quoted from slate

hmm watched the demo, seems that rehash won, because they tied (5-5) in a better time, leaving pt with no chance to win.

what i dont get though, is the B-cap somewhere after tick 150000. Rehash capped all 3 attacking and pt “lost” after capping B with 2mins left of the time rehash set to cap all 3.

glad someone else noticed, had that bug on public servers for months, only happens during overtime and only on A/D CP maps (steel/gravel..)

Quoted from Vali

[…]

I’m fairly certain this bug can’t be reproduced in a game where the config is loaded properly; I’ve never seen it happen on the first A/D round nor in games where the config is re-exec’d each round. It’s not a consistent bug though, sure, and there’s no way of telling unlike the 3rd round of this game where the timer is clearly fucked throughout.

well if this is true even two rounds might be in place :P pretty lol.

I’d say replay it, based on reading comments.

Quoted from slate

[…]

glad someone else noticed, had that bug on public servers for months, only happens during overtime and only on A/D CP maps (steel/gravel..)

mmm I was going to ask if it was in overtime… this is a known bug and Valve know about it (and the fix to it) but they won’t fix it.

edit: and it’s a consistent bug, Vali.

Quoted from droso

Make them replay the round. :/

sadly, not going to happen.
i have never seen the etf2l admins change a decision they’ve made on sth like this..
well, it probably has happened and i just can’t remember, but in the other 99.9% of cases the decision stands.

Just chill and listnen to http://www.youtube.com/watch?v=AaEmCFiNqP0