I like the concept. However, since you're already tagging videos by class etc. it'd be cool if, like others have suggested, there were either casts, full match POVs and also howto videos like the old MGE vids.

I mean, instead of just not allowing them it'd be cool if people can filter out only the kinds of videos you have now, OR if they want they can filter videos for only comp POVs for a certain class, or comp howto videos for a class or whatever...

I understand the site is new, so maybe look at adding this down the track if you have to add a bit of extra code to account for many different types of videos.

Only the micro instances share hardware, and they're not powerful enough to run TF2 anyway since you don't even have enough RAM. Other instances aren't effected by what any other customers might be doing, the performance you're paying for whatever instance you have is guaranteed.

I had an ec2 instance boot up for 4hrs at scrim time during the week for a month while our normal provider (ozfortress has ~20 servers any1 can book for free for scrims/pugs) was having issues. It cost me ~$10 for the month. I had multiple people asking what host I was using as it was the best ping/smoothest server they'd used. I know of at least 3 other teams who started doing the same thing until our usual host fixed up its issues. FYI I was using a c1.medium instance and it was overpowered for a TF2 server but gives great, smooth performance. Obviously this hosting won't be the best for everyone, depending on where you are compared to the host, your ISP etc. is going to get you better latency to different hosts, but they're certainly good enough for hosting any kind of gaming server.

While the performance is great, renting an already running TF2 server is far easier. I think in certain scenario's this kind of technology is really useful. For example, maybe running a short 1 day competition where you need multiple servers but only for a few hours. Or ESEA finals when everyone tries to join STV and it fills up. Booting up a bunch of ec2 instances and running some 250 slot STV's on really great performing hardware for only a couple of hours would cost next to nothing.

The way atmo's tool does it, which works fine with spaces or any weird characters is:

File: blu_scout.cfg

spec_player "<insert player name with spaces and weird characters here>"

Then to switch to the player:

bind p "exec blu_scout.cfg"

You could make these files manually or use the tool to create them for you.

All of the iM v HRG games where amazing. Possibly the closest head to head match up of the LAN. Over the 4 maps they played each other they split the map wins 2 a piece, with only a 1 round difference in total round wins favoring iM.

It's all just friendly banter. They've done enough to make people eat their words so people are bringing stuff up now to poke fun, relax ;)

As a spectator, how good are these games to watch without quickfix compared to the recent ESEA lan. Great to see so many really fast paced, exciting TF2 matches already on day1!!

Who's Platinum? is he playing at i49??

Sad that there were ~1000 viewers on the TFTV stream tonight, and so many things contradicted the above statement made by Sal. From both teams and ESEA.

Original dt/FT match pushed back an hour, because someone hadn't paid. Luckily there was another match on, however that start was delayed because their roamer didn't have gunboats? and then long pauses due to ESEA issues. Then finally 90mins delayed the dt/FT match went live, but with no STV.

It's good to see so many viewers but very disappointing how it turned out. Especially when there are so many people putting in a lot of effort to try and improve the exposure and professionalism of the tf2 comp scene.

Is the cast on mumble (if so, details please?) so we can watch in STV with casting or will it be via the stream only?

I had the exact problem and tried a number of things before I worked out a fix, which turned out to be very simple after spending a lot of time on this!

1) Make sure your config.cfg isn't set to read-only.
2) Open TF2, go into advanced options etc. and change something. i.e. I changed 'automatically rezoom sniper rifle'.

It will rewrite your config file, and for whatever reason this fixes it. Has worked for me and others with the same issue.

Note: I think I did the initial create local server/join server before I did this, but pretty sure it's not necessary.