There is however a potential that remotes are not related to the actual cause or root of the problem, so I still recommend a good amount of research.Sinister M. To log them outside of the console, you can use the HTTP service or datastores to upload logs, but if you are in a game while it happens, then it will be the easiest to debug, especially since you might not be able to upload logs before the game crashes or shuts down. This will let you debug information in console from all remote events that are fired from clients. You can do this for any remotes that are added afterward too by using the DescendantAdded() event. StorageLocations will be a list of places you keep your remotes in, such as Workspace or ReplicatedStorage. Print('Remote invoked', 'name:', object.Name, 'client:', client.Name, 'data:'. To account for RemoteFunctions: (Be careful here, as you could be running this before your functions are attached! Try using GetPropert圜hangedSignal or just wait for some time before doing this) elseif object:IsA('RemoteFunction') then Print('Remote fired', 'name:', object.Name, 'client:', client.Name, 'data:'.

Object.OnServerEvent:Connect(function(client.

for _, places in ipairs(StorageLocations) doįor _, object in ipairs(places:GetDescendants()) do You can try looping through all remote events and adding a debug handler. If I knew about these non-secured remotes, I’d have fixed them much sooner. Any help is greatly appreciated.ĮDIT 2: I’m securing remotes that were not too secure that were implemented by other developers. This is really hurting our revenue and in these times it’s what we rely on. The game in question is Greenville Beta, and you can observe the attack as it happens right now.ĮDIT: We’ve observed some users with seemingly auto-generated usernames, sketchy avatars that are very similar to exploiters that have been seen in the past, and more. I’m wondering how I can log remotes easily without adding code to each remote in the game, if possible, and if not, possibly get support elsewhere on how to stop this attack. We’re not sure how to stop this attack and it seems to be multiple accounts doing it. Right after they join, the servers they join show that (!) Slow Game indicator in the server list. There’s sketchy players joining servers and allegedly shutting them down with exploits. I’m wondering how I can log remote events easily to figure out how it’s being done. Hey, we’ve encountered a problem that has cut our concurrent playercount down to a third.

Why is roblox shutting down events