@Neph: FYI I run 15 CSS servers for a couple of communities (of various types - Gungame 5, Deathmatch, vanilla and one glassfun 24/7 [that one is HELL to manage believe me :P]) and 2 TF2 servers (a normal and a custom map one) all of which are fairly busy to full.
The custom tab barely affected the TF2 ones for me.. However I do see how those that valve see as custom will be affected by the bump to the custom tab AND that some of the stuff that your "de-listed" for is a bit silly. That said I do agree with their stance of 32 player servers being custom (can-o-worms opened :P). I dont see CSS being affected either. Deathmatch and Gungame are the ones that are likely to be "de-listed" in this case, (although as pointed out I dont see how they could tell yet..) - these cater for a specific need anyway and all GG/DM servers will be located in the custom tab - so no problem! Of course if they mark "friendly fire" as custom that could be another matter ;) @Roman: I'd concur with those ideas (I have just said I LIKE the custom tab, and I do, but this is a much more elegant solution with the same effect). Regarding #2. I think that certain things should force the server to be custom. So for example having a plugin loaded, or - in the case of TF2 - having 32 players. Then allow server admins to tag their servers (perhaps with some pre-decided default tags (gungame, deathmatch, custom maps etc..) as well as custom ones) with the option to mark it as "custom" for the browsing. (there ya go Neph.. you asked me to post ideas...) It seems the me that the only real problem people have with the custom tab at the moment is it's lack of "visibility". Tom -------------------------------------------------- From: "Roman Hatsiev" <[EMAIL PROTECTED]> Sent: Sunday, May 25, 2008 1:27 PM To: "Half-Life dedicated Win32 server mailing list" <hlds@list.valvesoftware.com> Subject: Re: [hlds] Scrap the custome server tab > The idea behind Custom tab is to separate classic servers from modded > ones. The idea is nice, I really love it. > > But the problem is that you cannot clearly distinguish those servers. > How drastic changes to gameplay should be to classify server as > modded? This leads to endless disputes. > > Also, as it was pointed out earlier, you cannot tell that the server > is modded just by looking at some server variables. Remember mods like > Gungame or Warcraft3 which change gameplay dramatically without even > touching those variables. So any attempt to automatically mark server > as modded by checking some predefined list of servers variables is > flawed. > > So I believe that: > > 1. Separate tab for modded servers is unnecessary but what we really > need here is three buttons, always visible on every server list. The > buttons are All, Classic, Modded, so player can click either one of > them without need to open filters bar. And All button should be > pressed by default leaving actual choice to player without forcing it > on him. Educational text should appear in tips windows which come up > when user keep mouse cursor over one of those buttons for a few > seconds, not just once as it currently implemented. > > 2. Separation between classic and modded servers should voluntary, it > should be left up to server operator to decide whether to mark his > server as modded or not. But with implementation of server browsing as > suggested above I'm ready to give up on this one. > > 3. Tags system should be made available to all servers, including > classic ones. I still welcome an idea of marking all my servers with > my brand tag. > > Regards, > > Roman > > _______________________________________________ > 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
