I'd say Brian and Florian have different ideas, Brian considers a reserved slot to be for a VIP to the server, and Florian considers it to be a reserved slot for the server administrators. Both valid views, but that means that the preferred operation of the server depends on it's use. I guess that's why theres the option to set the sv_ variable or not :)
On 7/8/05, Florian Zschocke <[EMAIL PROTECTED]> wrote: > Brian Haskin wrote: > > > > I'm surprised people aren't used to this from 1.6 since that is the way > > the slot reservation I saw in 1.6 worked. > > Which pissed people off in 1.6, too, which is why the cvar was added > already to the hlds in the first place. > > > Once public slots are > > full, the server looks full and launchers want to wait until a slot > > frees up before connecting. > > Which is exactly the desired result of setting this cvar. > > > pretty much by definition server operators are going to be more > > concerned about making the lives of people with reserved slots easier > > than they are about the general public. > > Most server browser tools indicate reserved slots. Or maybe not but I > know HLSW does and they really should. Only the built-in server browser > doesn't. There are very simple ways to easily connect to the server > bypassing the internal server browser, e.g. a desktop link. > > I wouldn't consider a server operator who doesn't care about the general > public a good server operator. > > > Maybe a standard public cvar that said how many reserved > > slots there are would be a good compromise > > A good plugin should already have such a cvar. I think most for 1.6 did. > > Florian > > _______________________________________________ > hlds_apps mailing list > hlds_apps@list.valvesoftware.com > http://list.valvesoftware.com/mailman/listinfo/hlds_apps > _______________________________________________ hlds_apps mailing list hlds_apps@list.valvesoftware.com http://list.valvesoftware.com/mailman/listinfo/hlds_apps
