I will give context that she has been educating herself on commands and working on these for A LONG TIME, from what I've seen. Highly recommend folks try them out.

Thanks for making these!

super clean and having a scrim config vs a match config is a cool touch

added a few new commands to try to help with optimization and better hitreg, shoutouts (again) to mastercomms

https://github.com/TheSqrtMinus1/NEW-tfcl-configs/commit/a8c7a5f42faca49363a122d2cb832ca6d2b509b7

let me know if theres any issues or if you notice hitreg being better or worse

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

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

For me, the tv_port is the big killer for me since with my server host, not all my servers have the default ports for servers or stv. I honestly dont see a point in forcing it either since its the responsibility of the server owner to know what ports their game and stvs are on, and 99% of the time its set to default anyways.

steph is a g and can confirm she's been working on this for awhile. even if the current state of the configs isn't perfect, with how much work she's been putting into them, i'm sure it's only a matter of time until they're super legit. plus, as a developer myself, having every line have comments explaining what the each line does alone is enough to win me over

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

What causes you to say that? Curious what you exactly mean by "state of the source server engine".

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.

Just because the engine isn't updated doesn't mean variables magically stop working.

sv_clockcorrection_msecs was changed to 30 in CS:GO, and is set to 0 in many CS:GO competitive leagues. It definitely works in TF2 too.

The other ones were optimizations that I agree should be server preference, and not part of a standard competitive config. However, optimizations can affect tickrate and thus networking reliability so the stability should be at least investigated to see if they can be used in normal competitive play.

reverted most of the experimental settings per mastercomms request. there was some miscommunication (my fault) and i assumed she had finished testing them, when they were actually WIP (whoops).

That commit is here

also i reorganized the configs so that they take up less space, instead of the old style of

(=> meaning "executes", using the koth config as an example)

=> tfcl_6s_koth => tfcl_6s_base => tfcl_6s_custom

its now going to be

=> tfcl_6s_koth => tfcl_6s_base => tfcl_base & tfcl_6s_custom

saves a lot more on file space having 1 large base config instead of having 3 large base configs

that commit is here

also re: host_framerate 0:

it's literally set by default in tf2 to 0 and it has been in comp configs since as far back as i can look

re: tv_enable:

it's completely nonnegotiable that this command is staying in, i cant fathom why you would want me to turn off stv in a competitive setting

re: stv port and all the other hostname/tvname settings:

all but tv_port are in custom.cfgs, which means that people can (and should) change them to what they want. i've removed the "dont change these" lines, though

i've moved tv_port to custom, but it's commented.

final commit for that is here

i appreciate all your feedback by the way, please let me know if there's any issues

Why have different _custom configs per gamemode and not just adopt the setup ETF2L uses where your base config execute the custom config, which is executed when you run your gamemode ones.

The only reason I could see those being useful is possibly for whitelists, but if you already have access to the server to be able to edit the configs I would assume you'd change them in the regular gamemode config, or simply rcon and use tftrue_whitelist_id instead.

Also the GOLDEN I personally would rename to 'gc' (and lowercase for consistency) and also not have it set the servercfgfile to be itself, but revert back to the 'non golden cap' version of that gamemode.

----

In an ideal world with consistent rulesets for 5CP, and KotH between 6s and HL you could actually have 'tfcl_koth' as base koth config which is then executed by your tfcl_hl_koth or tfcl_6s_koth configs which then also 'say' in chat that the one for that specific gamemode has been executed with possible win conditions.

i added bball stuff and I renamed the golden cap configs .

more updates coming soon, im heavily considering what wiet posted but stay tuned