🔑 PermissionsEx v2.0 [API 5]

Lemonous · September 22, 2015, 7:32am

Instead of "homes" = "10", that place in the config should contain:

"warrior" = "2"
"captain" = "5"```
And so on for all your ranks that you want to give more homes (If that gives an error, add a comma after "1" and "2")

Then you give Player the permission `essentials.homes.multiple.player`, and you gove Warrior the permission `essentials.homes.multiple.warrior` and so on for each of your ranks.

It is not possible to use PermissionsEX to give money. You must find another plugin for that.

Alfista · September 22, 2015, 11:51am

The permissions should be added to the ranks section?
And when I put “player” = “1” how it will the system know that it goes to the homes?

it should looks like these than:

“group”: {
“Player”: [
{
“permissions”: {
“tpa.use”: 1,
“tpa.accept”: 1,
“tpahere.use”: 1,
“tpadeny.use”: 1,
“minecraft.command.tp”: 1
},
“options”: {
“player” = “1”,
“warrior” = “2”,
“captain” = “5”,
“startingbalance”: “100”
}
}

.
.
.

"schema-version": 4,
"rank-ladders": {
    "warrior": [
        "index:2",
        "group:Player",
        "essentials.homes.multiple.warrior": 1
    ],
    "captain": [
        "index:3",
        "group:Player",
        "essentials.homes.multiple.captain": 1
    ],
    "player": [
        "index:1",
        "group:Player",
        "essentials.homes.multiple.player": 1
    ]
}

zml · September 22, 2015, 1:32pm

So that rank ladders section you posted is not exactly valid json, and also not correct for PEX. Take a look at https://github.com/PEXPlugins/PermissionsEx/blob/master/permissionsex-core/src/test/resources/ninja/leaping/permissionsex/backend/file/test3to4.post.json for an example of a simple permissions file.

Mr.Costa · September 22, 2015, 2:05pm

Can anyone tell me if I’ve done anything wrong in the json? I think it’s all good but I’m not exactly the best doing this http://pastebin.com/Cc7YmLuu

zml · September 22, 2015, 4:07pm

A group inherits data from its parents, so you did parents entirely in reverse of how they should be put.

Tzk · September 22, 2015, 4:23pm

i guess it’s time to write some basic docs

Mr.Costa · September 22, 2015, 4:48pm

Ok I see, changed that. Are there any more errors?

Alfista · September 23, 2015, 8:50am

OKI have looked at your file, but i don’t fully understand it.
I see that you have two ranks (default, moderation) and you have added them some groups.
The groups are the same for one rank, only the difference is in homes and these rewards that I will give the player?
And the same for the second rank?
Is possible to post full PEX config file to have a look at it?
And is needed then to each group put the option “rank”=“xx”, where xx is the number of each rank to have the possibility to then switch it?
If is possible can you explain me the complete rank system?

Inscrutable · September 23, 2015, 9:39am

I’m just rambling here, but maybe there’s an easier way than full docs
Some kind of “default” configuration (linked in OP) might be helpful, the same way the original PermissionsEx did. It would give new users something to start from, and might help resolve some questions.

Alfista · September 23, 2015, 1:38pm

I asked for it but now, I’m preparing it, but need understand some features of PEX and complete some basic permissions from the vanilla, sponge and some basic mods

p0wd3r · September 24, 2015, 12:22am

I’m having a hard time setting default permissions. Do I need to manually add every user that joins into the base group I’ve create? If I add a user to the “Grunts” group, it works as expected, however I cannot get the default users to take this permission by default. What am I missing?

Using Spong/PEX/Core. Here is the config…

MoeBoy76 · September 24, 2015, 1:52am

are they not getting permissions or are you just saying that it doesn’t assign them the group in the permissions.json?

p0wd3r · September 24, 2015, 2:06am

They get no permissions. A new user is very locked down. They can build n such, but they can’t chat, warp, or set home or whatever I have set in the “Grunts” group. I thought the part…

"default": {
    "default": [
        {
            "contexts": {
                "srcip": "127.0.0.1"
            },
            "parents": [
                "group:Grunts"
            ]
        }
    ]
}

… would do the trick, but it isn’t working the way I thought it would.

If I add the user to the “Grunts” group, it works perfectly. Ladder works, all that works, but I don’t know if there is a way to handle unknown users, or if I have to add everyone that joins. I don’t want to have a giant list of users in there if I don’t have to.

zml · September 24, 2015, 2:13am

Yeah, the issue there is you’ve added the default parent to the segment restricted to only local users (the contexts part). Add a new segment to the default:default subject (a new object in the subject’s list), and add the parent there.

p0wd3r · September 24, 2015, 2:51am

Beautiful! That did the trick!

    "default": {
        "default": [
            {
                "contexts": {
                    "srcip": "127.0.0.1"
                }
            },
			{
                "parents": [
                    "group:Grunts"
                ]
            }
        ]
    }
},

Now the commands work, but the chat doesn’t, I think that has to do with the channels in Core though, I can send chats and join channels and what not, but I don’t see the chat messages. My admin user sees it though, so I know it is going through. I’ll post back when I figure out that part.

Also, a JSON validator is extremely handy, for those having formatting problems, check this site http://jsonlint.com It’ll show you where your invalid commas and spacing are.

EDIT
I was missing the permission node for “core.channel.receive”, once I added that, I can see the chats now! w00t!

Alfista · September 24, 2015, 8:50am

Do you know how to use ranks and they features?

Lemonous · September 24, 2015, 12:34pm

I got several rank ladders to work by changing the default in the command to staff, and anything else should work as well. Here’re my rank ladders as they ended up in permissions.json:

    "rank-ladders": {
        "default": [
            "group:Tier1",
            "group:Tier2"
        ],
        "staff": [
            "group:Helper",
            "group:Admin",
            "group:Mod",
            "group:Owner"
        ]
    }

@Alfista You might want to see this snippet too. Oh, and the lines 111-118 in the Pastebin you quoted:

    "rank-ladders": {
        "default": [
            "group:Grunts",
            "group:Helpers",
            "group:Mods",
            "group:Admins"
        ]
    }

Alfista · September 24, 2015, 2:29pm

But I don’t fully understand the settings. You have there created two ranks" default and staff. Is it correct? Each rank work independently?
When we work with Default. You have there added 4 groups. When I change the ranks, then the player who I changed the rank will skip from one group to another? Thats the point of the ranks? And all settings and changes are then made in the appropriate group?

Lunatic_X · September 24, 2015, 3:09pm

I would wish if somebody who has big knowledge of this plugin/mod to make tutorial becasue for somebody its easy to use,but for me i have no idea how to use it or add groups or add premissions and on my server i added Pex and Core and when i am opped i have no premissions to any command why is that?
And i have “op-permission-level=4” set in server.properties

Lemonous · September 24, 2015, 6:43pm

Yes, that is correct. Each rank ladder works independently.

If you promote or demote someone within the rank ladder default, they will move from one group to another inside the same rank ladder. For example, promoting someone from Helpers to Mods will remove them from the group Helpers and add them to the group Mods. That is the point of the ranks, yes

@Lunatic_X: OP is disabled when you install PEX