![The God Eye (The Ultimate AntiCheat) [SKRIPT]](https://www.spigotmc.org/data/resource_icons/30/30770.jpg?1477187714){kind=icon}
The God Eye: A new, efficient, and accurate way to catch those pesky hackers
Version 6.7
![[IMG]](//proxy.spigotmc.org/ebd6ca6ff3012d9209990531e42eb2dcebb265b7?url=http%3A%2F%2Fsites.ucomc.net%2Fsite%2FTGE%2Ffiles%2Fimg%2FTGE-Logo.png)
NEWLY UPDATED!!!Version 6.7
![[IMG]](http://proxy.spigotmc.org/ebd6ca6ff3012d9209990531e42eb2dcebb265b7?url=http%3A%2F%2Fsites.ucomc.net%2Fsite%2FTGE%2Ffiles%2Fimg%2FTGE-Logo.png){kind=logo}
2000+ Downloads!
What is it?
The God Eye, developed jointly by UGCGames (ilyak on SpigotMC) and UniverseCraft Development Studios, is a fully-tested, feature-rich AntiCheat solution for all servers.
Covering a wide range of hacks - from Auto Clicker to Survival Fly - TGE sees all.
Commands
/tge - main command for TGE.
/ban <player> [reason] - bans the specified player, optionally for the specified reason.
/tempban <player> [reason] [timespan] - temporarily bans the specified player. If no other arguments are supplied or the timespan left blank, the player is permanently banned. Timespan argument follows normal Skript timespan format. Example: /tempban ThatOneHacker Hacking 1 day bans player ThatOneHacker due to Hacking for a timespan of 1 day.
/pardon <player> (/unban <player>) - unbans the specified player.
/view-ban <id> - views information about the specified Ban ID.
Covered Hacks
An * listed next to a hack indicates that it is punished for. All other hacks listed are detected but fall under a broader category; that is, one of the *-indicated ones.
A - listed next to a hack indicates that it is supported but disabled by default because it contains some false positives or does not always work as expected.
- Kill Aura*
- Click Aura
- Multi Aura
- Trigger Bot
- Auto Clicker
- Survival Fly*
- Flight (alias for Survival Fly)
- Jetpack
- High Jump (when very obvious)
- Speed Walk*
- Jesus*
- Fast Ladder*
- Phase*-
- Sneak*-
- Regen*
- Fast Consume*
- Speed Mine*
- Fast Place*
- Blink*
- Anti-Knockback*
- VClip (NEW)
Place the files in 'TGE.zip/TGE' into your 'plugins/Skript/scripts' folder and type /sk reload TGE(.sk) to install TGE. A second reload MAY be required for Skript options to registered.
If you would like to use TGE's ban commands (recommended especially for temporary bans), then you must also use /sk reload TGE-BanCmds(.sk).
Please only edit the config.yml under the 'TGE' folder. Most other functionality is best left untouched.
Configuration values are explained in detail in TGE's config.yml.
*** All config options (except for prefixes, appeal text, etc.) are set at their optimal values as tested by our testers and developers. Modify them and/or the native code of TGE at your own risk.
Why TGE over the billion other available AntiCheats?
As a server owner or developer, you are reading this right now because you are unsatisfied with your current AntiCheat or the solutions out there.
Very rarely does one stumble upon a truly balanced AntiCheat solution. NoCheatPlus? Over-sensitive and takes a genius to configure. AntiCheat? Under-sensitive. GWEN? Besides being publicly unavailable, it/she is both over- and under-sensitive. AAC? It costs money, and the entire thing is based around packets! It's horribly inaccessible and unintuitive. People literally make money off of selling halfway-decent configurations for it. Most Anti-Cheats? Untested, unbalanced.
Conclusion: Hacking solutions are hard to find. It seems as if nothing actually works! As a server developer or owner, you know that all those 'magic' solutions to hackers that you see out there just don't work.
But now it's changed. With The God Eye, you have a large range of fully tested hack blockers. To ensure maximum efficiency, simplicity, and accuracy, their balance and checking techniques are set and are not directly configurable - you want TGE to do its job right, don't you? Yet the entire interface is 100% customizable.
The God Eye is the solution you have been waiting for and the solution that the Minecrafting world needs.
So why wait? Try TGE now.
Coming Up...
We're not done! TGE is constantly being revised and expanded, and here are a few features and blockers we're planning to add in:
- More blockers:
- Glide
- Phase bugfixing
- Sneak bugfixing
- More info for /tge stats
- Performance improvements (some servers may experience occasional lag, although we have already greatly improved this issue and it remains our #1 priority as long as the problem persists in any amount.)
- Skript
- SkRayFall
- SkUtilities
- WildSkript
- SkQuery
- HolographicDisplays
- Umbaska (NEW)
- There may be other add-ons that enhance the functionality of some parts of TGE, but TGE does not rely upon them for any of its functionality. If TGE does not load error-free on the second reload, contact us and we will double-check to make sure that this list is accurate and our script does not contain any new bugs.
/tge, /ban, /tempban, /pardon: TGE.admin
/view-ban: TGE.mod
Ban IDs, Explained
When a player is banned or placed on the Ban Wave for TGE, an ID is associated with their ban. Moderators can view information on this ban using /view-ban <id>. Admins can also use /tge id <id>, but we thought that it would be nice to give Moderators / Appeal Managers a separate command without letting them use all of TGE.
Currently, the following information is displayed:
- The user who was banned
- Reason for the Ban (e.g. Survival Fly, KillAura, Phase)
- Time the player was detected (NOT necessarily when they were banned)
- Who banned the player (usually TGE, but a player could have done /tge punish <player> <reason> and, in this case, that player would show up.)
- The location of the player when they were detected
- Data associated with the ban (if any)
Spoiler: Ban Data Tutorial
Ban Data
TGE will save basic data about a ban and why the offending player was punished. Data for various violations is explained below. If no data is shown for a violation, this is because there is none; it was too simple of a check.
The term "false-positive," as used here, simply means detecting something that wasn't there, i.e. thinking that a player was hacking when they were actually not. Thus, if there is a higher likelihood of a false-positive based on a certain data value, then that player should be considered for unbanning over a player's data value with a lower likelihood of a false-positive.
Speed Walk
y1: The player's initial y-coordinate
y2: The player's y-coordinate after 0.5 seconds
dist: The distance between the player's initial location and location after 0.5 seconds
A lower distance is more likely to have been a false-positive.
Speed Mine
diff: The difference in time between the player's second-to-last mining time and last mining time.
A higher value is more likely to have been a false-positive.
Fast Place
diff: The difference in time between the player's second-to-last place time and last place time.
A higher value is more likely to have been a false-positive.
Fast Ladder
y1: The player's initial y-coordinate
y2: The player's y-coordinate after 1 second
dist: The distance between the player's initial location and the player's location after 1 second
A higher distance value is more likely to have been a false-positive.
Survival Fly 1
chk: A value of "pr" means that this check (primary check) detected the hack. This check detects flight in motion; if a player was flying around, this is most likely the check that detected it.
al: The player's height above the closest non-air block directly below them.
al2: The player's height above the closest non-air block directly below them after 1 second
edge: Basically, a count of how many blocks were near the player that could not potentially cause a false-positive. A number greater than 3 means that it is extremely unlikely that a false-positive occurred; a number less than 3 means that it is extremely likely that a false-positive occurred. The greater the number, the less likely it is that they were unfairly banned.
A lower value for edge is more likely to be a false-positive. A higher value for al or al2 is also likely to be a false-positive. If those two values are close together, then it is generally more likely to be a false-positive.
The difference betwen al and al2 is the change in the player's height in 1 second.
Survival Fly 2
chk: A value of "sc" means that this check (secondary check) detected the hack. This check detects stationary flight; if a player is standing still above ground, this is most likely the check that will detect it.
alt: The player's height above the closest non-air block directly below them.
y1: The player's initial y-coordinate.
y2: The player's y-coordinate after 0.5 seconds
The higher the value for alt, the more likely there is that a false-positive has occurred. The same is true for y1 and y2.
edge (NEW): The amount of non-air blocks the player was near to. A higher value indicates a higher likelihood of a false positive; the player could have been standing on the edge of a cliff, for example. Patch 6.5.1 reduced the likelihood of such a false-positive detection, however.
Kill Aura 1
chk: A value or "pr" means that this check (primary check) detected the hack.
diff: Time elapsed between player's attacks. A lower value means there is a higher likelihood of Kill Aura but does not determine it; nor does a higher value mean there is less likelihood (to a point; anything above 1 second is probably a false-positive.)
cps: Clicks Per Second.
A player punished in this check is more likely to have been mistakenly detected than in Kill Aura 2 - however, this check is important for detecting slower Kill Auras, such as KillAuraLegit on Wurst.
A higher value for diff indicates a stronger likelihood of a false-positive.
A lower value for cps (0 - 3) indicates a stronger likelihood of a false-positive.
Kill Aura 2
chk: A value of "sc" means that this check (secondary check) detected the hack.
diff: Time elapsed between player's attacks.
cps: Clicks Per Second.
A higher value for diff indicates a stronger likelihood of a false-positive.
A lower value for cps (0 - 3) indicates a stronger likelihood of a false-positive.
Regen / FastEat 1
diff-health: The difference between the player's last health and new health (last health is the health recorded in the last detection.)
diff-time: The difference in time between the detections.
A higher value for either indicates a stronger likelihood of a false-positive.
Regen / FastEat 2
diff: The difference in time between the detections.
A higher value for diff indicates a stronger likelihood of a false-positive.
Blink
Very prone to false-positives!
dist: Distance between the player's old location and new location.
A lower value for dist indicates a stronger likelihood of a false-positive.
TGE will save basic data about a ban and why the offending player was punished. Data for various violations is explained below. If no data is shown for a violation, this is because there is none; it was too simple of a check.
The term "false-positive," as used here, simply means detecting something that wasn't there, i.e. thinking that a player was hacking when they were actually not. Thus, if there is a higher likelihood of a false-positive based on a certain data value, then that player should be considered for unbanning over a player's data value with a lower likelihood of a false-positive.
Speed Walk
y1: The player's initial y-coordinate
y2: The player's y-coordinate after 0.5 seconds
dist: The distance between the player's initial location and location after 0.5 seconds
A lower distance is more likely to have been a false-positive.
Speed Mine
diff: The difference in time between the player's second-to-last mining time and last mining time.
A higher value is more likely to have been a false-positive.
Fast Place
diff: The difference in time between the player's second-to-last place time and last place time.
A higher value is more likely to have been a false-positive.
Fast Ladder
y1: The player's initial y-coordinate
y2: The player's y-coordinate after 1 second
dist: The distance between the player's initial location and the player's location after 1 second
A higher distance value is more likely to have been a false-positive.
Survival Fly 1
chk: A value of "pr" means that this check (primary check) detected the hack. This check detects flight in motion; if a player was flying around, this is most likely the check that detected it.
al: The player's height above the closest non-air block directly below them.
al2: The player's height above the closest non-air block directly below them after 1 second
edge: Basically, a count of how many blocks were near the player that could not potentially cause a false-positive. A number greater than 3 means that it is extremely unlikely that a false-positive occurred; a number less than 3 means that it is extremely likely that a false-positive occurred. The greater the number, the less likely it is that they were unfairly banned.
A lower value for edge is more likely to be a false-positive. A higher value for al or al2 is also likely to be a false-positive. If those two values are close together, then it is generally more likely to be a false-positive.
The difference betwen al and al2 is the change in the player's height in 1 second.
Survival Fly 2
chk: A value of "sc" means that this check (secondary check) detected the hack. This check detects stationary flight; if a player is standing still above ground, this is most likely the check that will detect it.
alt: The player's height above the closest non-air block directly below them.
y1: The player's initial y-coordinate.
y2: The player's y-coordinate after 0.5 seconds
The higher the value for alt, the more likely there is that a false-positive has occurred. The same is true for y1 and y2.
edge (NEW): The amount of non-air blocks the player was near to. A higher value indicates a higher likelihood of a false positive; the player could have been standing on the edge of a cliff, for example. Patch 6.5.1 reduced the likelihood of such a false-positive detection, however.
Kill Aura 1
chk: A value or "pr" means that this check (primary check) detected the hack.
diff: Time elapsed between player's attacks. A lower value means there is a higher likelihood of Kill Aura but does not determine it; nor does a higher value mean there is less likelihood (to a point; anything above 1 second is probably a false-positive.)
cps: Clicks Per Second.
A player punished in this check is more likely to have been mistakenly detected than in Kill Aura 2 - however, this check is important for detecting slower Kill Auras, such as KillAuraLegit on Wurst.
A higher value for diff indicates a stronger likelihood of a false-positive.
A lower value for cps (0 - 3) indicates a stronger likelihood of a false-positive.
Kill Aura 2
chk: A value of "sc" means that this check (secondary check) detected the hack.
diff: Time elapsed between player's attacks.
cps: Clicks Per Second.
A higher value for diff indicates a stronger likelihood of a false-positive.
A lower value for cps (0 - 3) indicates a stronger likelihood of a false-positive.
Regen / FastEat 1
diff-health: The difference between the player's last health and new health (last health is the health recorded in the last detection.)
diff-time: The difference in time between the detections.
A higher value for either indicates a stronger likelihood of a false-positive.
Regen / FastEat 2
diff: The difference in time between the detections.
A higher value for diff indicates a stronger likelihood of a false-positive.
Blink
Very prone to false-positives!
dist: Distance between the player's old location and new location.
A lower value for dist indicates a stronger likelihood of a false-positive.
Questions? Comments? (SECTION UPDATED)
For any and all questions or bug reports that do not go on this page's discussion, we suggest you submit a support ticket on our development team's website, sites.ucomc.net/contact.php (our other major project is a website builder).
Enjoy TGE!
Quick facts
- Edition: Minecraft Java
- File type: .jar
- Minecraft versions listed: 1.8, 1.9, 1.10
- How to install: Install the matching mod loader (Forge, Fabric or NeoForge) for your Minecraft version. → Download the .jar. → Put it in the .minecraft/mods folder and launch that loader profile.
- Where to get it: Opens on Spigot — not every file is mirrored on our own servers.
Install steps are the general flow for this file type — How to install Minecraft Java mods & modpacks walks through it step by step.
The God Eye (The Ultimate AntiCheat) [SKRIPT] is a free Minecraft Java mod. Compatible with Minecraft 1.8, 1.9, 1.10, 1.11. Downloaded 7,527 times (via Spigot). Download it and open it directly in the game.