Recently DDoSers have been able to enter games, or use 3rd party websites to get the IP addresses of ROBLOX game servers and then DDoS that server until it shuts down, this has significantly affected many groups as their group games, which keep them active, get shutdown constantly, making us lose activity and membership.
This is a major problem as any user can click the F9 button while in game and view the IP of the server and then shut it down, this is what is being done to my Levantine Assassins Creed Brotherhood group and has gone too far.
This is a very serious issue that needs to solved sooner rather than later as it will cause the demise of many, active and fun groups, such as my group.
Please patch
They’re using something called Wireshark I believe?
I had this happen to a place I lent to some war clans today (they wanted to use a 100 player server). We have a discussion thread up already, but it’s good to have a thread filed in bug reports so it’ll be kept track of.
Even if not for exploit-solving purposes, the server IP should be moved to the server console tab for better organization anyway.
1 Like
The F9 thing is just a convenience. Perhaps it makes sense to remove it from the dev console, but it isn’t much harder to view the info in wireshark or several other ways.
I will say that we use this info for debugging the game client in some rare cases.
1 Like
@anon87984611 @anon28124821 @anon72762450 Temporary fix till ROBLOX removes the IP from the F9 console. http://www.roblox.com/F9-Console-Crashing-item?id=339200282
Either way ROBLOX should let us know If there are any plans taking place to stop the ddosing on our group places? Literally today my place was ddosed for the entire day and stayed at 0 players and we couldn’t do anything about it other than to hope that it would stop.
The future of groups itself is in the hands of ROBLOX at this point @anon28124821
Yeah we created something like that on the thread I linked earlier. That model you linked is kind of messy though. localPlayer:Kick() will never be run because the script would freeze in the loop above it, it doesn’t cover people chatting “/console”, and it’s not telling people why they’re being kicked (not everyone opens the console to find the IP of the server so they’ll wonder why they got crashed).
You don’t need to crash people either, preventing them from sending you logs in the local console. As xSIXx reminded me, the dev console has a message limit (appears it’s 1000) – after that cap you can’t scroll up anymore because the old messages were removed. If you print anything 1000 times it’ll push the IP out of the local console without preventing the local console from being used how it should.
1 Like
@anon72762450 It would be really nice If you shared that new model you guys created through this thread to help others like me 
Put this in the StarterGuiStarterPlayerScripts
for i=1,1000 do
print(string.rep(" ", i))
end
(Instead of printing the same string 1000 times I made them unique in case the dev console ever starts collapsing duplicate error messages into one)
Edit: You can also add a whitelist / exclude the place owner if you need them / you to be able to see the server IP for whatever reason
2 Likes
Wouldn’t this be better in StarterPlayerScripts so we don’t run it every time they respawn?
2 Likes
Oh, yeah – it would. Old habits die hard I guess. I haven’t used StarterPlayerScripts enough to make it second nature it seems.