Antycheat bez blokady cheatów

Pytania i problemy
minecraft, zarządzanie
Matess219
Matess219

Posiadam w tym momencie na swoim serwerze plugin GrimAC, Ale chciałbym zmienić by plugin nie blokował cheatów ale je pokazywał, Jeżeli będzie to potrzebne mogę zmienić plugin na antycheata, Proszę o szybką odpowiedź :D

matrixx
matrixx

Nie rozumiem do końca czy o to chodzi ale jeśli tak, to zmień w konfiguracji client-brand na to:

client-brand:
  # This means it won't broadcast their brand to operators if the brand matches the following regexes
  ignored-clients:
    - "^vanilla$"
Matess219
Matess219

Chodzi mi o to że ktoś normalnie może używać sobie fly czy tam killaury, wyszystkiego, ale ma się wyświetlać na chacie.

Matess219
Matess219

Wyświetlać na chacie chodzi o oczywiście że ktoś będzie używał cheatów i go będzie wyświetlało

matrixx
matrixx

Nie wiem do końca czy to będzie działać, ale spróbuj zmienić w config.yml jak masz np. Simulation i setback-decay-multiplier na -1:

  # How much should we multiply total advantage by when the player is legit
  # This is what the default config looks like (x axis = seconds, y axis = 1/1000 block): https://www.desmos.com/calculator/d4ufgxrxer
  setback-decay-multiplier: -1

Wtedy raczej Grim powinien wyłączyć tą funkcję i nie powinno cofać, ale pamiętaj, żeby ustawić te -1 też w innych kategoriach konfiguracji - w tych, których chcesz mieć to wyłączone. Najczęściej ustawiaj te -1 przy funkcjach gdzie mają w sobie te setback.

Matess219
Matess219

a można by żebym poprostu dostał konfig? sory ale trochę nie jestem w temacie antycheatów

Tutaj mój konfig:

[details="Config (rozwiń)"]

# GrimAC main configuration
# Source code: https://github.com/MWHunter/Grim
# Copyright 2022 DefineOutside and contributors, Licensed under GPLv3.
# Modified binaries, or plugins with copied grim code, must be private,
# or with full source code available to buyers at no additional cost.
 
alerts:
  # In addition to broadcasting alerts to players, should they also be sent to the console?
  print-to-console: true
  # This controls whether/how alerts are shared between servers connected to your proxy.
  # You must have 'bungee-plugin-message-channel' enabled in your Velocity's configuration if Velocity is in use.
  proxy:
    # Should alerts be sent to other servers connected to your proxy?
    send: false
    # Should the alerts received from other servers be announced to this server?
    receive: false
 
verbose:
  print-to-console: false
 
client-brand:
  # This means it won't broadcast their brand to operators if the brand matches the following regexes
  ignored-clients:
    - "^vanilla$"
    - "^lunarclient:[a-z0-9]{7}"
 
spectators:
  # Hide all spectators with the grim.spectator permission regardless if they are actually actively spectating
  hide-regardless: false
  # Will make spectators hidden only in these worlds, keep blank to allow all worlds
  allowed-worlds:
    - ""
 
# How long should players have until we kick them for timing out? Default = 60 seconds
max-transaction-time: 60
 
Simulation:
  # How much should we multiply total advantage by when the player is legit
  # This is what the default config looks like (x axis = seconds, y axis = 1/1000 block): https://www.desmos.com/calculator/d4ufgxrxer
  setback-decay-multiplier: -1
  # How large of an offset from the player's movement should we create a violation for?
  # Measured in blocks from the possible movement
  # We account for Optifine by switching trig tables but dropping this to 0.001 will reduce FastMath
  # flagging the anticheat if this compensation doesn't work...
  threshold: 0.001
  # How large of a violation in a tick before the player gets immediately setback?
  # -1 to disable
  immediate-setback-threshold: -1
  # How large of an advantage over all ticks before we start to setback?
  # -1 to disable
  max-advantage: -1
  # After 50 seconds with default config, the player will go from 4 blocks -> 1 block of advantage
  # This is to stop the player from gathering too many violations and never being able to clear them all
  # Default advantage ceiling (x axis = seconds, y axis = 1/1000 block): http s://www.desmos.com/calculator/4lovswdarj
  max-ceiling: 4
 
# Checks to see if a player entered a block during a movement
Phase:
  setbackvl: -1 # Glitching into blocks can allow wall climbing, plus this check is relatively stable
  decay: 0.005
 
AirLiquidPlace:
  cancelvl: 0
 
FabricatedPlace:
  cancelvl: 5
 
FarPlace:
  cancelvl: 5
 
PositionPlace:
  cancelvl: 5
 
RotationPlace:
  cancelvl: 5
 
# Prediction-based no slow check
# Grim accounts for buggy netcode here... hard to false even when spamming right click and offhand button
# Much more stable than other anticheats, but please report any falses... I have fixed a ton of netcode issues here.
NoSlow:
  # How much of an offset is "cheating"
  # By default this is lower than other offs
  # Flags by 0.03-0.2 consistently with NoSlow on
  threshold: 0.001
  # Setback fast on the first item to remove any advantage NoSlow gives
  setbackvl: -1
  # Decay's when the player uses an item AND is slowed by it
  decay: 0.05
 
Knockback:
  # How much of an offset is "cheating"
  # By default this is 1e-5, which is safe and sane
  # Measured in blocks from the correct movement
  threshold: 0.001
  setbackvl: -1
 
Explosion:
  threshold: 0.001
  setbackvl: -1
 
TimerA:
  setbackvl: -1
  # Milliseconds that the player can accumulate for later use when they fall behind
  # Could potentially allow 1.8 fast use/fast heal/fast bow bypasses if set too high, 120 ms seems like a good balance
  drift: 120
 
NegativeTimer:
  # Number of milliseconds lost while moving before we should start flagging
  drift: 1200
 
# Same check method as TimerA, but for vehicles
TimerVehicle:
  # Target 1.005 timer
  setbackvl: -1
 
EntityControl:
  setbackvl: -1
 
Reach:
  # How much should we expand hitboxes by? 0.0005 should detect 3.0005+ reach
  #
  # There is 0.03 forced expansion with 1.9-1.18.1 (not 1.18.2), or some client/server combinations due to
  # protocol changes and limitations. This check is most powerful with 1.7/1.8 clients on 1.8 servers.
  threshold: 0.0005
  # Should we cancel hits that we know are impossible?
  # 3.00-3.03 hits may go through but still be flagged, due to packet order limitations
  block-impossible-hits: true
  # This will send an additional packet at the end of every tick to increase the likelihood of catching cheats
  # This injects into server's connection list to send a final packet just before the server flushes
  # Enabling this will increase bandwidth usage for all players
  # This will not decrease overall server performance
  # Enabling this will catch more cheaters.
  # Leaving this disabled will still catch cheaters and will not cause false positives
  # Unless you are a 1.8 PvP focused server, this additional packet is not recommended
  enable-post-packet: false
 
# Enable logging plugins who have injected into netty on join to debug compatibility issues
debug-pipeline-on-join: false
 
# Enables experimental checks
experimental-checks: false
 
# Grim sometimes cancels illegal packets such as with timer, after X packets in a second cancelled, when should
# we simply kick the player? This is required as some packet limiters don't count packets cancelled by grim.
packet-spam-threshold: 100
 
config-version: 8

[/details]

Matess219
Matess219

zrobiłem copy paste jak coś /|
|

system
system

Ten temat został automatycznie zamknięty 32 dni po ostatnim wpisie. Tworzenie nowych odpowiedzi nie jest już możliwe.