Bukkit

I have one group on our server set for:

boutique.shop.*

Everyone else has:

    -boutique.default
    -boutique.customertp.*
    -boutique.customerrequesttp.*:
    -boutique.ownertp.*:
    -boutique.ownerbindtp.*:
    -boutique.*

Yet still, people are able to use /shop go, to teleport to shops, which I don't want to allow.

Am I missing something or is this a bug?

I designed the permission system to have a lot of inheritances. By default, all of the permissions are set to false except for boutique.default. This node is meant to give out a series of permissions, so negating it, as you have done, should stop them using most of the plugin, including teleportation.

What permission plugin are you using? I've had a few problems with getting bukkit's permission system to understand what I want it to do - I've not know whether this was a limitation of bukkit, a limitation of my understanding of its permission system, or a limitation of my understanding of bukkit's api.

I'll do a few experiments to see if I can work out what's going wrong with it.

Using PEX here.

Why not make it easy on yourself and use Vault? Then you don't have to worry about different Permission systems, it's a very common and popular library:

http://dev.bukkit.org/server-mods/vault/

Sorry about not dealing with this soon - I've been a little busy. We're using PEX on the server I play on - now when Boutique's permissions were introduced, I didn't have the ability to set the permissions up myself and just assumed that they'd been set up in a particular way. Now that I check stuff out, I'm seeing some inconsistencies. Tell me, are people able to use request teleporting to teleport to closed shops?

As for vault, that'll mean that servers have to run vault to run Boutique won't it? That's something I'm not particularly interested in, even if Vault is near-ubiquitous.