[Minecraft Anticheat] TigerHack

Status
This thread has been locked.

SmakYop

Feedback score
0
Posts
23
Reactions
1
Resources
0
TIGERHACK ANTICHEAT
The plugin is not longer in sale!
Presentation

TigerHack is an anticheat based on many algorithms to perform the best checks on a player and detect if any hack/cheat is activated and used.

Detected hacks
  • KillAura (Forcefield : Aimbot & Reach)
  • Reach (3.1 min - 3.2 max blocks detected)
  • Aimbot
  • Fly
  • SpeedHack
  • NoFall
In the future i'm planning to do a bunch of things like :
  • Other detections
    • AutoPotions
    • AutoSoup
    • MorePackets
    • Regen
    • FastEat
    • Sneak
    • AntiVelocity
    • FastBow
Commands & Permissions

  • There's no command for the moment, but they will come!
  • Permissions :
    • tigerhack.* Give an access to all the permissions of the plugin.
    • tigerhack.report.view See the reports (soon)
    • tigerhack.alert.view See the alerts
    • tigerhack.command Use the tigerhack's commands (soon)
Database

TigerHack offers the ability to use a mysql database to store alerts and bans.
All of the access to it are configurable in the config.yml file!


Configuration

Here, you have all the configuration of TigerHack :

Code:
##############################
#                 TigerHack | Anti-Cheat               #
##############################

General:
  Prefix: '&7[&cTigerHack&7]'
  PrefixStaff: '&e(&c&lTigerLog&e)'
  ReportPrefix: '&7[&cReport&7]'

# Database configuration
# You can activate or desactivate the database.
# Recommanded if you are 2 or more servers and if you using Bungeecord
Database:
  enabled: false
  user: user
  url: jdbc:mysql://localhost/database_name
  password: password


# You can enable or disable the AutoBan.
AutoBan: true
OpPlayerCanBeBanned: false

# Commands configuration
CommandForReport: true

# Send an alert when a player is suspected
AlertStaff: true


# Firework configuration
# If it's enabled, a firework will spawn at the location of the player when
# he gets banned
Firework:
  enabled: true

# Broadcast configuration
# If it's enabled, a broadcast will be sended when a player is banned
# %reason% > reason | %player% > banned player
BroadcastOnBan:
  enabled: true
  message: '&7[&cTigerHack&7] &e%player% &7has been banned for: &c%reason%'

Message:
  alertMessage: '%prefixstaff% &7%player% &eattempted: &6%cheatreason% &7(&c%playerping% &7ms | &c%violation% &7VL)'
  reportMessage: '%prefixreport% &c%player% &7was report for: &3%cheatreason%'
  noPermission: '&4No permission.'


# Report Configuration
Report:
  CommandHelp: '&a/report <player> &8- &eReport a Player for cheating'
  CantReport: '%prefixreport% &cYou can not report this player!'
  MessageCancelReport: '%prefixreport% &cYou have cancelled the report!'
  ReportPlayer: '%prefixreport% &7You have report: &3%playerreport%'


# Bungeecord support is coming soon..
Bungeecord:
  enabled: false


# ---  Cheats Configuration  --- #
# Forcefield is Reach & Aimbot

CheatsConfiguration:
  Forcefield:
      enabled: true
      autoban: true
      alert: true
  Fly:
      enabled: true
      autoban: true
      alert: true
  Sneak:
      enabled: true
      autoban: true
      alert: true
  SpeedHack:
      enabled: true
      autoban: true
      alert: true
  NoFall:
      enabled: true
      autoban: true
      alert: true
      alertForBan:
  FastBow:
      enabled: true
      autoban: true
      alert: true
      alertForBan:


debug: false


##############################
#                 TigerHack | Anti-Cheat               #
##############################

Installation (You need Java 8 and ProtocolLib)
  1. Download ProtocolLib
  2. Place the "TigerHack.jar" on your plugins folder
  3. Launch the server
  4. You're good to go!


Thanks all.
 
Last edited:

MrIbrahimTv

Deactivated
Feedback score
0
Posts
11
Reactions
6
Resources
0
Vouch! Good plugin tested with Vape V2 Reach at 3.2 min and 3.3 max 3.1 min 3.2 max etc and the AC log me for Reach and bypassed with 6 Speed Mode but the devloper say me he gonna fix this in the v1 :^)
 

SmakYop

Feedback score
0
Posts
23
Reactions
1
Resources
0
Location damagerloc = damager.getLocation().clone();
Location defenderloc = damager.getLocation().clone();

double distance = defenderloc.distance(defenderloc);

if (distance > 3.2)
{
addFlag(player, this, "3.2 reach mlg detection");
}
Just : "Funny :D"
My reach detection has been tested by 2 peoples and these 2 peoples said that it's a good detection so please, go away ;)
 
Last edited:

Clyde

Premium
Feedback score
44
Posts
1,577
Reactions
1,220
Resources
0
Ok first of all, you cant patch 3.1 - 3.2 - 3.3 - 3.4 reach WITHOUT false-flags and not having any sort of vector mapping. Just doing

Location damagerloc = damager.getLocation().clone();
Location defenderloc = damager.getLocation().clone();

double distance = defenderloc.distance(defenderloc);

if (distance > 3.2)
{
addFlag(player, this, "3.2 reach mlg detection");
}

No, you cant make a good reach detection like that, as you simply cant code a perfect reach check in 10 mins. I have been coding a reach check for 3.1 - 3.2 for ghost-clients about 3 months now, and In-total, half of this time is research to find the best values for KB-Logging and Distance Logging. Now for kids that will react funny saying "SUCKER!? YOUR REACH CHECK IS JUST WHAT YOU TYPED UP THERE?!?!?!?!?!??! NOOB KYS", just dont, I wont give a damn. Now, what I am trying to say is that you need a lot of time to make a reach-check to ban efficiently.
I made one in 30 minutes and its quite accurate. Its quite easy really.

Edit: if you wanna know (leontss1), pm me
 
Status
This thread has been locked.
Top