OK, can someone from Valve please reply to this? I am a bit confused
on the cvars noted below.
When changing cvars, in console it will say on certain modes that it
WILL allow ad-hoc connects, yet it does not. Since the list has
recently been a bit confusing, please explain the cvars in detail,
and assure us they work properly according to the explanation you
give. Someone earlier posted a explanation that made sense, but when
I tested it, it did not work as stated. Do various combinations has
various effects? Seem's so....
What I am trying to accomplish is fairly simple... For 6 non-MvM
servers I want quick play traffic, to show in the server browser and
allow console connect command like we used to be able to do. For two
MvM servers I want quick play, shown in the browser and allowed
direct connect via console with a rotation of the MvM maps.
At around 3am this morning I started playing with the cvars and noted
below is as best as I can tell true pertaining to the cvars;
tf_mm_servermode "1"
tf_mm_strict "1" ---> (sv_tags "_registered,hidden, mvm")
allows console connect using connect IP, but will not show in browser
when looking for servers I presume.
tf_mm_servermode "1" -----> (sv_tags "_registered, mvm")
tf_mm_strict "0"
does NOT allow using connect IP
tf_mm_servermode "0" ------> (sv_tags "_registered")
tf_mm_strict "0"
Shows in browser, no quick play traffic and allows console connect.
AS in the "old days".
tf_mm_servermode 2"-----> Strictly MvM rotation?
tf_mm_strict "1" ---> (sv_tags "_registered,hidden,increased_maxplayers,mvm")
*increased max player? Valve said set cmd line at 32 for MvM... Is
this a penalty of sorts?
Allows console connect
Why is this getting complicated? Any clarification from Valve would
be wonderful.
Hutch
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
