Related question: do ESEA scrim servers work?

Potentially Heroes is the only team that's dead but not official, as far as I know. If they're willing, you'd need to somehow get three players on that roster to play matches with you for a week just to keep the team alive while you cycle through ESEA's roster add limit.

Godspeed.

The prizes for CS:GO are the same as well, with ESEA market coupons for the winners, so it's not as if this is just our issue.

Of course, that doesn't change the fact that they seem to have completely yanked prizes just when PUGs have started to really get going again. It's one of the few incentives to get people to pay and play with the system in its current state.

There isn't any integrated Mumble that works with the game server and moves people automatically, but seeing CS:GO players use in-game voice makes me think that's just something ESEA isn't able to do.

That figures.

Unfortunately most of these don't apply to TF2, but definitely do let me know when someone tries to speedhack on client.

I'm exactly as bad as I said I was. Maybe even more.

I didn't come into this season expecting to win a match at all, but actually getting crushed as badly as we are really saps your motivation. It doesn't help that we have a stretch of over two weeks in which we won't expect to win a single round, let alone come close to winning a match. I've been told that the second half of the season will be easier when we get matched with teams with similar records, but that doesn't exactly reassure me with how we've been doing.

Managing a team is extremely hard, and our lack of practice/play together as a team is probably going not going to end up well for us.

I do like the flexibility of being able to schedule matches at desirable days, but this week we're playing three matches in four days, and not being able to have any decent practice on Metalworks isn't going to help. Not that we weren't going to get rolled in both matches anyway, but...

Saving ESEA was great and all, but I'd be lying if I said that there weren't major issues that need to be fixed. Server hiccups are simply atrocious, and having to replay an entire match over a week later because the server crashed with 10 seconds left in the game is just terrible.

Ultimately, I'm left questioning my decision to enter Open. I don't think I was ready as either a team player or team manager, and I don't know if I'll ever be truly ready.

I imagine that most TF2 players that weekend will be heading to FITES, which is being officially covered by eXtv.

Hey all. Recently I've been working on some live graphics for TFTV streams, two of which have debuted - the team info graphic (with logos and extra info) used previously in coverage and the new ESEA stats graphic which debuted in last night's casts. Obviously, they could use quite a bit of work in both conforming to the TFTV graphics style and in actually looking somewhat decent.

Since I'm a bad developer and an even worse designer, I'd like to get someone on board who can help give these graphics the glory they deserve and assist in designing and implementing new graphics to debut on TFTV streams. You'll need to have a sense of aesthetics, and knowledge of HTML/CSS/JavaScript/web animations in order to help translate your designs into reality. Being a poor college student, I can't offer any pay, so this would be on a volunteer basis, but I can offer the assurance that your work will make our streams more aesthetically pleasing and functional, and we can definitely work out some incentives if absolutely necessary.

If you're interested, drop me a line through PM here or on Steam. Thanks for your consideration and help!

We've experienced the same issue with our Mumble - it affects one random person in the Mumble, gets fixed after a reconnect, doesn't appear to target anyone specific, and almost always gets fixed when using another Mumble.

Based on that I'd say it's probably an issue with the server.

Thanks for the giveaway!

ESEA Schedule has been updated to reflect options in the URL. When you choose options, they will automatically be properly placed in the address bar, and this URL can be copied and reused to reload the same options upon another visit. Let me know if you have any issues with this.

I'm not too experienced with the required methods, but I'll see if I can get the options to persist to the URL.

The sticky header is required so that on low resolutions the options bar can expand out to display options. I'll try to figure out some way to make the bar more useful.

The colon in the week numbers is due to how ESEA sends me the week numbers. I'll change the separator in between the week number and the teams playing to a hyphen to compensate.

I got a response to my ticket:

10/10 support

I don't have any way of knowing what it's supposed to look like, so I'm afraid that I can't answer your question. As it stands, StatusSpec does not interfere with any of the elements you've mentioned in any of its current modules, so it can't be the plugin which is causing those issues.

As for overriding the HUD, StatusSpec HUD elements and changes are not enabled unless you explicitly switch those modules on, and they have their own separate resource files which you have to edit to customize their appearance.