Quote:
Originally Posted by Crystalos
I need shut down first server? When i start new server with old token?
|
Old SRCDS need to be terminated of before starting SRCDS with the same token on the new one.
Quote:
Originally Posted by Crystalos
So it works like, GLST ban my token then i create new on old server, starting server, stopping and this token applying to my new and start new server?
|
Your GSLT tokens aren't getting banned if you follow Valve's guidelines.
The tokens work like this:
- I have 192.168.250.250:27015 on my favorite list.
- 192.168.250.250:27015 has a token generating the server Steam ID "[G:9:8765]"
- On
February 27, 12:34 I'm refreshing my server list, where the server list in my Steam client finds the Steam ID "[G:9:8765]" for server 192.168.250.250:27015.
- The Steam client on my machine will cache history/favourites (Server Steam ID<-> IP combos) for 24 hours
- On
February 27, 20:33 you're migrating from 192.168.250.250:27015 to 10.20.30.40:27015.
- At the first server list refresh on my PC, after
February 28, 12:34 - my server will check what IP address the server Steam ID "[G:9:8765]" has, and update accordingly.
Therefore, tokens should be kept consistent for servers is you wish to be able to migrate them properly.
I would suggest having a token on your sever for at least a week before performing a migration, to make sure most of your player base will migrate (automatically) together with you.
At the server and Steam side, the IP <-> Steam ID combo updates instantly, however, to prevent excessively load on the Steam infrastructure with millions of players, your local Steam client is caching it for (up to) 24 hours, depending on when you last refreshed your Steam server lists.
It may therefore take up a anywhere from 1 second to 23 hours, 59 minutes and 59 seconds for your players to migrate, and different players will migrate after different periods due to the Steam client cache.
But that's quite much how the GSLT system works in regards to server migration.
__________________