[B]Firstly hello guys i heard there was a wipe today i opened the rust searched for London 1 couldn't find it i tried to connect remotely via console 159.8.147.200:28015 this is the ip of it if i am correct when i connect via console it tries to connect Amsterdam 2 but if you look at this website [URL="http://rust-servers.net/server/36718/"]http://rust-servers.net/server/36718/[/URL] its up and running and i have this problem since i bought the game when i rust is open on google chrome it says dns_probe_finished i changed my dns several times but the problem is rust i validate the files thank you guys have fun.[/B]
[editline]7th January 2016[/editline]
[B]Okay guys so i find the London 1 on history tab only 5 people connected it says "Wrong Connection Protocol: Client Update Required!". There is no update for the version i am using but in steam Betas tab do i need to change the game version or some kinda thing?[/B]
Yes I have the same problem and so do most others because there were 250 people on the server suddenly it decreased to 5ish.
[url]http://www.playrusthq.com/server/3176/facepunch-london-i[/url]
I have noticed that but if we [B]​[/B]cannot connect how are they connecting are they the devs ?
[QUOTE=Perking;49475730]I have noticed that but if we [B]​[/B]cannot connect how are they connecting are they the devs ?[/QUOTE]
I doubt it probably people with some weird computer settings or something. So the ''bug'' or whatever it is doesnt affect them.
[editline]7th January 2016[/editline]
I mean havent the developers noticed the problem? Don't they wonder why their playerbase suddenly decreased with like 90%? Or did they not go to work today? Hopefully if there is a wipe they will notice the problem and fix it.
I guess they're using it for internal testing or something? Weird anyhow and it'd be nice with some information for all of us who are regulars at London I, but complete radio silence sadly.
steam->rightclick rust->properties->betas->prerelease or staging
but that server should be wiped in 1 hour if I understood it correctly, and then it is accessable through normal, non-beta access.
Sorry, you need to Log In to post a reply to this thread.
