Commands

[zml2008]

PEX2 needs a slightly different command structure due to important functionality differences.

Here's thoughts:

• /pex reload -- reload configuration
• /pex debug -- toggle debug mode
• /pex <user|group|etc> list -- list all subjects of the specified type
• /pex [--transient] <user|group|etc> <name> <subcommand> --context <key>=<value>

subcommands:

• parent(s)?
  • <add|remove> <subject>
• option(s)? <key> <value>
• perm(ission(s)?)? <node> <true|false|t|f|int val>
• info
• def <true|false|t|f|int val> -- The default permissions value for a subject

Flags: --transient: Whether or not the permission stored in-memory only, meaning anything set as transient will go away when the server stops --context <key>=<value>: The context to perform this action in. Contexts are things like world=myworld or dimension=Overworld

Example usage: Setting up a simple group:

/pex group Member perm worldedit.navigation.jumpto true
/pex group Member perm essentials.tp true
/pex group Member option prefix [Member]

Adding a (currently online) user to that group:

/pex user risaccess1 parent add group Member

(where replacing risaccess1 with the name of the user you want to add)

[zml2008]

Writing out permissions as I go:

• permissionsex.reload: Reload the plugin
• permissionsex.debug: Toggle debug mode
• permissionsex.command.list.<subject-type>
• permissionsex.option.set.<subject>: Set a subject's option
• permissionsex.permission.set.<subject>: Set a subject's permission
• permissionsex.parent.add.<subject>: Add a parent to a subject
• permissionsex.parent.remove.<subject>: Remove a parent from a subject
• permissionsex.info.<subject>: View information about a subject

where <subject> is <type>.<identifier>. own is checked if the subject is the command executor and can also give access to the command.

[zml2008]

Commands are more or less implemented. They'll probably be tweaked over time though.

[Rentai]

Pex reload is given to everyone by default. Without any PEX nodes given out, basic users can reload the files.

[ghost]

Howto set default group for players?

[RunningBuff21]

Hi, I was wondering if you could explain more into the parents and inheriting commands portion of this plugin. How is this done and what is the command breakdown

[sibomots]

Initial setup document / sample .conf ?

I haven't had much success in finding some sample config files

Just a typical server admin structure Server with admins, moderators and players Each with a set of permissions, the higher permissions inheriting from the lower levels

I've used PEX in the Cauldron era, but I think the config file format changed substantially.

[TypicalDarkness]

How can I make players be part of a default group when they join for the first time?

[ghost]

https://forums.spongepowered.org/t/guide-pex-quick-command-reference/8738

[Favorlock]

Are you supposed to be able to do "pex user Favorlock parent add somerandomword admin"? All the examples I've seen use "group" for "somerandomword", but yet I notice that you can use anything for "somerandomword".

[Malachiel87]

how i remove groups?

[Stormbow]

/pex group <group> delete

[crymates]

Is it possible to set permission for "join" and "leave" specific group?

Like Tester123 is allowed to join (set himself) group "newbie" and is also allwowed to leave (remove himself) the group "newbie".

Like current config the following perms should be needed:

                    "permissionsex.parent.add.newbie.user.xxx-xxxx-xxxx-xxxx-xxxx": 1,
                    "permissionsex.parent.add.newbie.own": 1,

Currently that does not work :/

Greetz, Hannes

Btw. perfect for roleplay servers if working, like an officer is on duty and off duty.