konsolas / AAC-Issues

AAC Issue Tracker.
32 stars 15 forks source link

Nuker & Fastbreak Issues #1209

Closed ItsTigerss closed 6 years ago

ItsTigerss commented 6 years ago

Issue description

Core information

Server version: 1.8-1.12

AAC version: 3.3.10

ProtocolLib version: 4.3.0

Plugin list: Will give if needed.

Special environment information

ViaVersion version: Yes

ProtocolSupport version: N/A

ViaBackwards version: 2.3.1

BungeeCord plugins: N/A

Configuration

Fastbreak: cancel_break: false

ItsTigerss commented 6 years ago

THIS IS FOR CELEBRIMBORS CONFIG

Janmm14 commented 6 years ago

High efficiency tools are exempted from fastbreak due to their insane speed causing false positives. You need to replace "will ban / kick you" with vebose output.

Please do not combine completely different issues in one.

The question here is not: Will it alert me, will it kick or ban me? The question here is: Does verbose say something?

ItsTigerss commented 6 years ago

I don't get verbose output. I always have it enabled when I test.

Janmm14 commented 6 years ago

For the step cheat bypass, a debug log is likely the best option to fix it.

For Nuker/Fastbreak non-alerts with high efficiency tools: konsolas will not change how it works, you'll have to live with how it currently works or use fastbreak check of another anticheat like ncp.

ItsTigerss commented 6 years ago

Well it doesn't even alert and it false bans. So you keep bugged stuff in your anticheat?

Janmm14 commented 6 years ago

there will always be a verbose output before any threshold command is executed

make sure you have the permission, turned verbose on in the config and not disabled via /aacverbose or /aacadmin

Additionally it is not my anticheat. What stuff do you you mean with it now?

As I said its not good to report different issues in the same issue.

ItsTigerss commented 6 years ago

Nuker and Fast Break, they are almost the same.

CeIebrimbor commented 6 years ago

@ItsTigerss I have cleaned up the original report to solo out nuker/fastbreak. Please provide a video showing the blatant bypasses and any other changes you made to Nuker or Fastbreak that are not consistent with AAC’s Default config, except thresholds(those are irrelevant).

Please open a separate report for your step bypasses and do the same there. Since you chose to not teleport for Fly, I guarantee you will have Step bypasses. When you elected to use my “Ghost” setup, you blew right past the warning that said:

Ghost Config Warnings! 1. These configs are not designed to block or punish as soon as reasonably possible. If you want an early detection that blocks the maximum number of hacks, use the <#optimized_configs> and stop reading this channel.

2. This config is an extremely dormant setup for owners that do not want a harsh punishment system, but instead want an advanced notify setup to give staff information about potential hackers. This setup will only kick for a severe levels of detection.

In other words, bypasses relating to “Not detected fast enough” will be ignored. If you get zero detection at all or bypasses on the default config, that would be worthy of a report.