100% I was planning on this,
Lemmie do this real quick.
also by emote glitching are you talking about people using roblox bugs or people exploiting them
Yes, but Eclipse blocks normal teleportation methods.
Also
What does the config mean about overheating
Hey! Just came here to ask something out.
Most of the scripts found in this module are eerie similar to the ones found in the demo place from this post. Did you update ForbiddenJ’s Anti-Exploit in any sort of way?
I use Heat Values as a way of detection I.E 1 = Exploiting, 0 = Not Exploiting
Yes, this is a fork of Forbidden’s Old AntiCheat as he has not updated this in 2/3 years I went ahead and forked it and this will be keep upto date.
I will be updating this with new detections and features every week, but yes this was forked.
You should mention that in your original post.
It should be like 2 = Exploiting 1 = Possibly 0 = Not Exploiting
UHH its called rogate in the testing game
Major issue
you seem to lack the knowledge that exploiters have access to the character
EXPLOITERS CAN DELETE THE FOLDER YOUR PUTTING IN THERE CHARACTER AND ITS REPLICATED
@NotBugle
Tested it with your test place and it does not cause any errors but add a check to see if its being destroyed.
This can be solved by using attributes. i’ve tried getting this issue fixed but roblox wont budge.
RoGate was the old AC name,
I renamed it to Eclipse
Dude you do know deleting the folder does nothing.
Its just a container for holding heat values for the client
If it gets deleted its fine, there is no error caused its just for the client to view, there’s even a option to not share heat values with the client
it is a dumb system
also why the hell should the client even know info about that
On your testing place, Noclip seems to work perfectly on the physics based parts.
I’d also like to add that AScriptingMonkey is completely correct, and there is a huge flaw in the system as it stands.
If you delete the whole folder, it does not cause any server-sided errors, just as AScriptingMonkey reported, however, if you instead delete even just one of the instances inside that folder, the whole system breaks, as it seems you are checking if the folder exists, but you don’t check if the instances inside the folder do.
Here is a code snippet that can be ran on the client to replicate this:
local Player = game.Players.LocalPlayer
for _, x in next, Player.Character:GetChildren() do
x:Destroy()
end
I don’t want to seem mean, but it looks like you spent more time adding comments to the configuration than you did working on the anticheat itself.
We can’t highlight your mistake, instead we make up excuses to make Eclipse seem bad?