Does anyone have any concrete details as to the format of the tournament? I've heard of there being an invite group, and there's some information in the tournament rules, but other than that there's not much info.

The reason I ask is because I'd like to get Comp.tf's page ready for the big weekend, especially with the new bracket style that we're implementing, and it would be easier to update if most of the information was pre-entered as far as maps played and such.

See the "variable" parts added to the SpectatorTournament.res file in that diff? You need to add those parts to your file as well so that it works properly.

@Admirable: I've done some brief testing on your issue and managed to replicated it. I'm blaming it on Valve, since they apparently broke drawing yet again. It was working earlier, right?

Ah... did you adjust your MedigunInfo.res file to account for breaking changes in 0.16.0? In addition, statusspec_mediguninfo_charge_label_text was removed as a result of that update, so you can remove that from your config file.

If that stops the crashing, it's probably some stupid VGUI bug. I personally haven't noticed any crashes in my brief (<5 min) of testing today.

Which features are you using?

That's... very odd. Can you send me your entire HUD? I'll try to debug the issue (which is probably something wrong with VGUI/HUD drawing, since StatusSpec relies on that).

You should be downloading a release package from the releases page. For each version released, there are two downloads for each (besides the source code), one of which is a package for Windows (labeled with "-win") and one of which is a package for Linux (labeled with "-linux").

Load error: Required extension "CompCtrl" file("compctrl.ext") not running

Try installing the other version of the extension - if you installed the Windows one, install the Linux one as well, and vice versa. You might have loaded the one for the wrong OS which causes a load error.

The matches plugin gives 2 warnings, due to some unnecessary code that hasn't been taken out. It should work perfectly fine, though.

Also - I didn't announce it because I was planning to work on releasing another version but wasn't able to, but CompCtrl 0.1.4 is out with a fix for the /readystatus command.

Hm, that's odd.

Try launching the game with "-console" added to your launch options. If that doesn't work either for showing the output, I can't know what the issue is. In that case, I'd have to advise that you make sure that you are launching the game in insecure mode and that you're launching the game with Steam.

Is there anything you can get from above that spew? The failure reason should be above the "unable to load" portion.

That's not enough. You need to post everything around that.

Are you launching your game with "-insecure" in launch options? If so, post the console output that appears when the game first launches.

Based on my limited knowledge of Dota, that seems logical.

However, if the states are equivalent, that would imply that there wouldn't be queueing based on class, but rather that players pick which class they're going to play once teams have been formed in the lobby. It makes some logical sense because in Dota and CS:GO, nobody queues based on role.

Why can't I ever find this stuff when I'm trawling through the binaries?!?

That's a really cool find, and I really do hope that something nice comes of it.

It may not be as useful to ETF2L 6v6 players because configs work just fine, but this plugin provides automated match management, which natively supports halves, team switches, and stopwatch mode, among other things. It also has a player ready system that works similarly to ESEA/CEVO (which ETF2L players probably haven't ever really used).

If it's doesn't seem useful to you, then it probably isn't. That's fine. It's just a tool made for general use.

You can probably use it with TFTrue with no issue, but tournament configs may interfere with CompCtrl if not set up properly.

CompCtrl 0.1.3 has just been released.

Changes since 0.1.1 include the addition of ozfortress configs, a new command to check which players are ready and not ready (/readystatus), and a setting to automatically ready up teams when they have a certain number of players and all players are ready (compctrl_team_auto_ready).