Today I will be teaching you how to correctly use the 'command_overrides' table located in the ascent 'world' database.
First off allow me to explain what the command_overrides' table does: It is where you can modify the default access flag requirement for GM commands.
Now if that didn't make sense, don't worry. It will all become clearer as time goes on.
First thing you need to do is open the command_overrides table and you should see two columns:
'Command_Name' and 'Access_Level'
The Command_Name is the command you want the user to have (like .mod display, .cheat god, .serverrestart, etc...) and the Access_Level is the level you want the command to be assigned to, we will be using numbers in this guide.
Let's say we wanted to make a guy a GM, but only with certain commands like .kick but not .ban. Since these two are under the same column, if we gave them the letter of that column he/she could kick AND ban. What we're gonna do is make this GM only be able to kick and such.
The first thing we do is make a new column and under 'access_level' put '7' and under 'command_name' put '.kick'. This makes a GM of level 7 able to kick people only. If you want to add more commands make more columns of access_level '7' and add whatever command you want them to be able to use.
There are rules, however, about this table. You cannot use numbers 0-3 because those strings are taken. You also cannot use double digits like 10 or 54 because those are two strings.
This will only work on the server you assigned this to so if you made a new server with a new world DB and tried to give a GM rank '7' then it wouldn't work unless you define them in the 'command_overrides' table.
Credits:
GastricPenguin - helped me learn the Do's and Dont's of this table
[Cloud] - Writing the guide
This is my first guide everyone so please leave any feedback or typo's you see in the guide. Thanks and I hope this helped you
And since no one uses these epic smilies:
:dancing:
~[Cloud]~