Using the plugin is available only to server admins. This is due to the fact that the plugin uses ddraw commands, which, due to the limitations of the Rust engine, are available only to admins. When invoking commands that show a violation, the admin is advised to enable vanish and noclip.
Check for No Recoil can be configured individually for each weapon independently by making changes to the weaponsConfig dictionary in the oxide/data/Arkan/config/weaponsConfig.json configuration file.
For example, by default pistol.python is configured to check only on AIMBOT:
To add the No Recoil(fastclick) check for pistol.python, you need to change this parameter to:
Where:
"AIMDetectEnabled": true - switch on a check for AIMBOT.
"NRDetectEnabled": true - switch on a check for No Recoil.
"NRMinShotsCountToCheck": 3 - the number of shots in a continuous automatic gunfire, from which a No Recoil check is triggered.
"NRViolationProbability": 70.0 - the probability of violation in percent, from which it is believed that No Recoil is detected.
"weaponMaxTimeShotsInterval": 0.15625 - the maximum time interval between shots to detect a continuous automatic gunfire from a given weapon.
"weaponMinTimeShotsInterval": 0.09375 - minimum time interval between shots. Added for future use.
AIMBOT testing is based on the recalculation of the trajectory of the projectile from the point of the shot to the point of impact and vice versa. The trajectory data is calculated based on the shot point and direction data received from the client. The velocity data is calculated from the standard values of velocity (depending on weapons and attachments), drag and gravity available on the server for each projectile. If the control data on the recalculated trajectories do not coincide with the data received from the client, then there might have been a third-party influence on the trajectory of the shot on the client side. What is defined by the plugin as a violation of AIMBOT.
Tip. Violation data collected by the plugin can be saved to a separate file with the command /arkansave . The command /arkansave without specifying a file name, saves to a file oxide/data/Arkan/.json. Then, for test, you can upload the log file to another server with the command /arkanload . The size and seed of the map on the test server must match the size and seed of the map on the server on which the log file was created.
The command /arkanclear clears all data about the detected positives of the plugin.
The data received by the plugin should not be considered as 100% correct. But they allow you to pay attention to the player who has a lot of positives for a possible violation.
The plugin can give false positives. If there are a lot of these false positives, please send log files to [email protected] email. This will help to analyze the reason for the detection of false positives and make corrections in the next update of the plugin.
Check for No Recoil can be configured individually for each weapon independently by making changes to the weaponsConfig dictionary in the oxide/data/Arkan/config/weaponsConfig.json configuration file.
For example, by default pistol.python is configured to check only on AIMBOT:
"pistol.python": {
"AIMDetectEnabled": true,
"NRDetectEnabled": false,
"NRMinShotsCountToCheck": 0,
"NRViolationProbability": 0.0,
"weaponMaxTimeShotsInterval": 0.0,
"weaponMinTimeShotsInterval": 0.0
},To add the No Recoil(fastclick) check for pistol.python, you need to change this parameter to:
"pistol.python": {
"AIMDetectEnabled": true,
"NRDetectEnabled": true,
"NRMinShotsCountToCheck": 3,
"NRViolationProbability": 70.0,
"weaponMaxTimeShotsInterval": 0.15625,
"weaponMinTimeShotsInterval": 0.09375
},Where:
"AIMDetectEnabled": true - switch on a check for AIMBOT.
"NRDetectEnabled": true - switch on a check for No Recoil.
"NRMinShotsCountToCheck": 3 - the number of shots in a continuous automatic gunfire, from which a No Recoil check is triggered.
"NRViolationProbability": 70.0 - the probability of violation in percent, from which it is believed that No Recoil is detected.
"weaponMaxTimeShotsInterval": 0.15625 - the maximum time interval between shots to detect a continuous automatic gunfire from a given weapon.
"weaponMinTimeShotsInterval": 0.09375 - minimum time interval between shots. Added for future use.
AIMBOT testing is based on the recalculation of the trajectory of the projectile from the point of the shot to the point of impact and vice versa. The trajectory data is calculated based on the shot point and direction data received from the client. The velocity data is calculated from the standard values of velocity (depending on weapons and attachments), drag and gravity available on the server for each projectile. If the control data on the recalculated trajectories do not coincide with the data received from the client, then there might have been a third-party influence on the trajectory of the shot on the client side. What is defined by the plugin as a violation of AIMBOT.
Tip. Violation data collected by the plugin can be saved to a separate file with the command /arkansave . The command /arkansave without specifying a file name, saves to a file oxide/data/Arkan/.json. Then, for test, you can upload the log file to another server with the command /arkanload . The size and seed of the map on the test server must match the size and seed of the map on the server on which the log file was created.
The command /arkanclear clears all data about the detected positives of the plugin.
The data received by the plugin should not be considered as 100% correct. But they allow you to pay attention to the player who has a lot of positives for a possible violation.
The plugin can give false positives. If there are a lot of these false positives, please send log files to [email protected] email. This will help to analyze the reason for the detection of false positives and make corrections in the next update of the plugin.