@obscurehero

Does the ChestShop permission work (add/remove) with that setup?

@obscurehero

Did you ever use bPermission groups for this, or have other groups defined those nodes?

@obscurehero

It looks good at first glance, however the wildcard permissions are not processed by RSP in any special way - so if the market plugin does not define those they can not work.

@obscurehero

The config you pasted there does not contain any transient-groups definition, though. Are you using transient permissions on side of the permissions plugin !?

Example: http://dev.bukkit.org/bukkit-plugins/rsp-region-specific-permissions/pages/examples/advanced/negating/

The example would be only really be necessary for overlapping regions, but it shows "transient-groups" as used in RSP.

@obscurehero

I am not sure what exactly happens.

• Does adding the permission work at all?
• If yes, then does removing the permission work on a non-overlapping part?

Maybe you should paste your configuration (pastebin or bukkitdev paste), so we can rule out some things directly, for instance:

You should handle permissions that get removed dynamically fully inside of RSP with transient groups and priorites in permdefs to be able to reliably negate permissions (see examples link in the description above, the bperms groups only carry the filter). That way adding both permdefs at the same time will lead to removal of the permissions, if the permdef that is used for the removal has a higher priority.

@Blacklands

Could be one of the next additions to have group/flag dependent stuff.

You have to add all the regions in the rsp.yml in the links section.

Currently the only exceptions are the generic links for ownership, membership and "every region": __owner__ ... __member__ ... __region__, and __global__ for world-wide.

@Blacklands

Approval pending ...

@Blacklands

I will update the descriptions soon. RSP is still operable, might upload a version compiled for 1.5.2 - i am using it on my own server, so certainly it is still maintained - only adding new features might not happen too much.

@SmallzZz8

Best start with a test!

It is about configuration, commands are of little use (except maybe for reloading configurations of RSP and GroupManager).

Can you test as a normal user ?

I suggest setting up a test thing with this (abstract) example: http://dev.bukkit.org/server-mods/rsp-region-specific-permissions/pages/examples/advanced/negating/#w-reliably-negating-permissions-inside-of-a-region

So just make a test group in GroupManager, like TestRSP and give it the permission "rsp.filter.havesomething", which means nothing by itself but allows to configure RSP to deal permissions on base of that filter, only to those who have it.

Then you choose a permission or set of permissions for testing, something that does not hurt if a tester has it, but which can be easily checked if it works or not works (like setting time or something), these will be input to RSP config.

Next is to set up RSP to normally give the permissions for the whole world.

Partial copy for having the permission in a world (test it that way, just replace permission names and filter permission

permdefs:
  # The permdef to be added normally inside of that world:
  defsomething:
    # The filter permission decides who is affected by this permdef.
    #  The players that have this permission from your permissions plugin,
    #   will have the groupsomething addedm then.
    filter-perm: rsp.filter.havesomething
    have-inside:
      groups:
      - groupsomething

links:
   TheWorld:
     # __global__ concerns "everywhere" in that world:
     __global__:
     - defsomething

# Finally you define the grouping with permissions right here:
transient-groups:
  # The normal group containing the permissions.
  groupsomething:
  - something.second
  - something.first

So after this the players who have the filter permission should have the somthing-permissions in the world "TheWorld".

Next is to set up the negation of those permissions within a certain region. Can you follow / test the above so far? The full example shows how the negating parts are done, maybe you can paste the links, transient-groups and permdefs sections once set up (use <<code YAML>>...<</code>> or a link to a yaml paste).