@Aleix16

Provided RSP works at all for our version of Minecraft:

Add this to the configuration (if you have already, add-in the entries).

# ADDED PARTS (PERMDEFS + LINKS)
# PERMDEFS:
permdefs:
    pd_ehome:
        ignore-perm: test.ignore.test
        # No filter perm used, uncomment to use:
        # filter-perm: test.test.test
        have-inside:
            groups:
            - g_ehome
# LINKS:
links:
    world:
        r_ehome:
        - pd_ehome
# TRANSIENT-GROUPS:
transient-groups:
  g_ehome:
  - essentials.home

Here the essentials.home permission is added if you are within the world with the name 'world' inside the region with the name 'r_ehome'. Now with the default setup oif your server you need to ensure that players don't have the essential.home permission by default. Of course you can alter the world and region name and add more/other entries.

WorldGuard does have some support for disabled/enabled commands within their regions via flags, so that might be worth looking up as well.

@ZoefyC

Haven't checked yet. I assume it should work, but it'll be better to test.

RSP 1.9.2 pending approval. Updated to MC 1.8.8 plus latest dependencies.

@chikken001

I'll update ...

I think a question was removed (probably you found the answer).

RSP does not support any regex/wildcard permissions, you'd have to enter each one individually.

Concerning simplified ways to express multiple permissions in an efficient way, one could talk about adding something that can be pre-cached (not necessarily strict regex), e.g.

• someplugin.somerootperm.item.(34|46|112-275)
• someplugin.skill.* or worldguard.region.flag.*.own <- This probably is not recommendable, and i would not have RSP resolve these at runtime like pex used to do, but instead any registered permissions could be scanned for inclusion.

@wesnoah3

You have to insert the world name and region names there instead of TheWrldName and RegionName - then you just append it to the configuration of RSP.

You can use the paste link on the top and set the content type to YAML and just post the link here, or you use code/YAML tags and paste content there, so i can have a quick look:

<<code YAML>>
# Paste your config in here.
<</code>>

@wesnoah3

Have you had a look at the configuration and examples pages?

The blueprint for having some permission inside of a region is this example (from # ADDED PARTS on):

http://dev.bukkit.org/bukkit-plugins/rsp-region-specific-permissions/pages/examples/simple/generic/

The config page might help with the accuracy settings (by default RSP has roughly 4 blocks inaccuracy):

http://dev.bukkit.org/bukkit-plugins/rsp-region-specific-permissions/pages/Configuration/

The minimal thing would look like this:

transient-groups:
  NoKillAll:
  - killallp.safe
permdefs:
  PDNoKillAll:
    have-inside:
      groups:
      - NoKillAll
links:
  TheWorldName:
    RegionName:
    - PDNoKillAll

There is no need to add anything in PEX, but you might want to set the accuracy higher with setting lazydist to 0 either globally. In fact you can also alter the accuracy just for a container region or just for that world, but that should be the follow up steps after making it work at all.

Edit: I am also not 100% sure if this works with WolrdGuard 6 - which versions are you on (server / WG)?

@Vlaminations

Ok, i will check this then.

@Vlaminations

Are there actual issues with 1.9.1?