Anti-Cheat Release : Visionary

Resources Community Resources
#23

Check in the client script settings that CAN_RUN_IN_STUDIO_OR_SANDBOXED is set to true and it is inside the client script is in ReplicatedFirst.

#24

you can’t do that on a local script hence it’ll always return the same error

#25

Alright,

The code is used by exploiters to priviledge escalate abusing roblox made Core Scripts since they have RobloxScript permissions on Roblox.

local actor = Instance.new("Actor")
game.ScriptContext:AddCoreScriptLocal("CoreScripts/whatever code you want in corescript folder", actor)

The Anti cheat also uses the code, and since the exploit script doesnt care whether the exploiter or a client localscript uses it, if the Anti cheat detects that it doesn’t give an error or is successful, bam. Your detected.

bypassing blocked function protections using corescripts

1 Like
#26

There isn’t a single exploit that doesn’t block AddCoreScriptLocal or actor instance creation

#27

who cares if you heard of it?

while AntiCheatListening do this is literally useless and proves nothing
the only time you set it to false is when one of these triggers
ClientReplicator[GetSecureString(“AncestryChanged”)]:Once(function(child,parent)
AntiCheatListening = false
Maid.__docleaning()
cleanupGame()
end)

game[GetSecureString(“OnClose”)] = function()
AntiCheatListening = false
Maid.__docleaning()
cleanupGame()
end

just disable the connection and its #gg
image

seperate thread for the handshake :fire:

#28

This was a valid detection back in 2023, and since executor devs make mistakes, it is still relevant today.

#29

How would I make a comparison of the code if I have never heard of it?

The reason it is on a separate thread is to prevent people from finding out that the Anticheat was flagged by the client stopping sending remotes.

There is literally 0 reason for the client to stop sending to the server unless the game is closing.

#30

Update 1.2.0

  • Added AES-256 into the handshake scheme and removed the previous one.

New release:
Visionary Anti Cheat.rbxm (34.4 KB)

#32

I’ve never seen anyone tried bypass this cheat with a real executor and not using studio to bypass it

1 Like
#33

code obfuscation has nothing to do with the fact that i can use getconnections to disable it

also citadel v3 is closed source and will never go open source its just dumb and makes it 999999999 times easier to bypass the anticheat

#34

Thanks for flagging my post, anyways I recommend you add sanity checks to coroutine.wrap :+1:

1 Like
#35

Why bro is having a beef with him :sob::pray:? Also wth is even citadel?

#36

a good anticheat but kind of a false flag simulator

#37

spam quartz to stop bricking stuff

#38

So are you going to obfuscate it or just never release it

#40

why would i release it for free
there are lots of games that would pay for an anticheat

#41

@Kealomon How come you dont incorperate some of the stuff in the valk anti cheat that you refrenece. Like you in my opinion use that as a base cause its so complex/has more detections

#42

I took alot of reference for the AES encryption from Valkyrie! But most of the checks no longer work. :melting_face: (Remote Spy, Infinite Yield)