Recent Discussions
Disable Commands by Name FOR OPERATORS? [Fabric]
Unanswered
Brown bear posted this in #questions
97 messages
0 views
Brown bearOP
Is there any possible way to restrict what commands players WITH OPERATOR can use, specifically via an UPKEPT fabric mod.
To specify, I am looking for the server to automatically reject specific and customisation commands (such as /give, /gamemode, /setblock, /fill, /effect, ect) from anyone WITH operator
NOT to setup a permission plugin/system that instead manually grants players access to commands by name
I feel like ive searched the entire internet with no modern-day solution
To specify, I am looking for the server to automatically reject specific and customisation commands (such as /give, /gamemode, /setblock, /fill, /effect, ect) from anyone WITH operator
NOT to setup a permission plugin/system that instead manually grants players access to commands by name
I feel like ive searched the entire internet with no modern-day solution
i wouldnt even suggest giving players OP just giving them sepcific groups with perms
like mod/staff/admin etc
server side only need ^
Brown bearOP
NOT to setup a permission plugin/system that instead manually grants players access to commands by name 
Brown bearOP
Thank you for trying
(technically this is Manually, just gui format but ok)
i wanna know first before i speak more
ill let you type 🙏
ill let you type 🙏
Brown bearOP
The reason being I hate back-end file editing
What I want specifically is for the operators on my server to be able to kick/ban respectively since we have a greifing problem, but NOT be allowed to use things like /tp, /give, /gamemode, ect.
Sometimes I'll want users to have access to this and sometimes not, controable from in-game
The solution would be disallow any operators to even run the commands I dont want, and I can control if they even have op within these paramiters in-game with just /op {user} or /deop {user}
What I want specifically is for the operators on my server to be able to kick/ban respectively since we have a greifing problem, but NOT be allowed to use things like /tp, /give, /gamemode, ect.
Sometimes I'll want users to have access to this and sometimes not, controable from in-game
The solution would be disallow any operators to even run the commands I dont want, and I can control if they even have op within these paramiters in-game with just /op {user} or /deop {user}
additionally, I hear getting all the necessary stuff to port luckperms to fabric is a pain in the ass
Brown bearOP
"port" i know it exists but it needs placeholders and something about needing to run it the first time on spigot to create the necessary directories
luckperms has its own fabric placeholders api that uses the fundemental api system that most plugins do
Fpapi its called
Brown bearOP
You see, this is where we get to territory where I have 0 idea what any of this means
I can drag files into the mods folder and I can set values to true or false in .txt files
I can drag files into the mods folder and I can set values to true or false in .txt files
@Brown bear I dont understand any of this
its a placeholder api wiki
the one that most spigot/plugins use
also no mod uses .txt
or hell Why not just luckperms, what exactly is wrong with it?
its clean and gui so you can do it snappy, and has its method of adding to databases / exporting to import to other servers
its clean and gui so you can do it snappy, and has its method of adding to databases / exporting to import to other servers
i dont think thats clear on my end
@Tamz or hell Why not just luckperms, what exactly is wrong with it?
its clean and gui so you can do it snappy, and has its method of adding to databases / exporting to import to other servers
its clean and gui so you can do it snappy, and has its method of adding to databases / exporting to import to other servers
Brown bearOP
you dont seem to be understanding me so i hope this makes it more clear
Loading...
Loading...