You all seem to be misunderstanding sv_unreserve.  It's not a setting, it's
a one-time command.

For instance, let's say your server is empty.  Then a reservation cookie is
sent and for whatever reason, the lobby that issued the cookie doesn't end
up connecting.  Your server is then reserved and unjoinable by any other
lobby connections until 45 seconds later, which is the default value for
sv_reservation_timeout.  It is during this timeout period that you would
issue the sv_unreserve CVar.  That reservation cookie will be cleared and
you'll probably see another one come in rather quickly.

Using sv_unreserve in a config is pretty much useless.  When the server is
first started up, there are no reservations, so sv_unreserve does nothing.
If anything, you may want to lower the value of sv_reservation_timeout,
though I don't know the consequences, if any, of doing so.  The CVars
minimum and maximum values are 5 and 180, respectively.

Also, sv_allow_lobby_connect_only 0 didn't ignore lobby connections.  I have
that set on my server and I mostly get lobby connections.  All it did was to
allow people to connect through the server browser.

With the new CVars, sv_steamgroup and sv_steamgroup_exclusive, you're
basically getting the functionality that was most requested...easy community
access, with the ability to be publicly available and also group
exclusivity.

It seems like a great approach to the problem.  They haven't spent all this
time building the Steam Community for nothing, after all.

                                                    -Richard Eid


On Fri, Nov 14, 2008 at 10:44 PM, msleeper <[EMAIL PROTECTED]> wrote:

> I still have sv_unreserve set, and my private server has yet to get any
> traffic. The removal of allow_lobby_only doesn't seem to have destroyed
> the ability to make private servers.
>
> On Fri, 2008-11-14 at 21:41 -0600, turb0z wrote:
> > Has the removal of this convar disabled joining the server directly?
> >
> > Make sure you're still using sv_unreserve - from what I've heard so far,
> > people still can connect directly.
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Sugar
> > Sent: Friday, November 14, 2008 9:35 PM
> > To: [email protected]
> > Subject: [hlds] sv_allow_lobby_connect_only removed?!
> >
> > It appears sv_allow_lobby_connect_only was removed, which has disabed the
> > ability for us to ignore lobby connections and have our users connect via
> > the command line instead. This is a huge inconvenience.
> >
> > I would use the new "sv_steamgroup" cvar in the meantime as a workaround,
> > but it doesn't seem to allow for multiple groups -- and I'd like both our
> > clan members and regulars (2 groups) to be able to join.
> >
> > Can something be done about this?
> >
> > Thanks,
> > -Atreus
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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