What I find funny is that you explain all this, but I didn’t understand that this is something that will help in the beginning, not a permanent protection.
With all due respect, you guys from England and the United States don’t need to worry too much about this, you can buy good and cheap PCs there, besides, if you say that an ant cheat that has, I don’t know, a while task.wait() do will crash the client, it’s a joke, since most foreigners have at least 30 or 40 while true do in the jailbreak example codes that have 43 emergence response 32 in my entire game there are 12 while task.wait() do
What is your solution actually? This wont help detect hackers. They would come up with guis with randomized elements such as 0234250345 or fklsdfurtc.
caralho nao acredito que tu comentou isso kkk
local player = game.Players.LocalPlayer
local playerGui = player:FindFirstChild(“PlayerGui”)
if playerGui then
for _, gui in ipairs(playerGui:GetChildren()) do
if gui:IsA(“ScreenGui”) then
local name = gui.Name
-- Verifica se o nome contém símbolos ou números
if name:match("[%p%s%d]") then
warn("Possível GUI suspeita encontrada:", name)
end
end
end
end
Usando match, é possível detectar símbolos ou números no nome do ScreenGui, já que Roblox não usa símbolos ou números nos nomes de suas GUIs.
No, its not. Being unable to access the coregui is intentional through scripts and is because of security reasons.
The scripts run at a script level (level 2 i think)
and coregui scripts run at level 3.
Exploiters are just injecting their own code to run in the coregui as it’s visible on the client.
1 Like
Like others have said, there’s just no real point. While it sounds like a good idea, exploiters will literally just find workarounds to it. Besides, your detection code would have to be on a client anticheat, and i dont even need to explain the problems with that. Even if you do place that within one of your very important systems, exploiters will just hook it.
For example, when you used PlayerGui:GetChildren():
local oldnc = getrawmetatable(playerGui).__namecall
hookmetamethod(playerGui, "__namecall", newcclosure(function(_, ...)
local method = getnamecallmethod()
if (method:match("GetChildren")) then
--they can just return whatever they want. maybe just a blank table.
else
return oldnc(playerGui, ...)
end
end))
Basically, you’re better off with a strong server-sided anticheat. While client anticheats do offer some protection, mostly to script kiddies who aren’t using a script which bypasses it, they are incredibly vulnerable and just not really worth the effort.
2 Likes
The real problem is the fact that he hasn’t marked one of these responses as the solution because he is obsessed with trying to make his client anti cheat work.
There comes a point where you have to just accept the facts and surrender to them.
I’m sure there is people here who have already tried making client anti cheats like myself and are advocating against it.
You would think he would take our advice already.
1 Like
‘-’ o debate nao e sobre um ant cheat ou não e sobre o roblox permitir os desenvolvedores o acesso ao coregui
When would you ever need to access the CoreGui other than an anticheat
1 Like
They can. From what I know, there are barely any exploits today that actually, truly bypass Hyperion. If you want to put your tinfoil hat on, you could theorize that Roblox is unwilling to terminate large amounts of players, thus they are given lots of leeway. First, a 1-day ban, then 3-day, then 7, and only after that a termination (from what I’ve heard).
Additionally, bans are administered via “banwaves”, so someone who exploited can simply continue to exploit, even if they have been “detected”, up until the banwave actually hits their account. This helps keep Hyperion effective (at detecting exploiters) by making it more difficult to figure out if you have gotten caught, or if you have actually bypassed it, but has the downside of letting people exploit for longer.
3 Likes
With access to CoreGui, it would not be necessary to replace the inventory system. It would be possible to improve the “Tab” interface without having to overwrite it, just by editing the elements directly in CoreGui. In addition, a script would not be necessary to create and deactivate the current inventory, allowing the implementation of other functionalities in a simpler way.
Then it wouldn’t be read only…?
sim somente leitura se o caso fosse pra exploit, para outras coisas o roblox teria liberar o acesso no coregui
There’s a way into detecting CoreGUI “exploitation” elements such as “Menus”, I don’t remember exactly how but that was done already few years ago and it still works flawlessly, I can check back on the script if you want.
preload pra achar imagem no coregui