Suggestion 100% Accuracy Reports With Partial Magazine Shots

Return to plugin
cachalote

cachalote

Customer
Hello, I purchased the plugin and while testing it I’m running into some doubts — it’s not working the way I expected. Maybe you can help clarify a few things.
I’m getting reports showing 100% accuracy, but when I check the report details I see something like:
Shots (F / H): 6 / 6
Hit Areas: Chest 1 / Arm 1 / Head 4
Average Distance: 85.7 m
At first I assumed it was clearly a cheater. But when I tried to do shooting tests, I asked the player to always shoot a full magazine, and I got mixed results at different distances and with different AK setups (with and without attachments). I’m attaching some reports.
My questions are:
  • If the player fires 30 bullets, why does the system sometimes count only 7 shots and 7 hits as 100%?
  • Why does it treat 100% as “all body” (or count it as 100% regardless of hit location)?
  • Do you have any reference I can use to compare whether players are legitimate?
  • Does the plugin generate a full detailed log that I can export, so I can feed it to an AI (like ChatGPT) to help analyze all player reports?
  • I also use other tools like PvP Combat Logger (Codefling) and the rustadmin.com console, and the hit/shot numbers don’t match the plugin’s numbers. I’m not sure which one to trust.
For context, I configured it to 90% and 5 shots (on my server it’s rare to see fights with more than ~10 consecutive AK shots; most “arkan-style” reports are 5–6 bullet bursts).
Thanks in advance.
 

Attachments

  • Screenshot_107.jpg
    Screenshot_107.jpg
    62.6 KB · Views: 6
  • Screenshot_108.jpg
    Screenshot_108.jpg
    64.5 KB · Views: 8
  • Screenshot_109.jpg
    Screenshot_109.jpg
    57.9 KB · Views: 6
  • Screenshot_110.jpg
    Screenshot_110.jpg
    54 KB · Views: 8
Recent First Highest Voted
You must log in or register to reply here.
  • About us
    Game4Freak is a Rust plugin marketplace and modding platform offering free and premium plugins for server owners looking to improve and take their servers to the next level.
  • Our
  • Your
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -