ID:1543235
 
Applies to:DM Language
Status: Open

Issue hasn't been assigned a status value.
client/var/single_connection = 0


So lets just say I compiled my game with the clients
single_connection = 1
option set.

The client is now only allowed to be connected to 1 server for that specific game title.

So lets say I am connected to my main server and try to connect to some random server someone is hosting.
This variable restricts me only to be connected to 1 world with the same name title at a time.

This would all be handled by the clients PC so games that use client side saving would find this handy.
There are a lot of potential problems.

1) What if two servers have different values?
2) What if the other server has been renamed?
3) What if the other server is on a different hub entry?
4) What if the player changes the value?

Realistically, you might be better off just querying the BYOND site for the game and parsing the data yourself.
1) byond_version var (client) and byond_version var (world) can be used for this.
2&3) You cant rename a world thats hub has been compiled and thats the whole point to this, its meant to be for 1 game with the same hub entry.
4) A player cant change the compile time of a client code.
This would fit better as a hub option than one set in the code.