Mod Perms
Need help doing that " Fixed an issue where you couldn't set Allow/Exclude Roles/Users/Channels on any of the available " but somehow i can't find where to set it that way so that mod can't strike/ban admins.
Wfeel free to ping me
L@没落侍 Thank you for your report, I've pushed a security update and fixed the problem
Wit should be fine now ?
LYes sir
Wyet i can still warn a admin using just mod
Whmm
LWell, imo mods should be able to point out misbehaviour of other mods, even when they're higher in roles
W
Ltta mute log fix
Wwell what if a mod's is hacked , they could possible just ban everyone
LNo, they can't ban people
L(People above them)
Wlet me test rq
Wthey can't but the bot can ? cause what if it's role is above other's ?
LI'm not sure I understand that correctly
LIf the bot is above a user it can ban them yes.
If the ban command is executed by a member below the member they're trying to execute it on, the bot will deny the request
If the ban command is executed by a member below the member they're trying to execute it on, the bot will deny the request
Wah ic , yeh tested it
Wit works aight
Lwas that meant to show the broken <t::f> things or that the role hierarchy doesnt matter on muting members?
W2nd one
Lill reverify all cmds, give me a bit
Walthough admin wasn't muted
Wbut the commad was for it
Lyeah admins cant be muted, thats a discord limitation
Wmhm
Wlike before
Wwe couldn't strike/warn someone above our role
Wbut now we can
Wooof
Wsry
Lwhats up
Wwhole strike setup is messed up
Wlemme see if i can set it like it was before
Wi just gave 10 strike to someone
Wthey still in the server except muted
Lthere's an issue while saving strikes
Lill get to that right after checking the mod commands
Lgive me a little, ill ping you again
Wyeh
W
Wafter 10 strikes , it still shows 1 warns
Lyeah, they arent saved to the DB
Lim getting the errors
Wic ic
Wit's doing this too
Lthats desired
Wwhomever gets striked , it does that
Whow do i change it btw ?
Lyou cant
Wic