[CSGO] How to migrate players to new IP

j1gg · **Author**

How can I migrate players from old to new IP adress?
Is there any plugin for migration?
Ofc I can change servername etc but Iam lookig for other ways. Is there any plugin that does this?

YoloMySolo · 06-17-2017 , 09:39 Re: [CSGO] How to migrate players to new IP

There's no way to force players to join the new server, although you can make it so when the players join they get kicked with the new ip as a reason.

**DarkDeviL** · 06-17-2017 , 11:37 Re: [CSGO] How to migrate players to new IP

Use the same GSLT (sv_setsteamaccount) on the new server as you did on the old.

Everyone having your server in their history and favourites will automatically follow within 24 hours.

ambn · 06-17-2017 , 23:50 Re: [CSGO] How to migrate players to new IP

Quote:

Originally Posted by arne1288

Use the same GSLT (sv_setsteamaccount) on the new server as you did on the old.

Everyone having your server in their history and favourites will automatically follow within 24 hours.

Are you sure? Even if the ip had changed?

**sneaK** · *Last edited by sneaK; 06-18-2017 at 03:01.*

Quote:

Originally Posted by ambn

Are you sure? Even if the ip had changed?

I think this "feature" that came with GSLT's is pretty janky, I've tried it myself with a very low success rate.

In theory it's supposed to work, in practice... ehh

**DarkDeviL** · *Last edited by DarkDeviL; 06-18-2017 at 06:41.*

Quote:

Originally Posted by ambn

Are you sure? Even if the ip had changed?

That's what the GSLT''s was made for in first place.

Quote:

Originally Posted by sneaK

I think this "feature" that came with GSLT's is pretty janky, I've tried it myself with a very low success rate.

In theory it's supposed to work, in practice... ehh

It works fine, and I have tested it:

Each individual Steam client's server browser remembers that it last refreshed the GSLT <-> IP combination at 2017-06-18 12:41:59, and then it won't update the GSLT <-> IP combination until 2017-06-19 12:42:00 (and later).

This means that if John Doe has just refreshed your server a few minutes before you change IP, it will take him up to those 24 hours to propagate to his server list as well.

- At 07:03 I migrated one server, and refreshed server list. It changed the IP address.
- According to the Steam data, the last "refresh" was done on 07:04:09.
- On 07:08, I migrated it back to the initial IP address.
- On exactly 07:04:10 the next day, when refreshing the sever list, my Steam client got the original IP address back.

So yeah, it works. But since the gaming industry contains a lot of people that lacks patience, it may seem problematic.

File: \{STEAM_FOLDER}\userdata\{STEAM_ACCOUNT_ID}\7 \remote\serverbrowser_hist.vdf, contains:

Code:

"lastupdate"		"1234567890"

which is the last unix timestamp of when when your Steam client refreshed the sever list, the GSLT <-> IP combination won't be reloaded until 24 hours has passed away from that.

No one likes DDoS attacks towards their servers, right? -

This 24 hours delay was obviously made to prevent that "legitimate" use of the Steam network (GSLT <-> IP update) would cause a DDoS like situation where the Steam network would be hammered to death by 14 million (or more) online Steam clients at once.