-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback Version 1.7.0 Beta | Macro Auto-Jump #75
Comments
If you want I have a complete log of all servers, I can send in private, since there is the IP of the players. |
Thank you for testing the Beta version, it really helps me develop Lilac :) Anyway, Macro detection checks if a player is spamming a certain input all the time, the limit being 20 times a second. Macro detection is disabled by default, because it's not something most server owners care about or need; plus it's not a big deal for most servers. That said, perhaps I should add an option to prevent logging of Macro detection, but still detect it. Also, regarding bans for Macros, by default, players get kicked for Macro usage, not banned (Because it's not a cheat feature). Lastly, Macro bans only last 15-60 minutes. |
Perfect, thanks for explaining. On the question of the log, wouldn't it be a good idea to create a separate log for each detection / verification mode? Create a |
Hmm, I don't think server owners would like files to be separate, tbh. Still, I'll put it on my todo list of adding an option to detect but not log Macros :) |
Just moving on to update, so far no errors with the plugin apparently. Bans that are being applied most often would be by: Researching about it I found nothing, could you explain to me what would be the case, any video? |
Anti-Duck-Delay isn't actually the official name of the cheat feature, "Fastduck" is. Fastduck/Anti-Duck-Delay is a cheat feature which disables your duck-delay. Cheats can bypass this by inserting an impossible input value (You can't insert this value normally). I don't think there's any video showing it? At least I'm not aware of one. Edit: Also, version 1.7.0 has new translations, so if you update, make sure you updated those as well. Missing translations can lead to errors. |
Alright, I've updated the ConVar |
Doubt, I leaving the autoupdate cvar enabled:
Do you update to the latest version of the |
I'm not entirely sure what you mean, but I think you're asking if updates can overwrite your config? |
I am going to close this, as no further replies have been made. |
@J-Tanzanite oops, sorry for the absence, I will test this new feature thanks. Do I have to delete the current configuration file for it to update, or would there be some way to update all cvars, the configuration file without me having to delete it and configure it again? |
Sadly, you have to delete the config file and reconfigure it again. :( As far as I know, there is something called autoexecconfig (or something) that I could use, that would append new ConVars to the config file when I release new updates with new ConVars. Hopefully in the future, I will have that setup so that you don't have to delete the config file and reconfigure stuff. |
Apparently everything is fine with the question of the LOG regarding the Macro. I will be closing these issues, any problems return the contact, thank you! |
I would like to say that so far I have not noticed any errors or BUGS in version 1.7.0 Beta that I have been using on my servers.
However I noticed that on all my servers the log is always being updated, detecting the use of Macro Auto-Jump:
Would that be a false positive?
No player has been banned for this reason yet, but all my servers only have this detection in the anti-cheat log.
My servers do not have any plug-ins for Auto-BunnyHop or configuration to facilitate this, except AWP ONLY that I have a plugin for this, but limited to 5 hops and then have to wait 20 seconds to use it again and all servers configured at 128 tickrate.
However, even on servers without this plugin it still detects this macro.
I don't know if it helps, but they are all CSGO servers.
The text was updated successfully, but these errors were encountered: