So this is all in game chat there is no option to do it in files for people who have common sense.
Any chance to have wildcard permissions?
e.g.:
from:
"SpongeAdmin": [
{
"permissions": {
"sponge.command.chunks": 1,
"sponge.command.config": 1,
"sponge.command.reload": 1,
"sponge.command.save": 1,
"sponge.command.heap": 1,
"sponge.command.version": 1,
"sponge.command.audit": 1
}
}
]
to:
"SpongeAdmin": [
{
"permissions": {
"sponge.command.*": 1
}
}
]No need for * permissions. See:
2 Likes
Sure you can do it in files, (it has to save its data somewhere) I just really doubt zml supports it. 
Correct.iirc Zml wants to avoid users breaking their config files. Thus official support is for gamechat configuration only.
I have a problem of my console not being able to do anything. Is there a way to fix this?
Yes, donāt explicitly set the default permission to false. That overrides the default to true that the console has.
This is what it says, āpermissions-defaultā: 1 Yet console doesnāt have permissions still
Okay im not sure if im doing something wrong or what but i cant seem to get Rankings to work when ever i try to use /promote or /demote it says āUsername 10 was not on ladder defaultā or if i try /pex ranking default it says āNo ranks in ladder defaultā
perms file : http://pastebin.com/P7M1PG6F
Because thatās not how ranks are done anymore. Use the commands:
/pex rank default add group <group>
to add the first group to the rank ladder (and any furthers. Once the ladder already exists, you can use /pex rank default to view and modify the rank ladder.
And to promote and demote users:
/promote user <name>
/demote user <name>
We have gotten it to work, thanks!
ugh okay so my perms file got removed (no big deal) but after setting stuff back up the console wasnt alowed to use commands tho prior to setting it up it had been i havnt restricted any commands and to fix this i did /pex System Console def true but now all command blocks dont seem to work and the server still has a tag even after telling it not to witht the command zml told me to use. server gives this
7:38:12 PM CONSOLE: thread/ERROR]: Couldnāt process command: ā@p subtitle {text:"=-=Spawn=-="}ā
7:38:12 PM CONSOLE: cannot be cast to org.spongepowered.api.util.command.CommandSource
7:38:12 PM CONSOLE: Source) [?:1.8.0_11]
- pastebin your permissions file
- paste the full error, not just some random lines
soz i thought i had server to send full errors 
Permissons: http://pastebin.com/tksuMQj0
Full error: http://pastebin.com/hv3W5wBr
setting the console to have a parent group or giving it default true fixes this (figured it out from something you said in FeatherChat thread):
/pex system console def true | /pex system console parent add group Admin
setting the system default with default false after this doesnāt block console 
In general you really donāt want to set the global permissions default to be explicitly false ā thatāll cause problems like this since you override all the defaults that are applied normally.
and @Zakari_Chupinski that error looks like an error in Sponge itself ā Iāll take a look at it and see what I can find.
Excuse my silly question: The usual setup for grey-listing a server is to have a default group with very few (or no) permissionsā¦ is there a way to accomplish that easily, without compromising the console?
1 Like
odd. cuz it only started happening since i messed up my perms file and started it from scratch
@Inscrutable
yeah, in that case you might want to set the console to default to true. But that seems like a really good/important use case for per-subjecttype defaults. Iāll bump that issue up to high priority for getting into PEX.
@Zakari_Chupinski sure PEX isnāt giving you any errors on start?
2 Likes