Recent Reviews

1. 
   IHaxMC

   3/5,

   Version: 1.2

   i rate 3 stars because it is not made in the best way, but because it works, i will give 3, a better way is to check if a hit distance is more than 3, add 1 to a variable, if the variable is more than 3, flag, if the hit is less than 3, clear the variable, :)

   Aug 10, 2018

   1. 
      Author's Response

      Thanks for the feedback, any suggestions? Dm me

2. 
   jaylawl

   5/5,

   Version: 1.1

   "Don't remove the %{_d}% unless you know what you're doing"

   Jul 28, 2018

   1. 
      Author's Response

      I don't understand what you mean by this.

3. 
   Ofus

   4/5,

   Version: 1.1

   I like the idea of logging illegal hits and the fact you got rid of those useless stops:
   
   Now i've looked in to your skript a little further here are things to improve:
   
   - Variables - any use of {variable.index} (dots in general) is never really a good idea even when followed by {variable.index::index}
   - Waiting - I don't see why you're waiting ticks in certain situations but that's not exactly an issue just peaked my curiosity and may be unnecessary
   - else statements (line 130) - Remember if you're using else you don't have to be so specific in certain situations. If it doesn't follow in to any of the if conditions it will look for the else statement no matter if you've used an "else if"
   - Also try look up on using cooldowns properly in skript

   Jul 27, 2018

   1. 
      Author's Response

      Thanks, will work on stuff!

4. 
   Ofus

   2/5,

   Version: 2.2-dev37c

   3 things that lost you 3 stars:
   - Poor variable usage
   - Using "stop"
   - "distance between attacker and victim" never actually functions very well and usually prints out a number larger than 5.

   Jul 27, 2018

   1. 
      Author's Response

      Thanks for telling, I've tested lots of times and I've never seen it go more than the aprox. distance of the attacker.