| Account Details | |
|---|---|
| SteamID64 | 76561197974608015 |
| SteamID3 | [U:1:14342287] |
| SteamID32 | STEAM_0:1:7171143 |
| Country | Canada |
| Signed Up | February 24, 2014 |
| Last Posted | July 16, 2015 at 10:22 PM |
| Posts | 104 (0 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | |
| Windows Sensitivity | |
| Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
defyreillyIs there any word on when the esea season starts?
since lan is pushed back id say a week or two after that so maybe mid january? then again they always say last day to get a roster etc but registration is ALWAYS extended, maybe late january then
Don't count on it! :)
Last post on this early morning, we are looking at the options to see if we can actually push the match. Should be able to report back in the next hours!
Good morning to all!
FoxVandWhat's their reasoning for forcing you folks to play given they are going through with that, out of curiosity? Just because they can? How would you folks playing when it would best suit both teams ruin what ESEA has lined up?that have to follow their policy or w/e and it lies on whatever shooter says because he's the head dog for tf2
Sorry, just a bit confused as someone who is pretty new to ESEA (only played this season in this league).
i tried talking to tri for a few hours, and i've left the same message with killing, so all we can really do is wait to see what happens lol
I'm not the "head dog" for TF2, I do all League! :)
Foxthat's dumb
i was trying to write up a request about the rescheduling because of the circumstances but it said it would ban me for support ticket abuse for messaging them about rescheduling :|
Assuming you are writing a League ticket for a League issue (question), you wouldn't be banned for that.
First of all, let me start by saying that it's not because we (ESEA admins) do not reply to a thread that we do not see it nor talk about it.
Now that this has been cleared of. Here's the deal. I've personally reviewed pretty much all comments here and in the other thread I've seen in the past days.
I can understand the frustration after the announcement and we've discussed internally about it. We're going to revert back to 8 playoff teams this season as we've done in the past for this season.
Moving forward, I'll work on establishing the number of playoff teams earlier in the season to make sure everyone is fully aware of important changes like that and fully understands.
Killing / tri will update the Playoff post on ESEA in the upcoming days.
Thank you.
It'll be ready for the 2nd map, sorry about that. Technical issues!
enigmahey guys
i'd like to apologize on behalf of all us -- it was really miscommunication between parties
ESEA had no problem waiting until STV was fixed but we started the game under the impression that the issue was resolved
we'll wait and make sure STV is good to go for the next game
Thank you ;)
Mixup in the port forwarding, getting fixed right now. Good part, the demo is recording.
BlueberryVillainUntil ESEA unlocks the rosters and moves up teams, noway to tell how competitive/alive its shaping up to be. If you want to play it safe, sign up for CEVO and be guaranteed a season. ESEA isn't a lock to have a tf2 season at this point, nor has a single rep even replied to their S17 signup thread.
Moveups will be done as soon as all games / divisions are done playing playoffs, which should be in a few days if everything goes alright ;)
Also, I just want to point out, when I say to "Open a ticket", it's not because I don't "care" about the problem, and send you somewhere else. It's simply because it's the best way to log the problem, and get the proper people (specialists) to help you out, and fix the problem for good. It keeps a track of the issue, and it's not closed until fixed/addressed (client problems, server lags, etc.).
Please, don't take this the wrong way, if you already have one open, let me know the ticket #, and I'll see what I can do :)
clorgI guess that means there will be no writers, thanks for the reply shooter.
That's more something from Brett (Few), he handles everything related to ESEANews. I'll pass along.
bobbydababzI haven't even been able to play this season due to the client
extracrispyevery time my teammate connects to the server, it kicks him about 30 seconds after hes in and it says he must be running esea client. this isnt the first time ive seen this issue arise, however ive never had it myself so i dont know how to fix it. anyone whos experienced this, could you give us some suggestions on how to fix it?
Did you guys open tickets, under Client?
Also, it's not because I don't reply directly to your post that I don't see it :P
cookiecould you guys fix the lag at the beginning of the match?
Open up a ticket with details, and I'll have someone take a look at it.
sandwiches_timeESEA-ShooterblinKStill dodging the compensation though! How about this. If there are server issues going on, why not put in a rule that allows us to run our own servers using the ESEA configs of course as long as both teams agree. Then we can just forward the scores to admins to input manually into the website. This would save your admins from being bombarded on bad nights and allow us to get our games done without having to wait hours upon hours to get a 10 minute match done with. Didn't even mention the client issues. It either goes really well or really horrible. There should be alternatives.
I would much prefer to fix the issues (as we do right now), than take the matches elsewhere. I doubt it takes hours, after hours to change a server on ESEA.
Yet 16 seasons later and the client/server selection is still terrible. Looking into other options at this point seems reasonable to fix issues esea is either unwilling or unable to fix.
What do you mean by client/server selection "still terrible"?
cyzerIgnoring idiotic suggestions such as compensation and whatever drploxo said.. the main suggestions and whether they are implementable are going unanswered and we're hoping to know the viability of them.
1. Expanded stats (#9 suggestion) if you need an example of what I think players are hoping for are more the lines of www.sizzlingstats.com, I know the owner of that would be more than willing to help ESEA with any questions about implementing them (SizzlingCalamari is one of the nicest people ever) .. I mean it's not vital but it would be very nice to have after this many seasons.
2. DM on servers (#6 suggestion) getting 12 on a server does take some time and having this pregame mod on servers would be nice.. would also give people who connect early something to do. I know lpkane said something about having match servers as vanilla as possible but I feel this is a bit archaic
3. My suggestion of lowering backup fees, see my reasoning at #18
4. Some sort of backup plan on those days the client downright breaks because of a TF2 update or the client is just broken, maybe ESEA servers that can be put up that aren't required by the client in case of emergencies or the sort. And perhaps can be put up quickly in case it's a high profile match and stv isn't working. Dunno, just a thought.. though the client seems better this season although it might just be because I'm not using it as much.
Edit: oh whoops, #1 was responded to while I was typing this!
2. Something Joey brought to me, but I prefer not to touch the League mod during a season, to implement such a thing, and possiblity have small issues for matches.
3. That's not possible, unfortunately.
4. Like I've said earlier, things should be fixed, and not sent somewhere else. I think ESEA has made great improvements for the updates (I think we didn't have any downtime this season, thanks to the client team) :)
potWhy do virgina/cali/ny/georgia servers even exist? The money could go towards more chi/dal/denver servers
These servers are used by a lot of teams, so I'm not sure why taking them down would benefit the players.
AloSechow about medic stats?
AloSecmedic stats?
Sorry, I didn't reply to your message first, but I noted this :)