I don’t think Roblox wants developers building exploit prevention around their CoreGuis. This means that the only uses for accessing the CoreGui are: What’s left in the CoreGui has information that developers shouldn’t know or are GUIs that the developer should not mess with. Roblox exposes APIs for what we should have access to, and moves GUIs that don’t need privileged access to the PlayerGui. I followed that with a separate hypothetical scenario for if the CoreGui was read-only or otherwise protected. To be clear, I didn’t assume that Roblox can’t make it read-only, I only considered a hypothetical scenario where Roblox allows changes. Making the assumption that ROBLOX wouldn’t be able to protect real CoreGuis from being deleted by a normal LocalScript is wrong. Server-side exploit detection is permanent and can’t be changed by the exploiter. Client-side exploit detection is never permanent and is a constant battle. If they did implement checks for new objects in the CoreGui, exploiters would just disable those checks. There’s no reason that Roblox cannot implement the same checks that you’re wanting to implement. You’re better off programming your game with a good server/client relationship. Legitimate developers have no need to access it except for detecting exploits – which as previously stated won’t even work all the time. In essence, CoreGui is locked to prevent malicious developers from being malicious. You should never need to access the built-in CoreGuis if you’re developing a legitimate game. Reading – not changing – the CoreGui isn’t as big of a deal, but it could be used to detect CoreGuis such as the menu or the purchase prompts in order to change or modify the game in order to misdirect or deceive the player. There are many kids that don’t know other ways to close Roblox, especially if it’s in fullscreen or on the console. If developers could change the CoreGui, then a malicious developer could trap kids in a game with seemingly no way out. In fact, nearly all CoreGuis except the menu can be disabled. The CoreGui is how the player accesses important functions in all Roblox games, such as the settings menu, the leave button, and purchase prompts. To prevent exploits, you need to run exploit detection code on a computer that they don’t control i.e. It would take a ton of checks to find all of these, and all of those checks can be disabled individually no matter where you put them.Ĭhecks like that can be good for slowing exploiters down, anyways, but it won’t be 100% prevention. GUIs can also be put in BillboardGuis, SurfaceGuis, or in the PlayerGui. The exploiter’s GUI could start using randomized names or existing CoreGui names to make it hard to detect or differentiate from real GUI, too. They can delete only sections of scripts or modify those scripts such that it looks like it’s doing its job to the rest of your scripts but it’s actually making no checks and just reporting “all good” constantly.Įxploiters can stick their UI in existing CoreGui objects anyways, so you can’t just check for new ScreenGuis in CoreGui, you’d have to check to make sure it’s not added as a descendant to CoreGui. How would you check for this? Exploiters can modify all code. In such a way that destroys gameplay by removing all client-side and interface functionality when disabled
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |