Dark

These are 4 non-default, very rarely changed variables on a 10 year old engine that no longer gets a lot of love from its creator.

If they work, only 1 out of 4 (clock correction) has any bearing on competitive play, the others are the concern of server operators, who should prefer sticking to defaults (used by nearly everyone) instead of rarely used (threaded) optimizations.

As a server operator I favor stability over changing variables that hardly anyone else runs. That way when one of my servers crashes, it's more likely to be something a lot of server operators have already seen, instead of some rarely unknown network threading bug in the orangebox server code.

League configs should concern themselves with settings that affect competitive play, not try to do server optimizations nor change server names and passwords.

Stuff that shouldn't be in any league config ever, because:

• It gets people into trouble with their gameserver provider
  
• Or it's none of the league's business

tv_port "27020" // STV port
tv_enable "1" // enables Source TV
host_framerate "0" // unlocks server framerate, essentially
tv_password "tfclSTV" // STV password. ***REQUIRED FOR MATCHES, DO NOT CHANGE***
tv_name "TFCL SourceTV Bot" // STV name in scoreboard. change this if you want
hostname "TCFL 6s Match" // server name in server browser. change this if you want

Stuff that probably doesn't work considering the state of the source server engine:

sv_clockcorrection_msecs "30"
host_thread_mode "1" // turns on multithreading if the server supports it
lzma_persistent_buffer "1" // keeps a persistent buffer for LZMA decompression to prevent memory from being allocated and unallocated repeatedly
sv_parallel_sendsnapshot "1" // sends packets in parallel

RecordSTV can change the name and location of the recording. If you haven't set any of the RecordSTV variables, it should look something like this in the "tf" dir:

match-YEARMONTHDAY-TIME-MAP.dem

If you also start using demos.tf you won't have to worry about FTP-ing and looking for the files of course.

33.

He had a blood cloth (DVT) back in 2013 and recently had to get an infected abscess removed on his leg.
Still very very unexpected, his last stream was Saturday and he seemed fine.

Your ISP probably bought some extra IP addresses formerly used in India, GeoIP databases can take a while to catch up and not everyone updates them regularly (looking at you TF2Center!).

Not much you can do about it yourself, you could try submitting a correction here: https://support.maxmind.com/geoip-data-correction-request/

I can't wait to hear about a more modern piece of VoiP software, especially one that's:
- Free
- Self-hosted
- Open source
- Secure
- Light on CPU
- Light on memory
- Light on bandwidth
- Provides amazing audio quality with a codec like opus

Please do tell

Could be your router blocking access. If you can login to it, see if it has flood detection or other useless security voodoo and disable it.

I can ping both those IPs, so you're either IP banned by both, or there's something wrong with your connetion. Run a "tracert" to the same IPs.

In the same cmd prompt: tracert ip-address-here

Cheers, I made a mistake when creating the more recent NA servers, so they were missing a bunch of maps. Fixed now.

Sigafoo for FIA boss please

Just forget about "_off" configs, they're rarely complete and it just easier to issue an "rcon restart" or a real server restart to get a clean slate.

League configs also really need to stop touching things that are none of their business. Slot limits, sv_contact settings, server names, STV names, to name a few.
Having 128 clients in your server STV is a really bad idea anyway, since TF2 server runs on a single CPU core. That means the STV specators eat up a bunch of capacity of that single CPU core, leaving too little for the game itself. Especially now a lot of leagues use a tv snapshotrate of 66 and other settings that boost STV accuracy at the expense of more processing power.

Right click in your steam library, "backup game files" or click on the menu item named "Steam" and select "Backup and restore games".

A bunch of new developments that might be interesting:

- Thanks to Gameye, we've added a new feature, cloud servers. These servers get launched on demand (takes just 20 seconds) and this gives us more capacity and locations. Locations already live: Warsaw (PL), Moscow (RU), Frankfurt (DE), London (EN) and Sao Paulo (BR). Soon we'll have some more USA locations for this service as well, most likely New York and San Francisco.
- 8 new Dallas, USA servers from a new host/datacenter we haven't used before
- And soon, 8 new Los Angeles, USA servers

This should give na.serveme.tf some more capacity now ESEA will be out of the picture soon.

I'm a little late to the party, so first of all, good luck Sigafoo with this first season of real competitive TF2 at RGL (lolhl). You've shown your dedication and tenacity in your previous leagues, so I'm confident you have the skills to make this 6v6 league a success.
I am still hoping for some competition though ;)

Like others before me in this thread, I was hoping to change your/RGLs mind about two things planned for this first season:

The whitelist:
Using the global whitelist instead of a modified ESEA one would be great. You could still modify it mid-season if stuff seems broken, exactly like it's mentioned in the current rules for the ESEA whitelist. Basically a RGL-version of the global whitelist, but only if it's needed. No bureaucracy required.

External casters
I get the technical concerns about allowing more people on STV, but simply attaching an STV relay yourself (a good idea anyway) or requiring 3rd party casters to bring their own relay solves this.

That just leaves the exposure for the sponsor and the stream viewer numbers. I think more streams get more people to watch a game, not less, so just request 3rd party streams to use your sponsor's assets when casting RGL games. Seems fair to me. I'm willing to provide STV relays to any caster that needs them.

To anyone unhappy with RGL or Sigafoo and thinking it's unfixable, please support those working on alternatives and actually try to help them, because it's going to take the amount of effort Sigafoo puts into RGL to deliver a better product and he's already done this before.