My only concern with this change is that with a HTML motd, you can keep a MOTD central. That's a bit harder to do with a text MOTD, unless motdfile_text can be defined as a URL to a textfile.
On Thu, Nov 7, 2013 at 12:03 AM, Fletcher Dunn <fletch...@valvesoftware.com>wrote: > We're making two changes to TF HTML MOTD support that server operators > should be aware of: > > > 1.) HTML MOTD's will no longer be shown by clients that connect via > quickplay. Those clients will show the plaintext message instead. (The > file identified by the convar motdfile_text, which defaults to > motd_text.txt.) > > 2.) When sending a URL to the "info" panel by name, the URL must begin > with 'http://' or 'https://'. Note that this change does not affect > putting a URL in motd.txt directly, which has always required a protocol > prefix in order for the file contents to be interpreted as a URL. > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux