![]() ![]() To recap: the default player argument of OnServerEvent is not exploitable in this manner. I also see making the statement of “never trust the client”, and I feel like that statement is drawn majorly out of proportion - while it is true that you shouldn’t have data/weapons/etc rely on information from the client, to disregard all trust in the client would cause for a major deconstruction of a games features. This is a week where us engineers get to try out some of our cool ideas for the platform. Roblox is ushering in the next generation of entertainment. It’d be outlandish to hold a firm belief that the possibility for a system exploit of this magnitude to exist is there, so I’d say don’t entirely count it out but don’t overly prepare for it’s presence either. Hey all Each year at Roblox we have a hack week. ![]() A popular childrens video game has blamed a virtual 'gang rape' on a hack of its systems. The picture was downloaded on the same day. Roblox said last year that it had 64 million players. September 2018 - RobloxPlayerLauncher (2).exe. ![]() It is my best understanding that the default player argument is thoroughly encoded and protected - and even if theoretically possible, ROBLOX would be quick to squash any backdoor that allows this to take place seeing-as it fundamentally disrupts the entire purpose of FilteringEnabled’s existence in the first place. April 2019 & July 2020 Roblox Client + Other Stuff (READ DESCRIPTION) by ROBLOX Corporation. Well this would not print anything, for one FireServer does not trigger a ClientEvent, however technicalities aside the answer is no. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |