-
Notifications
You must be signed in to change notification settings - Fork 29
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
Uninstall option #23
Comments
Hey i didnt got ur exact issue but i hope this helps |
What I mean is in every resource on the server that has a manifest file such as fxmanfiest.lua or __resource.lua (which is every single resource) after installing badger-anticheat contains the line 'client_script "@Badger-Anticheat-master/acloader.lua"'. After you remove badger-anticheat that line 'client_script "@Badger-Anticheat-master/acloader.lua"' is still in every single resource in the server and then shows an error in the console because the resources can't find the dependency badger-anticheat because it's no longer there. But the resources are still searching for badger-anticheat as a dependency because badger-anticheat writes that line to every resources manifest file. Does this help you better understand? |
Apparently this doesn't even work anymore so it's pointless now. Hopefully someone can remove it all-together in a pull-request in the near future. I'll leave this open until then. |
I couldn't find a way either to remove the added client script from |
I believe so. FiveM thought it was invasive and I could of sworn they removed the functionality of it from actually doing anything. Someone would need to test it and verify this though |
Once installed this script writes to the manifest of all resources that it is a dependency. After uninstall the scripts are still looking for badger-anticheat because it is still in the manifest to do so. An uninstall bat would be nice to remove client_script "@Badger-Anticheat-master/acloader.lua" in one wack rather than going through each resource and removing it manually.
Something like this.... Which must be ran inside the main resource directory to update all resources.
Manifest_Updater.zip
The text was updated successfully, but these errors were encountered: