What he means is an equals sign being used to assign the steamed to a cvar.
Like a variable

tf_server_identity_token = "lallaalalalL" WRONG
tf_server_identity_token "lallaalalalL" CORRECT

Hope that helps.

On 31 Oct 2011, at 00:50, Team BOOM! <[email protected]> wrote:

  I’m sorry fellas, I know this has been discussed already but I’m still
not clear on the convar syntax with the “=” sign.



I have 7 registered TF2 servers. Some have an = sign inside the quoted
identity section of the convar and some do not. My problem is I don’t know
where the “=” Fletch is talking about actually belongs within the  convar
line. Below is the convar from one of the servers I run. Note there is no
“=” sign anywhere in the line yet the drops are working fine using on this
server.



tf_server_identity_token "BeH&>_VJ$T6&sgn"



Do I need to add an = sign somewhere to this line for some reason? If so,
can you reply with an example of what the line should look like with the
“=” in the line?



Thanks in advance and sorry for my confusion.




 ------------------------------

*From:* [email protected] [mailto:
[email protected]] *On Behalf Of *Fletcher Dunn
*Sent:* Friday, October 28, 2011 1:38 PM
*To:* Half-Life dedicated Linux server mailing list; Half-Life dedicated
Win32 server mailing list
*Subject:* [hlds] TF2 registered servers: check for rogue '=' in the
convarsettings



If your server is not getting Halloween drops, check if your config file
has an '=' in the lines to set the registration convars.



Also,  make sure you put the identity token in quotes.



If you have these two problems, you probably (quite reasonably) cut and
paste the two config file lines from the client console when you registered
your server.  That output erroneously had the ='s in them, and did not
quote the identity token.  We fixed the output soon after we shipped the
registered server feature, which explains why a lot of people not getting
the drops are also saying that they have been registered for a long time.



In case that does not fix the problem, the next update will provide more
verbose logging so such errors will not go undetected for so long.



Your humble servant,

Fletch

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to