Tonight's TF2 update came right at the time a lot of people launch their EU matches (21:00 CEST), the update was large and the steam servers for server downloads slow or at least varying wildly in performance. This caused the update to take anywhere between 2 and 20 minutes. These long update times were experienced on servers from all the geographical regions we provide. They're still slow now, timing out while servers try to get the latest version info.

Since people are used to <5 second server boot times, many people ended their reservations within a few minutes (while the update was still running), and made new ones. This didn't help the situation as this had a chance of triggering a bug in Valve's steam server update tool causing the update process to freeze while trying to shut down, this left a handful of servers in this frozen state.

Luckily it seems everyone managed to get a working server within 15 minutes or so, but I'm not yet sure how to improve this situation. If an update drops close to match times, is big, and steam is slow, we're going to have a bad time.

Because they're Taiwanese, so Blizzard has to show the Chinese they're serious about protecting their interests.

I didn't sneeze, but something did forcibly leave my nose while reading this excellent post.

It's on all serveme.tf servers, but it's the "official" one by F2. That's because the sigafoo one points to F2's auto-update URL for this plugin, so it automatically downgrades itself xD

I'll fix that later. Thanks for letting me know alba, check your private messages for a little gift.

Update: Fixed, running the sigafoo version with the uber-pause-fix, but modified (source) so it won't commit sudoku

Some more updates:

- Greatly increased the average server launch speed. The system will now try to do a fast start of the server (takes between 1 and 5 seconds). If there's a TF2 update or the server is unreachable, the system does the old, slow start (35 seconds). The on-demand cloud servers are still fast at about 20 seconds.
- Added auto-updater for plugins and configs. Stole that idea from RGL, cheers
- Fixed the double response when you had plugins enabled and typed !rcon commands in chat
- Added a little ping refresh button on the reservation form, don't spam it, the TF2 server will ban you
- If you're from NA and end up on EU serveme.tf, we'll now suggest you try na.serveme.tf. With RGLs season in full swing there are lots of new faces visiting from NA and we did a poor job of directing them to the right region.

Cool idea, I've uploaded the current maps to serveme.tf and have given you serveme premium so you can upload updated or new maps.

It's good

Some updates....

- Removed the idle timer / 24h temp ban if you didn't use a server
- Removed ads, the $9 a month in Adsense revenue is not worth the privacy mess
- Removed relaypassword (it's the same as STV password now)
- Slightly improved the ping indicator, it's still not great due to browser limitations
- Any player in a premium reservation can now !extend in case you run out of time

Get an RTX card if you want to stream and play games, if you insist on CPU encoding, 9900k.

It seems like they played 7 vs Ascent.NA on a LAN server with some issues. Judging by the logs, no extended stats, we missed quite a cool game.

Banned.

Serveme cloud has London.

http://fakkelbrigade.eu/i/serveme.tf_-_free_TF2_server_reservations_2019-08-23_16-10-38.png

Serveme.tf, official iSeries "LAN" server supplier since 2015! 13ms to our Dutch and French servers from LAN.

RIP Multiplay LAN Clanforge

Please frontpage this, this is excellent. The main item on the frontpage is still the Moscow LAN viewer guide, which is now useless.

Just having the feature of logging in as another user as an admin isn't a huge deal in my opinion. As long as you make sure the actions done by these admins are logged properly it's a very handy tool to help customers. Has to be used responsibly obviously.

Now not having SSL, either by simply adding cloudflare (probably a good idea for a league site anyway due to DDoS protection) or getting a free cert from letsencrypt, is mind boggling.

What happens? Is this a potential XSS issue? Has anyone changed name to <script>alert("hi");</script> yet?