Does this plugin cause lag?

I have implemented the plugin on the server and the fps has been lowered, any way to solve it?

Is it possible to change the file settings to improve the lagg?

There are some settings that can cause lag. All of the Log settings are intensive.

Version 1.7.1 should improve this issue:

  1. All of the heavy AntiCheat checks have been deferred.
  2. Fire initiators are cached.
  3. This should result in a faster return path for all related hooks, and an improved framerate.

Ok, thank you very much, you did a good job. It is very difficult for me to read the data from /g.log. How can I monitor this data and discover cheaters?
THX

For example:

03/08 13:54:04 | 02395.79s Recoil[02](x=0.036910, y=0.036910) Trajectory(0.964701) Aim(a=0.770584, p=0.988000, r=0.233529) (0.1m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 107.5m]
03/08 13:54:04 | 02395.47s Recoil[00](x=0.045772, y=0.045772) Trajectory(0.966165) Aim(a=0.817503, p=0.988000, r=0.293298) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 99.4m]
03/08 13:54:04 | 02395.36s Recoil[01](x=0.019402, y=0.019402) Trajectory(0.981444) Aim(a=0.778263, p=0.988000, r=0.321031) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 95.5m]
03/08 13:54:04 | 02395.02s Recoil[00](x=0.160315, y=0.160315) (0.0m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 02394.90s Recoil[01](x=0.037109, y=0.037109) (0.0m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 02394.79s Recoil[02](x=0.018459, y=0.018459) (0.0m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 02394.53s Recoil[00](x=0.093237, y=0.093237) Trajectory(0.981266) Aim(a=0.507150, p=0.988000, r=0.416804) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 82.0m]
03/08 13:54:04 | 02394.40s Recoil[01](x=0.061320, y=0.061320) (0.0m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 02394.31s Recoil[02](x=0.139737, y=0.139737) (0.0m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 02393.31s Recoil[00](x=0.013114, y=0.013114) Trajectory(0.983399) Aim(a=0.881459, p=0.988000, r=0.412061) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 82.7m]
03/08 13:54:04 | 02393.18s Recoil[01](x=0.010621, y=0.010621) Trajectory(0.949401) Aim(a=0.908409, p=0.988000, r=0.420390) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 81.5m]
03/08 13:54:04 | 02393.05s Recoil[02](x=0.127771, y=0.127771) Trajectory(0.949895) Aim(a=0.794366, p=0.988000, r=0.406660) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 83.4m]
03/08 13:54:04 | 02392.96s Recoil[03](x=0.116177, y=0.116177) (0.0m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 02392.84s Recoil[04](x=0.043122, y=0.043122) (0.0m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 02392.73s Recoil[05](x=0.019491, y=0.019491) Trajectory(0.950020) Aim(a=0.595201, p=0.988000, r=0.371418) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 88.4m]
03/08 13:54:04 | 02392.62s Recoil[06](x=0.080120, y=0.080120) Trajectory(0.985408) Aim(a=0.522787, p=0.988000, r=0.339536) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 92.9m]
03/08 13:54:04 | 02392.51s Recoil[07](x=0.011271, y=0.011271) Trajectory(0.988580) Aim(a=0.837328, p=0.988000, r=0.313458) (0.0m/s, LR-300 Assault Rifle): NPC(Helicopter)[Body, 96.5m]
03/08 13:54:04 | 02337.33s Recoil[00](x=0.047679, y=0.047679) (0.1m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 02337.21s Recoil[01](x=0.026756, y=0.026756) (0.0m/s, LR-300 Assault Rifle)
03/08 13:54:04 | 01560.00s Recoil[00](x=0.001587, y=0.001587) (0.0m/s, LR-300 Assault Rifle): Player(El-sacacorchos)[Arm, 26.7m]

In general, many values that are below 0.000100 should be a red flag. The number after Recoil[xx] is the burst count for the weapon. Recoil x is yaw variance, Recoil y is pitch variance. Trajectory variance is the difference between projectile distance and actual distance; small values for trajectory indicate some type of projectile manipulation on the client side. Aim variance is reported for 3 categories; Aim a is aim angle variance, Aim p is PvP variance (hit/miss ratio & headshot ratio), Aim r is range variance (based on weapon range, attachments and ammo characteristics).

Violations for an attack will appear, at the end of the line, as:
    [A] - aim violation
    [F] - fire rate violation
    [R] - recoil violation
    [T] - trajectory violation
    [W] - wallhack violation

The example log that you submitted looks clean.