Forum

Sure I might be awfully biased because it’s our 2nd team but the way I see it the fair option for both teams would be to replay the round. Either from the beginning or trying to recreate the situation where the config broke.

TF2 really is not a game where you can look at demos and decide, yep, that team is gonna win because of this, this and this. Especially not on gravelpit where engies, snipers, spies etc are always present. Because pretty much anything can happen.

Given that both teams were unaware of the config messup, which you explicitly state is clear from round start, then I think it should be replayed.

If in future this same thing arises and one team (the ‘away’ team, ie. not their server) notices then they could surely choose to not say anything and have the point awarded in their favour. If a team says something and the ‘home’ team ignores it then the ‘away’ team should rightly be given it but as no team realised then I don’t see how either of them should be penalised when they both technically had the opportunity to notice the fault.

Quoted from konr

Apparently it’s because there is a rule that you must have the proper config loaded. It isn’t that you lost, it’s that it was your server and your config, therefore your fault.

Bollocks.

There is a rule you must have the server config loaded. They did.

What they did not do was this last part from 4.4:

In the case of both teams taking one round (1:1) there will be a decider round. In the first 2 rounds the teams should note the final cap time of the first team attacking. The team that has the best cap time (or more caps in the case a team did not cap all points) can choose if they want to attack or defend first in the 3rd round. Remember to reload the config between rounds, so teams can be switched.

While pt.con were at fault for not doing this, the other team were equally at fault.

So we come back to simply: Neither team was in a clearly winning position, and neither team were breaking any rules.

Just replay the damn game.

Quoted from Oxy

[…]

Rehash aren’t the sort of people who go default hunting.

Then why aren’t they just replaying? This sounds like a very clear case of default hunting to me.

Quoted from konr

The other team was equally at fault for not executing the config in someone else’s server? Meh, whatever man.

They were equally at fault because there is no way for the home team to more easily notice it than the away team. Rehash were either equally unaware, or unwilling to indicate the config wasn’t reloaded.

Quoted from konr

The other team was equally at fault for not executing the config in someone else’s server? Meh, whatever man.

I had this before in a highlander community challenge. The other team didn’t execute the config before the game. We rolled them, and then they went and cried to admins saying the game wasn’t played with the right config and the admins said we needed to replay the whole map.

How would not reloading the config cause that? Only thing i could think of is windifference, but score should have been 5-3 to rehash by what you described.

or was timelimit hit after after their capture (which shouldn’t have been on) ?

I’ve had similar things happen on a pub i help administer, when points were captured during overtime in A/D CP maps., the round would just end, I could never figure out why.

tl;dr
I don’t think anyone is to blame, but rather that it was an odd bug.

Quoted from Crasp

If both teams agree to replay any part of the match then that’s fine by us.

While keeping that in mind, don’t let yourself start a witchhunt after rehash. It’s up to both teams to solve the issue and by starting flame wars you don’t help either side.