Multiverse/Multiverse-Core — Issue #426: Allow the autogeneration of unique world perm names. 
Author: FernFerret
Created: 2012-01-22 15:20:33+00:00
State: open
Labels: Feature, Suggestion

As it stands, all world names, when permissioned are lowercased via the superperms api ([PermissibleBase.java#53](https://github.com/Bukkit/Bukkit/blob/master/src/main/java/org/bukkit/permissions/PermissibleBase.java#L53), [PermissibleBase.java#69](https://github.com/Bukkit/Bukkit/blob/master/src/main/java/org/bukkit/permissions/PermissibleBase.java#L69), [PermissibleBase.java#89](https://github.com/Bukkit/Bukkit/blob/master/src/main/java/org/bukkit/permissions/PermissibleBase.java#L89), [PermissibleBase.java#254](https://github.com/Bukkit/Bukkit/blob/master/src/main/java/org/bukkit/permissions/PermissibleBase.java#L254) and [PermissibleBase.java#184](https://github.com/Bukkit/Bukkit/blob/master/src/main/java/org/bukkit/permissions/PermissibleBase.java#L184)).

This means that if you have a world **WOrLD**, it's permission will always be `multiverse.access.world`. That's fine and dandy, except when a user were to _also_ have a world named **World**. This permission would _also_ be `multiverse.access.world`. Obviously, the easy fix is "hey, users, don't name worlds the same thing with different case" (something that is not possible on case-insensitive filesystems). However, I know if I say that, then someone will come up with a reason that they want it.

Since putting in a special case for worldnames seems a bit out of line, I'm proposing the following changes:

1. Uniquify world permissions by adding a digit after them. ex. `multiverse.access.world`, `multiverse.access.world2`
1. If you have permission to access a world's information via `/mv info`, then you will be able to see what permission is required to enter said world.

This is related to #421

This could even be a config variable that would be _off_ by default. I think I like that idea the best. Thoughts?