An example of this is the moderation system.
Just because we don’t hear about something doesn’t mean Roblox is not actively looking at it. Roblox does loads to help prevent cheaters/exploiters but we just don’t hear about it much. Besides, most games do have proper checks on the server to ensure nobody can ruin your gameplay (or at least not significantly). The fact that all of this happens behind the scenes doesn’t mean nothing at all is done to address the exploiters issue. Roblox also sometimes pulls a surprise attack on exploiters: by implementing a new injected dll check, then letting exploiters exploit for a while, and then baaaam, everyone who was detected gets terminated. And when one manages to do that, they have to update it every time roblox updates. That’s why there aren’t a lot of people who can get past all of them and successfully create an exploit. And they keep adding new ones or changing the old ones. The roblox client executable, aside of being obfuscated and packed, has many checks which when triggered by an exploiter will cause the game to crash. By doing that they made it way harder to achieve malicious code execution via exploits. For example the reason why loadstring was disabled in localscripts was roblox removing the compiler from the client.
That’s just an example from the top of my head, but there are obviously more of them. If you look at functions such as BadgeService:AwardBadge() you will notice it can only be used on the server. Roblox already does A LOT to prevent exploiters.
0 kommentar(er)
