The point is - that's impossible to do fairly. We DO run that plugin, but on the maps where it is disabled (i.e. "sm_respawn_time_enabled "0") that plugin is technically still RUNNING, but since fast respawn is disabled, the sv_tag is not set.
See my point - you can't just poll a bunch of servers running a plugin and ban them outright, as the plugin may be running but disabled for that particular map (which would therefore not require the "respawntimes" tag to be set). Actually, this whole argument would be a moot point if Valve could just implement settings in the engine itself that allows us the same functionality of the fast respawn plugins, and automatically sets the proper tag if/when they are modified (I think this would be the optimal solution). That way - server operators that want/need fast respawn times on certain maps/servers could transition away from using plugins all together, and Valve could implement allow a couple of months for server operators to change their servers over to the new system, after which fast respawn plugins could be outlawed all together ;-) On Tue, Jul 31, 2012 at 3:15 PM, ics <i...@ics-base.net> wrote: > I think that these plugins that Todd posted are really breaking the > rules of quickplay and the owners should be punished accordingly. They > might not do it willingly, might have just grabbed a plugin and now know > about the rules of quickplay. Then again, if they registered their servers > to receive traffic, they will know about the rules too. So, there should be > made a check which of these servers that use these 2 plugins are using it > as is, without setting the tag. Those plugins do not set the tag and they > have been disproved for it. > >
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
