Anticheat Methods

Resources Community Resources
,
#45

How is that remotely related to what I just said?

1 Like
#46

i replied to the wrong thing smh

1 Like
#48

okay. this is a great bypass. rip juice wrld

i like kai cenat and ishowspeed

Make me mad an i will probably have to fanum tax you.

1 Like
#49

This post is insanewy innapropwiate pwease refwain fwom making deez posts or I may have to repwort you to higher authworities

6 Likes
#50

I don’t know how to quote the getnamecallmethod() line in this message but this is inaccurate information because it will just change the __index metamethod’s 2nd argument, namecall does not utilize null-bytes

#51

Yes right I forgot to edit this out

#53

Well you clearly don’t understand how metamethods works, that fakenamecall function will always return the same function regardless if you add \0 at the end or not, you’re not magically getting some other function so game.GetFullName and game[“GetFullName\0”] would be exactly the same as they return the same function. So this is really pointless as it serves no protection against exploiters

SafeCFakeNamecall = function(self, Method, ...) --> Does not invoke __namecall, but will invoke __index instead.
        return self[ProtectMethodString(Method)](self, ...)
    end

before namecall is called internally setnamecallmethod() is called, after that it calls namecall so whatever method is set before will be used. You cannot obtain that function and spoof your own namecall methods from a non exploit environment.

#54

Interesting, so how do you stop exploiters? I know about metamethods, and I know that you can negate some exploiters with certain methods like renaming serverscriptservice etc. But you might have a solution? Because if your posting to tell someone is wrong, I don’t mind that, but where is the solution ? Because us arguing about exploiter protection and working together to solve the problem is two different things.

1 Like
#55

I am just stating that namecall one is pointless, sure other methods like SafeCNewIndex, SafeCIndex you’ve posted here are effective and help in combating cheaters while the namecall one may just mislead other users researching this kind of topic

#56

So no constructive feed back to help the problem? Got it… I see so many people fight about exploiters and how to “Stop” them but no one ever post a solution lol.

1 Like
#57

I wonder if you even read what I have wrote before, there are no similar solutions for namecall as there are for index and newindex.

As for constructive feedback I’ve already explained on how that is misleading certain people on this forum who want to research this topic as that method regarding namecall serves no protection not to mention your misleading explanation on how it works because thats not how it works, and it doesn’t even call namecall in the first place.

Because getnamecallmethod() will instead return something along the lines of GetChildren\000\000\0004154565.1561216 (\000 being null bytes, which are string terminators in C++, meaning the rest will be ignored) which is NOT equal to GetChildren.

And you should really tone down your ego.

1 Like
#58

I have zero ego, because I know that there is always someone out there that is way better at scripting vs exploiters than me. The point of this place is to learn and have teamwork, I don’t really see anything like that in your post. When I go to my boss with a problem I normally get asked the same question, “Where is the solution.” I don’t think you get that concept yet so I will let it go at that. Thank you for your post in attempts to belittle the OP. But I don’t anyone is learning anything from you.

3 Likes
#59

It does work for when exploiters use __namecall hooks, as it won’t even trigger Namecall, hence why “FakeNamecall”. One could use hookfunction which can be detected with coroutine.wrap as stated above in my post. Why are you being so negative?

#60

Sure but yet again this has nothing to do with namecall and is just spreading misinformation

Because getnamecallmethod() will instead return something along the lines of GetChildren\000\000\0004154565.1561216 (\000 being null bytes, which are string terminators in C++, meaning the rest will be ignored) which is NOT equal to GetChildren.

#61

Yes it does have something to do with __namecall, as it’s goal is to completely not invoke it.

#62

and then its an awful practice, for one namecall hooks are expensive, individual functions are much cheaper to hook, so you’re doing exploiter a favour in terms of optimization. Its better to use namecall than to get barely any security out of this method

#63

So is it true that exploiting is quickly dying? Not sure about that statement but I just came back from a multiple year hiatus

2 Likes
#64

it’s slowly returning due to a dedicated team of devs and the fact Hyperion seems to have ran out of detections

#65

Why is this thread still ongoing anyway? These client-sided anti-cheats can be pretty performance expensive, and will still get bypassed sooner or later. All it takes is for someone to bypass it, post the source code online on a website or a platform where skids regularly visit, and your game is doomed.

1 Like
#66

That could work if you have no sense of security whatsoever. If there’s a way to bypass, there’s a way to detect.