Skip to content

Latest commit

 

History

History
74 lines (60 loc) · 4.37 KB

fight.creole

File metadata and controls

74 lines (60 loc) · 4.37 KB

fight

<<<Back to Checks Overview<<<

Checks that at least technically have to do with direct combat.

canceldeadPrevent dead players from hitting due to latency (silent).true
toolchangepenaltyAttack penalty in milliseconds, applied for changing the tool.500



yawrate: Deal penalties for too fast turning, mostly attacking with close and projectile combat.

configDescriptionDefault
activeShould this check be active?true



angle: This check will prevent the player from hitting 2 or more entities at the same time. ToDo

configDescriptionDefault
activeShould this check be active?true
threshold Control the strictness of this check.50



critical: This check will prevent the player from doing fake critical hits to give more damage to entities.

configDescriptionDefault
activeShould this check be active?true
falldistanceTODO0.01
velocityTODO0.1



direction: Players may attack other players and creatures without really looking at them. This is often combined with automatically attacking every living thing within reach ("kill-aura"). This check will check if the attacker looks at his target.

configDescriptionDefault
activeShould players get checked for this type of hack?true
strictExtra strict interpretation, makes close combat more difficult.false
penaltyHow strict should NoCheatPlus be when comparing the players line of view with the his target's location. The value represents (roughly) the amount of 1/100 blocks that the player is allowed to look past the to be attacked entity. 75 (0.75 blocks) seems a good default value.500

TODO: fastheal



godmode: Players may trick Bukkit into not dealing them damage when they get attacked. This will try to identify and correct that behavior.

configDescriptionDefault
activeShould players be checked for this behavior?true



knockback: It shouldn't be possible for the player to deal knockback while standing still also faking knockback distance in any way shouldn't be possible. This check will make sure that the player only deals knockback if he/she is supposed to deal knockback (knockback enchantments are supported here).

configDescriptionDefault
activeShould this check be active?true
intervalTODO50



noswing: Players may attack entities without moving their arm. This is confusing for nearby players, as they won't see who is attacking them or the nearby creatures.

configDescriptionDefault
activeShould this check be active?true



reach: Players may slightly increase the distance at which they can attack enemy creatures/players. This check will try to identify that by comparing player and target location.

configDescriptionDefault
activeShould this check be active?true
survivaldistanceMaximum attack distance for survivalmode. Statically about 3 or 3.5 applies, with latency and moving 4.5 makes sense.4.4
penaltyExtra attack penalty for close combat, dealt on violations.500
reduceEnable/disable the dynamic max-distance feature: If players hit rather at the limit of distance, the dynamic maximum is reduced, so it is harder to use kill-aura. A player that hits between dynamic max and max distance gets a "silent cancel" without violation level added.true
reducedistanceMaximum amount of distance by which the max-distance (survivaldistance) can be reduced.0.9
reducestepAmount to change the dynamic max-distance per long-distance or short-distance hit.0.15



selfhit: This check will make sure that a player doesn't abuse knockback to win some height by doing self hits (supports the SurvivalFly check).

configDescriptionDefault
activeShould this check be active?true



speed: Minecraft doesn't restrict the amount of hits a player can do in each second so we made a check that will prevent a player from going over the allowed hit speed limit (more hits = more damage).

configDescriptionDefault
activeShould this check be active?true
limitHow many hits should be allowed to do in each second?15
shortterm ticksTODO7
shortterm limitTODO6