Of course, that’s why I mentioned Dear ImGui—but that begs the question of why can’t Roblox see when UI libraries are being injected when they shouldn’t?
I don’t know much about DLL injection or detecting it, so take that point with a grain of salt.
That’s interesting. All the menus I’ve tested in my game either have random string names or are using the same names as the ScreenGuis already present in CoreGui. Even with these basic defenses they put in place, it would be ridiculously easy to detect them.
1 Like
Basically, I’m using ChatGPT to translate because I’m Brazilian and to ensure the grammar is correct.
3 Likes
Infinite Yield uses syn.protect_gui to do this. Since Synapse X isn’t functioning anymore, there may be another method I’m not aware of. If not, they can still hook on to whatever connection or method you use to detect their Gui and prevent it from catching them. This will never go away.
Don’t be silly, use Google Translate.
1 Like
Wait a bit, I’ll test it here quickly.
qual seria a versão desse infinity Yield
Ah, that makes sense. However, don’t use ChatGPT for that still—use a real translation software, like DeepL or Google Translate.
oops Roblox replied to the wrong thing. You know what I meant, though!
That is not in English.
The latest version may differ, I took the script and put it in my game a while ago.
– Dark Dex
… And the infinite yield is actually hidden, but it is still possible to detect the images used in infinite yield even when hidden.
This is true, I was able to detect those images being loaded. If a very popular game patches this though, the developers of the script will probably take action and patch the detection.
So, the question remains that, even with some guidance, it is not possible to detect via FindFirstChild or search directly. In the same way, it would be very useful if Roblox allowed this search.
OK Thanks for the heads up friend
1 Like
I think I made a mistake and I can’t find the infinite yield that gives me the dark dex anymore.
– infinity yield
What makes you think exploit developers won’t just try to work their way around that? You would have to call GetCoreGui() from the client, which they could hook onto.
1 Like
A guide or menu, as you prefer, still needs to exist somewhere. If Roblox allowed searching in CoreGui, there wouldn’t be much the exploit could do. Either it would have to create a workaround to try to hide it, or it would simply have to accept detection.
To avoid this, it would have to disable LocalScript, but that would be another problem. In the case of aimbot menus or any other type of exploit, they are basically disabled for a while.
Following this logic, Byfron wouldn’t even need to exist. After all, after it was implemented, exploits were disabled for about two months… and now they’re all back.strong text
Developers do not have access to the CoreGUI’s as some GUI’s such as purchase prompt are also part of the CoreGuis including the escape menu which allow the player to leave.
If developers have access to the CoreGui they may have malicious intent to force purchase of items or disable the leaving functionality of players. There’s more hidden features that the CoreGui has which are not meant for developers to explore on.
No it isn’t. Most executors have the feature built in which allows access to instances and services that are normally locked by Roblox.
No. I wouldn’t even usually have to explain this, but since people don’t want to read the security section in the creator docs, I will have to do.
Providing even read access to CoreGui is bothersome, unnecessary, and useless. From an engineering standpoint, making all Instances read-only just for developers to read them is very time and resource consuming.
It poses security risks. CoreGui is a service meant for Roblox Gui, it is not meant for developers to see or access directly. You can see what happens when developers even get a small vulnerability in their hands; when they can access CoreGui, they abuse it to hell and back.
Not only that, but it is completely useless for developers in the general sense anyway.
See, Roblox isn’t granting exploiters free access to CoreGui; the Client just has access to everything. Why? Because the Roblox application runs on the Client. It is the Client’s domain. The Client can modify CoreGui because it is on its domain and, therefore, can read, modify, or delete it however it wants.
Your “Core UI” detection would immediately get bypassed, not within a day later. It would take mere minutes. And it would be wide spread not even after a day.
7 Likes
Hyperion’s existence is one of the main reasons why exploiters are unable to cause as much of a rampage they used to cause before it existed. It’s an obfuscated anti-tampering software, very hard to deobfuscate and bypass completely. A mere “Core UI” detection cannot reach the level of quality it has.
The world of cybersecurity may contain problems that seem simple on the surface, but only a fool believes that simplicity is the true aspect of those problems.