-
Posts
133 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Pho3niX90
-
Could you please provide me with the file in question.
-
Changed Status from Pending to Closed
-
Things that can help development is maybe letting me know of false positives, and maybe your analysis on why it was detected incorrectly. The default settings isn't fit for all servers, a heavily density server, like RP or aimtrains, might need shorter detection ranges etc.
-
Changed Status from Pending to Closed Changed Fixed In to 1.2.90
-
This is fixed now
-
Changed Status from Pending to Work in Progress
-
Hi Jayson I am actively working on finding the cause of this. Unfortunately it's extremely niche. If you can provide me with a demo file not working, and one that is, that will help immensely. Other possible factors that might help: Does this occur only for users that disconnected? Or all? Does this occur only when recordings are split? Or all?
-
Changed Status from Pending to Work in Progress
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Not a Bug
-
unfortunately at this stage the only way to know if a player has left, is after the fact. It's impossible to anticipate a player leaving the game beforehand. Once a player has left, the required data to form the recording, has disappeared. I am actively looking at ways to properly handle this scenario.
-
Yes this is possible. My discord handle is Pho3niX90#8454 PS: having it enabled for everone doesn't affect server performance. It's ran on my own servers as well. -
If a player should be tracked if they are constantly finding tool cupboards
-
Apologies for the late reply. Yes it's still maintained.
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.2.10
-
Changed Status from Pending to Can't Reproduce
-
This seems to be related to the items in stash section. The plugin is currently being reworked and will be updated the weekend.
-
Changed Status from Pending to Work in Progress
-
Changed Status from Pending to Can't Reproduce
-
Can you give me more information regarding your config? When exactly did it stop generating stashes? Does it print in your logs that it placed stashes? Did you wait for it to first generate a spawn file for your map? Are you using procgen maps or prebuilt?
-
Currently not, however will add it in ASAP.
-
Everything is bypass able when the right people know how to bypass it. Ergo, no video explaining how it works. It's currently on beta, and that is why it's on sale. The sale ends the 20th. Thus far, the feedback has been amazing, and reviews amazing on another site. Nothing is fullproof, however, this will definitely assist you greatly in finding espers, and when paired with ADR, it will provide substantial evidence as well. I use this on my own servers, with 300 online players, and have caught many espers that wasn't suspicious before.
-
Unfortunately there isn't any videos yet. I will see if I can do one, but it might just give enough information to circumvent the detection if a video is out in the open.
-
Version 1.1.3
364 downloads
This is a simple tool to help you catch ESPer's. Unlike methods in the past requiring cheaters to fall for traps, this one will be watching without having to give them any bait! This plugin is still in "beta" and is offered at a reduced price for a limited time. Since 1.0.12, the embed now includes a radar image to show violations (red line): The above embed shows the culprit, with quick links to Steam, Battlemetrics, and ServerArmour. Along with each violation that caused the trigger, the consist of the violation id, the time it happened, and steamid and distance from the culprit. It is highly recommended to use along with ADR, although not required, but can easily eliminate false positives by having the option to watch the player from the demo. Commands /testesp - this will send a test embed to your configured webhook. Permissions espdetection.ignore Ignores specific players who are granted this permission. Config options explanation General Max distance to check The maximum to check if the player is ESPing. (default 150 outside, 100 inside) Check Interval How often should a player be checked (default 1 second) Ignore Players Idle Ignore players that haven't changed position (default 15 seconds) Only track players with active weapons Track players that have equipped weapons only. (default true) Auto Demo Record (only applicable if Auto Demo Record is installed) Record Length How long should the triggered recording be (default 10 minutes) Discord Webhook Where the logs & ADR recordings should be sent to Webhook Title Title of the embed Violations Probability % Which % probability should trigger a Discord embed and ADR recording. (default 40%) Samples How many samples should be kept in memory, to calculate the probability (default 20) Weapon Specific Configs These change characteristics of weapons Weapon Shortname Max distance to check This overrides the general setting for the weapon only Track if set to false, a player will be ignored if he has this weapon equipped. (default true) Attachment Specific Configs These change characteristics of attachments Attachment Shortname Add distance while aiming As the name suggests, it adds extra distance to the previous configs, useful for when aiming with an 8x or 16x Track if set to false, a player will be ignored if he has this weapon equipped. (default true) NOTE: if you are using ADR, a good command to use when reviewing the demos are `debug.culling 1`$25.00
