It is not killing's job to coordinate your personal lives with your esea matches. I feel for your situation though.

ahhahahahhahahahahahahahhahahahahahah

the legacy of Killing in the Name #esea lives on

yea its strange why he said you *have* to replay

It is also not killings job to overturn a forfeit win when we had our people in the server on time. They where late. They got the forfeit loss. That should be the end of it. We dont have time to be rescheduling all our games.

Yeah, like Kace said, I don't think you should blame ESEA admins. They are going by the rules and it's not really their problem if your medic doesn't have time. There is always an option for backup to be used if you have one.

The match was scheduled. They where late. They got forfeited. We shouldn't have to change our schedule because they fucked up.

after this and the AG/FT situation, hopefully people realize that there's probably a limit to the amount of leeway you give your opponent and that you should report your forfeit wins earlier instead of letting the rope dangle long enough to hang yourself with

I don't think everyone here is totally understanding the situation.

The match HAD to be played by 10:30, by that time they can forfeit their opponents.
Their entire team was in the server before 10:30, the opponents weren't.
They gave them 45 minutes past the deadline, but they still didn't make it.

The forfeit was totally viable, and yet the guys who 'won' are getting the short end of the stick by being forced to replay a match that, by the rules, they already won.

As a Euro I'm not 100% sure about how ESEA run their operation, and whether or not they had some good reasoning behind forcing the replay, but I personally find it to be pretty harsh.

30 minutes past your match, you're no longer able to ready up for your match (it says you can no longer ready, contact an admin). At 32 minutes past eCg reported the forfeit win which leaves noodle is moist one minute to .start. Since it was 32 minutes past, they tried to .start but couldn't because the server wouldn't let them.

TLDR; eCg reported the ffw, noodle tried to .start but couldn't because of server stuff, I took it away

I hope that explains it well. It's kind of complicated.

Killing in the Name #esea: nothing is gonna change that
Killing in the Name #esea: find a time by thursday
eCg | Dakrah: what about the esea rules?
Killing in the Name #esea: I am the rules
Killing in the Name #esea: I enforce them
Killing in the Name #esea: find a time by thursday
Killing in the Name #esea: or i'm going to give them the ffw
eCg | Dakrah: why?
Killing in the Name #esea: why what?
eCg | Dakrah: I mean we'll try
eCg | Dakrah: but whyn would you forfeit us when they were late?
Killing in the Name #esea: the forfeit doesn't stand
Killing in the Name #esea: so it's irrelevant
Killing in the Name #esea: they are being more than accomodating for scheduling
Killing in the Name #esea: you aren't
eCg | Dakrah: we were
eCg | Dakrah: initially we could not do friday
eCg | Dakrah: and we bended our stuff to get there friday
Killing in the Name #esea: that's great and everything but now you gotta replay it
eCg | Dakrah: I still don't see the reasoning
Killing in the Name #esea: It really doesn't matter at this point
eCg | Dakrah: yes it does
Killing in the Name #esea: You can keep asking me
Killing in the Name #esea: but nothing will change
eCg | Dakrah: you're a professional league
eCg | Dakrah: that we pay to play
eCg | Dakrah: and we
eCg | Dakrah: being professional
eCg | Dakrah: were at our match on time
Killing in the Name #esea: You're paying me to uphold the rules
Killing in the Name #esea: that's what I'm doing
eCg | Dakrah: on top of being there on time we allowed them extra time to get on the server
Killing in the Name #esea: if you .reportffw before the 30 mins
Killing in the Name #esea: I wouldn't be speaking with you
eCg | Dakrah: they still weren't there by that time
Killing in the Name #esea: but you did and I am
eCg | Dakrah: fine
eCg | Dakrah: we'll find a time
Killing in the Name #esea: thank you
eCg | Dakrah: but this is highly unprofessional
eCg | Dakrah: and unbecoming of a league admin
Killing in the Name #esea: You can make an admin abuse ticket

"I am the rules
I enforce them"
~Killing in the Name #esea

LEAVE KILLING ALONE !!!

stop being mean to killing, hes crying in my arms right now.

damn bullies.

when you reportffw the other team has a minute to start the game

the enemy team tried to start the game when they got reportffw'd but it didnt work because it was past 30min which prevented them from starting (even though they tried to)

it wasnt a legit forfeit

Killing_in_the_name_#esea

HEED THESE WORDS

did you look at it upside down?

Killing was being pretty professional

trust me he can get a lot, lot worse

plus ffw's are gay anyways just play the damn game

Then one would think to put it somewhere in the rules for teams to be aware of the procedures. The ESEA rules only state the following regarding forfeit wins and reporting them:

Forfeit Wins & Loses
If a team does not have six players in the server "readied up" after 20 minutes from the originally scheduled match time, then the opposing team can force them to play with five. If they cannot field five, then the other team will be able to submit a forfeit win. The captain of the team should use the ".reportffw" in the game in order to submit the forfeit win.
Below is the listed amount of times a team may forfeit before they are placed inactive in the league.
All Divisions: Four matches per season

Here's my source for that:

http://play.esea.net/index.php?s=content&d=league_rules_TF2

As you can see, nowhere in there does it clarify that past the 30 minute mark a team cannot forfeit it nor does it mention that the other team is allowed a minute to ready. If we're supposed to be punished by this after bending our schedule for matches, it should at least be clarified in the rules so that teams may know beforehand.

If we had the time i wouldn't care but our medic had to make an excuse to his boss just so he could be there. We where there on time. We barely had enough time to practice. We haven't even scrimed snakewater yet and we have a match on it today. We dont have time for this shit. These things are scheduled days ahead of time. They agreed to the date and time. If we could make it there is no excuse for them not to make it.

So basically, now we know that you should .reportffw and .confirm before 30 minutes. As gay as a ffw is the system doesn't naturally handle waiting too long and it's your team's fault for not fielding 6. Be like carnage and smoke a victory blunt (although that one overturned too).

The Server Config is to blame; not Killing. Sure, technically that should have been a forfeit win. But due to your lack of punctuality (and consideration) the server wouldn't have allowed it in any way.
Killing did the professional thing and had you reschedule a match when you made an error in procedure.

While I agree that it's pretty gay Killing's trying to threaten your team with a ffw if you aren't able to reschedule, I think you should probably be a little more flexible as far as scheduling goes, like 9 out of every ten games turns into a 5v6 or ffw because people don't understand how to schedule properly or something gay happens and a team isn't able to field 6 players at the last moment.

Procedure needs to be written down. None of this is stated anywhere in the rules. We where punctual. We gave the other team 40 minutes to ready up and they didn't even have 5 in the server when we reported let alone 6.

should just flip a coin

Then that is there problem. Teams that are on time and following the rules as written shouldn't be punished because another team cant field 6 on time.

we did have 5 in the server and couldnt ready when you .reportffw

We waited as long as we possibly could for you to get 6. We where on time and had all of our players in the server. Nowhere in the rules does it say anything about waiting a minute for the other team to ready.

http://play.esea.net/index.php?s=content&d=league_rules_TF2