Hi everyone. My names Carson "Kalkin" Eades, and I'm a Guy Gamer.
Account Details | |
---|---|
SteamID64 | 76561197999779383 |
SteamID3 | [U:1:39513655] |
SteamID32 | STEAM_0:1:19756827 |
Country | Fiji |
Signed Up | June 24, 2012 |
Last Posted | January 9, 2022 at 11:21 PM |
Posts | 2136 (0.5 per day) |
Game Settings | |
---|---|
In-game Sensitivity | 3 |
Windows Sensitivity | 6 |
Raw Input | 1 |
DPI |
1800 |
Resolution |
1920x1080 |
Refresh Rate |
120 |
Hardware Peripherals | |
---|---|
Mouse | Xai |
Keyboard | Das silent |
Mousepad | Icemat v2 |
Headphones | ATH-M50s |
Monitor | Alienware aw2310 |
BTMPLhttp://i.imgur.com/Vg4O2Rl.png?1
THIS IS CHEATING! Can we get some admin to comment on using phone to wake up players?
But I am the admin and I called him.
Legal play.
seanbudthey're being played at the same time and while i agree both could be good games there would probably be less than 100 viewers for vector vs root+6, if it's played/casted at the same time as HRG vs tri hards. best case scenario would be if one of the matches could be moved to make the cast a double header, but since ESEA insists on automating the process so much this is not always easy to do.
I'll be here tonight and I can always move matches with agreements. Let me know what you want to do.
obligatory post sarcastically referencing clockwork's and my competitive smash history
obligatory post cynically mentioning how terrible brawl was and how terrible this will be
seanbudThank you for the update.
Do we still have a guy talking to valve updating the client when this shit is released? What happened to that?
Again, thank's for the communication, it's nice actually hearing something.
Usually we are notified via the HLDS mailing list in advance of updates, the second one we weren't notified though it just happened.
milehighmilitiaKalkin...
generally, tf2 updates are the least of ESEA's problems.
I agree with you.
Norahttp://play.esea.net/index.php?s=stats&d=match&id=3344569
submitted a ticket for it. hopefully that wasn't entirely inappropriate, given the existence of this thread.
Done.
Who keeps minus fragging the entire thread?
milehighmilitiajust one of those nights with esea tonight.
Generally we can deal with updates when they come out, there are exceptions but most of the time we update fast enough. TF2 updated before matches started tonight and we updated in response before matches started. Then they updated again right in the middle of peak time for matches. There's nothing I can do to avoid cancelling matches when that happens; servers are already live with matches and now they're out of date and need further updated along with the client. It's incredibly unfortunate, I have no idea why Valve decided updating this late was a good idea. Over the years we have rarely seen an update this late on match nights.
I've posted on all the matches. Sorry guys, it's just one of those nights with Valve tonight.
Feel free to link your match comms thread here when you've reached an agreement if you'd prefer. I'll be checking it periodically.
Given that a second TF2 update was released at 10:30 est it is likely that we can't possibly respond in time for matches. If it's 20 minutes past your match time then your match tonight is cancelled.
Matches that were to be played tonight now have until 6/13 to be played. The reschedule process is simple. Have your captain/scheduler agree to a new date, time, and server location on the match comms page (looks like this http://play.esea.net/index.php?s=stats&d=match&id=3342141). When you've agreed please open a support ticket, or contact Killing or myself.