kukubaczek

CONFIG

Feb 13th, 2015
281
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Lua 12.65 KB | None | 0 0
  1. #Welcome to the configuration! It can be hard to configure the plugin correctly, but once you do, hackers will feel the heat.
  2. Forcefield:
  3.   MobInFront:
  4.     #Do you want to enable the mob in front?
  5.     #This will create a cow between the player and the person who he is attacking.
  6.     #If the player still hits the person (with the cow in the way), he is hacking.
  7.     Enable: true
  8.     #Do you want a cow to be riding the already-spawned cow?
  9.     #This is just there to stop clients hitting above the cow.
  10.     #Disable this if you are seeing flickering cows during PVP.
  11.     MobOnTop: true
  12.     #Every time a person hits the player (when the cow is spawned), the number goes up by 1.
  13.     #Every time a person hits the cow (when the cow is spawned), the number goes down by your SafeHitDecrease value in the config.
  14.     #If the number hits this value, the person is detected for hacking (and MobBypassCommand is executed).
  15.     Threshhold: 10
  16.     #As described in the above configuration, what do you want the number to go down to?
  17.     SafeHitDecrease: 2.5
  18.     #How long (in ticks) do you want the cow spawned? 20 ticks equal one second.
  19.     TimeSpawned: 15
  20.     #The nearer the player is to the player he is hitting, the more likely false-positives are to occur.
  21.     #The plugin will not do the MobInFront check if the player is closer than MinDistance blocks to the other player.
  22.     #You can decrease it if you are having issues with not detecting. A minimum value of 2 may be acceptable.
  23.     MinDistance: 2.5
  24.     #What commmands do you want to execute when the person is detected bypassing the cow?
  25.     MobBypassCommand: kick %PLAYER% Forcefield is not allowed!#broadcast %PLAYER% was kicked for hacking! (MobBypass)
  26.   #What commands do you want to execute when the person is detected for forcefield (using the HeadPlayer or normal checks)?
  27.   ForcefieldCommand: kick %PLAYER% Forcefield is not allowed!#broadcast %PLAYER% was kicked for hacking! (Normal)
  28.   #Do you want to check for forcefield if the person is PVPing a mob?
  29.   CheckWhileFightingMobs: true
  30.   #Do you want to set the player above your head that is spawned to be invisible?
  31.   #This is recommended left as false! Some hacked clients ignore invisible players!
  32.   HeadPlayerInvisible: false
  33.   #Enabling this will tell the player that the HeadPlayer is riding experience orbs!
  34.   #This means the HeadPlayer will move with your client and will always be in a set position above it.
  35.   #Disable if you do not like seeing irritating XP orbs in your vision.
  36.   OrbBug: false
  37.   #The amount of times you need to hit the HeadPlayer before you are detected.
  38.   #Rules as to how the number goes up/down are the same ones explained on the MobInFront threshhold value.
  39.   HeadValue: 1
  40.   #How often (in seconds) do you want to do a check for a player to see if he is using forcefield?
  41.   #WARNING: /areload WILL NOT change this value! You need to reload/restart the entire server or use PlugMan!
  42.   CheckTime: 5
  43.   #How long (in half-seconds) to spawn the HeadPlayer and the normal players before they dissappear.
  44.   #A value of 1 is 0.5 seconds. Increase this if the hacked clients are not hitting the fake entities.
  45.   RemoveTime: 1
  46.   #Set to false to disable the player above your head.
  47.   HeadPlayer: true
  48.   #Set to false if you want to disable random checking of players (e.g. if you want to check people only during PVP).
  49.   #The normal checks can create a SMALL amount of lag. If you only care about checking during PVP, disable this!
  50.   NormalChecks: true
  51.   #Set to true if you want to have the head player only, and get rid of the 4 fake entities surrounding the player.
  52.   HeadCheckOnly: false
  53.   #If CheckDuringPVP is on, how long since the player has last hit someone should he be able to be checked again?
  54.   #Increase this if the plugin gives any lag issues.
  55.   PVPTime: 5
  56.   #Normally, the plugin checks player 1, then waits the CheckTime, then checks player 2.
  57.   #Do you want to just check ALL players at once? May become laggy if you have too many players.
  58.   AllAtOnce: false
  59.   #How many players around him should the person have to hit to be detected?
  60.   DetectThreshhold: 4
  61.   #Do you want to check a person for forcefield whenever he hits someone?
  62.   CheckDuringPVP: true
  63. AutoBow:
  64.   #Do you want to enable AutoBow blockage?
  65.   #This will temporarily block someone from using AutoBow until they stop using it.
  66.   Enable: true
  67.   #How many times should the person be detected for AutoBow before the command is executed?
  68.   #It goes up and down by 1 - I don't see a reason for a SafeHitDecrease/LowerAmount variable for this one.
  69.  BowThreshhold: 5
  70.  #Command to execute when a player reaches the Bow Threshhold.
  71.  AutoBowCommand: kick %PLAYER% AutoBow is not allowed!#broadcast %PLAYER% was kicked for hacking! (AutoBow)
  72. All:
  73.  #If you see names flickering in the tab list, ENABLE THIS!
  74.  #It will give NPCs names of players that are online RIGHT NOW.
  75.  OnlinePlayerNames: true
  76.  #Not recommended if you don't have an SSD since it goes through the player files.
  77.   #Gives NPCs real names of people that were previously on your server.
  78.   RealisticPlayerNames: false
  79.   #Do you want to generate a random numeric name for the fake players?
  80.   #Set this to false to just have a "_" for all player names.
  81.   RandomPlayerNames: false
  82.   #Do you want the MapScrewer mobs and the Forcefield around checking mobs to be invisible (I recommend you leave as true)?
  83.   Invisible: true
  84. Soup:
  85.   #Do you want to enable anti-Autosoup?
  86.   Enabled: true
  87.   #How long after last hitting someone is the person not allowed to move items in his inventory?
  88.   SoupTime: 1
  89. Map:
  90.   #Do you want to enable the MapScrewer at all (this ruins minimaps and tracers).
  91.   MapScrewer: true
  92.   #How far away should you check entities and players near the player to hide/unhide them?
  93.   #Lowering this SIGNIFICANTLY decreases the lag per check of each player.
  94.   DistanceChecked: 50
  95.   #How often do you want people to be checked?
  96.   #Raising this over 15 will decrease realism and make players appear to appear out of nowhere.
  97.   #Decreasing it to 1 will mean totan realism, but may cause a bit of lag.
  98.   #WARNING: /areload WILL NOT change this value! You need to reload/restart the entire server or use PlugMan!
  99.   HowOften: 5
  100.   #If an entity or player is closer than this, they will be visible regardless of if you can actually see them.
  101.   MinDistance: 10
  102.   #This will HIDE PLAYERS FROM YOU if you cannot see them!
  103.   #WARNING! THIS WILL HIDE THEIR NAMETAGS TOO!
  104.   HidePlayers: true
  105.   #Do you want to mess up
  106.   SpawnFakePlayers: true
  107.   #The max entities this feature can spawn.
  108.   #Lower amounts will create less lag.
  109.   #Higher amounts will block tracers better.
  110.   MaxEntities: 200
  111. Knockback:
  112.   Launcher:
  113.     #This will enable the launcher. This will launch a player up in the air.
  114.     #If the player does not move, then he is hacking.
  115.     #Disable if you find it annoying, but you may want to try lowering TicksAfterLaunchToCheck first.
  116.     LauncherEnabled: true
  117.     #Commands to execute when person is detected by the Launcher.
  118.     LauncherCommand: kick %PLAYER% antiknockback is not allowed!#broadcast %PLAYER% was kicked for hacking!
  119.     #There are 20 ticks in a second.
  120.     #How many ticks after launch do you want to see if the player has moved?
  121.     #Set this too low and people who are lagging may be detected.
  122.     #Set this too high and it will annoy real members too much.
  123.     #A value of 5 may be acceptable. If this check detects people who are not hacking, increase it to 10.
  124.     TicksAfterLaunchToCheck: 5
  125.     #How high do you want to launch the player into the air?
  126.     SetVelocityTo: 5
  127.   #Do you want to enable AntiKbockback checking at all?
  128.   Enabled: true
  129.   #How many ticks after the player has been hit should it be checked if he has moved?
  130.   #There are 20 ticks in 1 second.
  131.   TicksAfterHitToCheck: 10
  132.   #What is the LOWEST velocity to check a player?
  133.   #Knockback amounts lower than this will not be checked for hacks.
  134.   #Setting this too low means that players just walking normally could change their velocity and be detected.
  135.   MinimumKnockbackCheck: 0.5
  136.   #Set to true if you want to NOT check players if they are standing next to a wall.
  137.   #Hitting a wall obviously stops the player from being knocked back, which may cause bad results.
  138.   DontCheckOnWalls: true
  139.   #Do you want to enable special checking for Projectiles (e.g. arrows)?
  140.   #This will check if the player velocity has gone upwards within a certain time frame, and if it has not, detect the player.
  141.   Projectile: false
  142.   #Command to execute when person is detected for Knockback.
  143.   KnockbackCommand: kick %PLAYER% antiknockback is not allowed!#broadcast %PLAYER% was kicked for hacking!
  144.   #You know how threshholds work by now.
  145.   #If the person is detected for AntiKnockback, raise value by 1.
  146.   #If the person is not detected for AntiKnockback, lower value by LowerAmount.
  147.   #If value hits the Threshhold, command is executed.
  148.   Threshhold: 10
  149.   #How much do you want to lower the threshhold when a player is detected as legit?
  150.   #If hacked clients have a higher detect rate than normal people, it may be a good idea to set a low Difference and a high LowerAmount.
  151.   #With the above suggestion, legit players would be detected more but kept below the threshholds, wheras hacked clients who were detected more would get kicked.
  152.   LowerAmount: 4
  153.   #If a player is sprinting torwards another player, he may travel too far forward after being hit and trigger the detection.
  154.   #Disable this only if MinimumKnockbackCheck is at at LEAST 0.2, if not higher.
  155.   DontCheckIfPlayerIsSprinting: true
  156.   #Do you want to use the Launcher check if a person is detected for AntiKnockback?
  157.   #This will execute INSTEAD of the KnockbackCommand! It will ignore the LauncherEnabled option.
  158.   #Use this only if you want to make doubly sure of players hacking before you kick them.
  159.   UseLauncherIfDetectedForKnockback: true
  160. Specifics:
  161.   #Time after using a CrackShot weapon a person should not be checked for forcefield.
  162.   #The value is in ticks: 20 ticks is 1 second.
  163.   #This is useless if you do not have the CrackShot plugin.
  164.   CrackShotCompatibilityTime: 40
  165.   #Don't change this.
  166.  version: 12
  167.  #Do you want to call a FAKE LEAVE EVENT to the server that tells OTHER PLUGINS that the player has "LEFT" when he is actually kicked?
  168.  #Good for plugins like CombatLog, to punish a player as if he left willingly during PVP.
  169.  #If you have this enabled, you MUST have a kicking or banning command in ALL the hack checks, or the plugin will not function correctly!
  170.  CallFakeLeaveEvent: false
  171.  #If the person says invalid chat, execute this command.
  172.  #This for clients that send invalid messages to the server to kick themselves during PVP and not be detected by current plugins.
  173.  InvalidChatCommand: tempban %PLAYER% 30m Banned for invalid chat used for PVP Logging!
  174.  #1 is looking right up, -1 is looking down.
  175.  #How far down must the player be looking to spawn the headplayer (only works if DontSpawnHeadPlayerWhenLookingUp is true).
  176.  YLessThan: 0.0
  177.  #Do you want to enable the AntiAura.bypass permission for admins not to be checked?
  178.  #This won't affect the AntiAura.debug or AntiAura.reload permission nodes.
  179.   EnablePermissions: false
  180.   #Do you want to show debug messages?
  181.   #This will tell you exactly what kicked the person and what value to change if the person was not kicked correctly.
  182.   #You may want to disable it to reduce unnecessary spam on a server that has already managed to configure the plugin successfully.
  183.   ShowDebug: true
  184. Spambots:
  185.   Captcha:
  186.     #Do you want to enable the CAPTCHA?
  187.     #This will make users type certain letters in chat before they can do ANYTHING!
  188.     Enabled: true
  189.     #Do you want to enable typing of the CAPTCHA Only when the server is detected to be under a spam attack?
  190.     #This is detected by checking the amount of joins and seeing if there are more joins than usual.
  191.     EnabledOnlyWhenSpammed: true
  192.     #Do you want to apply the CAPTCHA to ONLY new players? Existing players won't be asked for a CAPTCHA.
  193.    #Warning: According to Bukkit's API, logging in and then re-logging in 5 seconds later counts as an "Existing player".
  194.     NewPlayersOnly: true
  195.     #Command to execute when detected.
  196.     CaptchaCommand: kick %PLAYER% You failed the captcha!
  197.     #Message to send to people. CAPTCHA is replaced with the CAPTCHA.
  198.     Message: Please type CAPTCHA to move and type commands!
  199.   MessageDisabling:
  200.     #This will stop all chat from a player until he has moved.
  201.     #Will only stop simple spambots.
  202.     StopChatBeforeMovement: true
  203.     #Do you want to disable join and leave messages under an attack?
  204.     #This will only disable the messages iuf the server is detected to be under a bot attack.
  205.     DisableJoinAndLeaveMessages: true
Advertisement
Add Comment
Please, Sign In to add comment