Description:
Hi! I would like to suggest a small but very useful improvement for the AutoDupe module.
The Problem:
Currently, when running AutoDupe, it goes through the duplication methods. If a dupe worked previously but was later patched by the server administration, or if certain dupes have already been tested and failed, the module doesn't remember this. Running them again wastes time and might trigger anti-cheat alerts.
Proposed Solution:
Please add a feature that saves a local history or "blacklist" of dupes that have already been attempted on a specific server.
Allow the user to see which dupes have been tried.
Add an option to skip previously failed/patched dupes automatically so the module only attempts untested ones.
This would make the brute-forcing process much faster and safer. Thank you!
Description:
Hi! I would like to suggest a small but very useful improvement for the AutoDupe module.
The Problem:
Currently, when running AutoDupe, it goes through the duplication methods. If a dupe worked previously but was later patched by the server administration, or if certain dupes have already been tested and failed, the module doesn't remember this. Running them again wastes time and might trigger anti-cheat alerts.
Proposed Solution:
Please add a feature that saves a local history or "blacklist" of dupes that have already been attempted on a specific server.
Allow the user to see which dupes have been tried.
Add an option to skip previously failed/patched dupes automatically so the module only attempts untested ones.
This would make the brute-forcing process much faster and safer. Thank you!