Disable all client-sided anti-cheats by default, even on older loaders

[moo1210]

Wasn't it discussed that all these detections on the client would either be off by default or removed earlier this year? I don't think any of these even actively flag genuine exploiters now that Byfron is deployed on Windows clients, it looks more like they just keep falsely flagging players after Roblox updates something.

Some of this was done (all of the toggleable client-sided anti-cheats in settings were set to false by default, however, there are still fairly useless client-sided ones that run under settings.Detection, which is still true by default), but in practice applies to virtually no games, since they all use outdated loaders, and most people don't actively merge their settings file. Realistically speaking, the client-side anti-cheats need a new setting to re-enable them, in order to disable them on games without the newest config file, which is kind of a flaw in how the settings file was created.

More recently, #1203, #1133, #1144 have been filed just fixing issues that they falsely flag users after Roblox updates things, which is to be expected since we're searching thru internal Roblox-type things, that aren't documented and can change at any time.

(CC: @Sceleratis @coasterteam)

[Sceleratis]

Agreed tbh

[wilsontulus]

Tbh it's not really caused by Byfron. Atleast for me, most of the skids (which actually counts over 80% of the exploiters in my games) are still detected even by Adonis alone, let alone my own anticheat that's more optimized for the type of the game (e.g. obbies, vehicles, etc). All metamethod hooks are still detected properly, and most non-chad exploits that prints their credits in the console, or some scripts erroring out while trying to call some unsupported function in non-chad executors, are still detected like normal.

For example, this is one of my PR to address a false positive caused by a Roblox update: #1203

I still partially agree for the option tbh, it looks like some people using Adonis don't really know how to tune & debug Adonis, let alone creating their own anticheats or even scripting all alone.
Plus more skilled exploiters are offering their own scripts to those skids even though there's still a chance that a skid will, unknowingly use a non-chad executor and the script spits out an error with blacklisted words in it.

[moo1210]

I still partially agree for the option tbh, it looks like some people using Adonis don't really know how to tune & debug Adonis, let alone creating their own anticheats or even scripting all alone.

This is the main problem, Adonis, never should've been doing anything beyond protecting itself as an anti-cheat. That was never its intended purpose or job. It's an admin system, not an anti-cheat system. People don't want to configure a built-in anti-cheat perfectly to get their admin system to work without kicking half of their players. That should be a separate project outside of Adonis, but realistically, it still would still have the same false-detection problems, and would still be a massive hack, Adonis or not.

Also, the way most of these "anti-cheats" built into Adonis is inherently flawed. Most of them are just depending on undocumented Roblox functionality that can change at any time, or depend on even weirder stuff, that the developer can affect, like prints to the console log. These issues have happened, time and time again, ever since the introduction of most of these features into Adonis. Wherever it's from a developer prints something that we recently "blacklisted", Roblox updates Lua VM behavior, or updates how an Instance reacts or responds, it ends up kicking people from games.

Tbh it's not really caused by Byfron. At least for me, most of the skids (which actually counts over 80% of the exploiters in my games) are still detected even by Adonis alone

So I presume all your exploiters all on UWP or Android then? Byfron is planned to come to both, with UWP coming first (as well as it moving to 64-bit). So, it's only a matter of time, before those are also patched out (somewhat) properly, without hacky client-sided Lua scripts.

[ccuser44]

I don't think any of these even actively flag genuine exploiters now that Byfron is deployed on Windows clients, it looks more like they just keep falsely flagging players after Roblox updates something.

Thats just not true. Byfron cannot cause Adonis to be detected.

What is happening is that Byfron fixed most professional exploits so exploiters switched to half baked broken exploits (like Celery) which use UWP or mobile version.
These exploits do not have vulnerability fixes which makes them detectable by Adonis, that is the source of detections, not false flags.
This can be confirmed by increased posts on exploiter forums requesting for "Adonis bypasses."

---

This is the main problem, Adonis, never should've been doing anything beyond protecting itself as an anti-cheat. That was never its intended purpose or job. It's an admin system, not an anti-cheat system. People don't want to configure a built-in anti-cheat perfectly to get their admin system to work without kicking half of their players.

Sceleratis literally was part of the Roblox anti cheat consortium and Epix Incorporated had a exploiter banlist in 2016. Epix Inc used to even advertise Adonis as an anti cheat.

Again because there is an anti cheat people expect it to be there. I would say it's a net positive if a lot of games are given a blanket protection for them not having to do any effort to configure it. Less exploiters in Roblox is a net positive.

[moo1210]

literally was part of the Roblox anti cheat consortium and Epix Incorporated had a exploiter banlist in 2016. Epix Inc used to even advertise Adonis as an anti cheat.

Yeah, back in 2016…. A a lot a changed both in Adonis’s anti-cheat and Roblox, from filteringenabled, to network ownership, to Byfron.

[moo1210]

(Also didn’t mean to close that was a mistap on mobile, although there is a open PR)

[alau740]

do we even need an anti exploit in adonis anymore

[Dimenpsyonal]

Wasn't it discussed that all these detections on the client would either be off by default or removed earlier this year?
@moo1210 yes it was. Unfortunately lazy maintainers

[alau740]

Wasn't it discussed that all these detections on the client would either be off by default or removed earlier this year?
yes it was. Unfortunately lazy maintainers

@LiveFireExercise i remember saying something on the discord like a year ago saying we should disable anti by default

[Dimenpsyonal]

@LiveFireExercise i remember saying something on the discord like a year ago saying we should disable anti by default

@alau740 yea and a year later nothing has happened

[ccuser44]

literally was part of the Roblox anti cheat consortium and Epix Incorporated had a exploiter banlist in 2016. Epix Inc used to even advertise Adonis as an anti cheat.

Yeah, back in 2916…. A a lot a changed both in Adonis’s anti-cheat and Roblox, from filteringenabled, to network ownership, to Byfron.

But Byfron doesn't apply for UWP. Which most exploiters now use.

Exploits developed for UWP are bad and that makes them detectable for Adonis. The detections you are seeing are valid detections from bad quality exploits like celery (expect the ones relating to new Roblox changes)

In fact because of this the AC has become more relevant not less.

Also I don't see why the detections should be disabled on old loaders? If people have issues with them then they can just disable them manually.