Well pardon my lack of knowledge on the situation, but couldn't you:
1. Set a version constant in the code
2. Check to see if the server and connecting client's version match
3. If they don't, disconnect with a custom message?
Could all this occur before class table checking, like right on connect?
// Adam Maras (memzero)
[EMAIL PROTECTED] wrote:
Well, you can always put the version number in the name of the server, which
may be what he's doing?
Really though what you want, per previous discussions, is a way to alert users
to the existence of a new version when they try to connect and fail. And
ideally a way to seamlessly perform the update via Steam.
At 2007/11/17 11:54 AM, Adam Maras (memzero) wrote:
Garry's Mod beta (somehow) has [BETA] preceding the Game column contents
in the server, if I'm correct. Perhaps you could put the version in that
data field so that people can look specifically for servers of their
version.
// Adam Maras (memzero)
[EMAIL PROTECTED] wrote:
For what it's worth the last few times I asked this, the answer was basically
"no".
At 2007/11/15 10:39 AM, Jeremy wrote:
Is there a way to do proper mod versioning?
Disconnect: Server uses different class tables. isn't a very useful
error message when clients try to join wrong version servers.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
