-
Notifications
You must be signed in to change notification settings - Fork 73
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
Solution to #103 #105
Solution to #103 #105
Conversation
Thank you for your interest in making ULX/ULib better for all users! We appreciate all the contributions our users send in. However, I'm denying this PR for two reasons.
|
I believe there's also a bit of an issue where you can |
I can see the point you make @Codingale, but this is why banid defaults to superadmins, while ban defaults to admins. |
Just noted, this actually wouldn't fix it anyways. It throws an error:
|
That was a fault on my end. I fixed it for myself but I didn't edit this because it was already closed. |
is it on your repo? @iViscosity I'd like to add it but am too lazy to find out how to check if a group can target another.. |
It is not but I can add it real fast EDIT: Actually, the one I have on there should work. |
I think I tried that one too, also I think running ulx banid via server console throws an error. Edit:
Also doesn't work (Unless a full restart is required) |
Yeah running through console will cause an error now that I think about it. Let me fix that. (Also I don't know if we should be having convo through here :P) |
No description provided.