[ADMN/DEV] PermissionsBukkit v2.0 - Official Default Groups Plugin [1.5.2-R1.0]

PermissionsBukkit - the Official Default Groups Plugin
Current Version: v2.0
Find PermissionsBukkit on BukkitDev!

If you are getting a specific error or cannot determine what is wrong with your permissions file, filing a ticket on BukkitDev will make me much more likely to respond to you; general questions are best to ask in this thread or on the forums on BukkitDev.

It's been a long time coming, but with the accomplishment of build 1000 Bukkit has finally accomplished a built-in Permissions system (codenamed Superperms). For more info on how they work, and how to integrate them with your plugin, see the official Permissions FAQ. Keep in mind that you should rarely, if ever, have to hook this plugin directly; instead keep things in the realm of checking player.hasPermission("yourplugin.node"). The FAQ thread has more info on how to use Superperms with things like chat prefixes/suffixes.

Features:

• Storage of users and groups in plugins/PermissionsBukkit/config.yml.
• Both users and groups can be assigned individual permissions and parent groups to inherit permissions from.
• Support for global and per-world permissions.
• Reload configuration from file with out reloading the plugin.
• Ability to check if a player has a specific permission node.
• Ability to dump all permissions a player has and the plugins that set them.
• Ability to print plugin, description, and default for a given permission node.
• Ability to modify the permissions of groups and users and the groups of a user in-game.
• Built-in antibuild via the "permissions.build" node (defaults to allowing anyone to build).
• A minimalistic bridge from Permissions 3.0 to Superperms is available as a separate plugin, which does not depend on PermissionsBukkit.

Command Usage:

Show Spoiler Hide Spoiler

PermissionsBukkit uses the command /permissions, with aliases /perms and /perm.

/permissions reload - reload the configuration from disk.
/permissions check <node> [player] - check if a player or the sender has a permission (any plugin).
/permissions info <node> - prints information on a specific permission.
/permissions dump [player] [page] - prints info about a player's (or the sender's) permissions.
/permissions setrank <player> <group> - set a player to be in a group with per-group permissions.
/permissions group - list group-related commands.
/permissions group list - list all groups.
/permissions group players <group> - list players in a group.
/permissions group setperm <group> <[world:]node> [true|false] - set a permission on a group.
/permissions group unsetperm <group> <[world:]node> - unset a permission on a group.
/permissions player - list player-related commands.
/permissions player groups <player> - list groups a player is in.
/permissions player setgroup <player> <group,...> - set a player to be in only the given groups.
/permissions player addgroup <player> <group> - add a player to a group.
/permissions player removegroup <player> <group> - remove a player from a group.
/permissions player setperm <player> <[world:]node> [true|false] - set a permission on a player.
/permissions player unsetperm <player> <[world:]node> - unset a permission on a player.

All commands have in-game help and are usable from the server console.

Configuration:

Show Spoiler Hide Spoiler

A permission node is a string like 'permissions.build', usually starting with the name of the plugin. Refer to a plugin's documentation for what permissions it cares about. Each node should be followed by true to grant that permission or false to revoke it, as in 'permissions.build: true'. Some plugins provide permission nodes that map to a group of permissions - for example, PermissionsBukkit has 'permissions.*', which automatically grants permissions for all PermissionsBukkit commands. You can also specify false for permissions of this type.

Users inherit permissions from the groups they are a part of. If a user is not specified here, or does not have a 'groups' node, they will be in the group 'default'. Permissions for individual users may also be specified by using a 'permissions' node with a list of permission nodes, which will override their group permissions. World permissions may be assigned to users with a 'worlds:' entry.

Groups can be assigned to players and all their permissions will also be assigned to those players. Groups can also inherit permissions from other groups. Like user permissions, groups may override the permissions of their parent group(s). Unlike users, groups do NOT automatically inherit from default. World permissions may be assigned to groups with a 'worlds:' entry.

The cannot-build message is configurable. If it is left blank, no message will be displayed to the player if PermissionsBukkit prevents them from building, digging, or interacting with a block. Use '&' characters to signify color codes.

An example configuration file might look like this:

Code:

users:
    ConspiracyWizard:
        permissions:
            permissions.example: true
        groups:
        - admin
groups:
    default:
        permissions:
            permissions.build: false
    admin:
        permissions:
            permissions.*: true
        inheritance:
        - user
    user:
        permissions:
            permissions.build: true
        worlds:
            creative:
                coolplugin.item: true
        inheritance:
        - default
messages:
    build: '&cYou do not have permission to build here.'

Permissions:

Show Spoiler Hide Spoiler

PermissionsBukkit checks for the following permission nodes:

• permissions.build - Allows a player to build. Defaults to true.
• permissions.help - Allows viewing of usage for /permissions.
• permissions.reload - Allows use of /permissions reload.
• permissions.check - Allows use of /permissions reload.
• permissions.info - Allows use of /permissions reload.
• permissions.dump - Allows use of /permissions reload.
• permissions.group.help - Allows viewing of usage for /permissions group.
• permissions.group.list - Allows use of /permissions group list.
• permissions.group.players - Allows use of /permissions group players.
• permissions.group.setperm - Allows use of /permissions group setperm.
• permissions.group.unsetperm - Allows use of /permissions group unsetperm.
• permissions.player.help - Allows viewing of usage for /permissions player
• permissions.player.groups - Allows use of /permissions player groups.
• permissions.player.setgroup - Allows use of /permissions player setgroup.
• permissions.player.addgroup - Allows use of /permissions player addgroup.
• permissions.player.removegroup - Allows use of /permissions player removegroup.
• permissions.player.setperm - Allows use of /permissions player addgroup.
• permissions.player.unsetperm - Allows use of /permissions player removegroup.

Also, the following parent nodes are provided for convenience:

• permissions.* - Maps to permissions.help, .reload, .check, .info, .dump, and to permissions.group.* and permissions.player.*. Defaults to op.
• permissions.group.* - Maps to permissions.group.help, .list, .players, .setperm, and .unsetperm.
• permissions.player.* - Maps to permissions.player.help, .groups, .setgroup, .addgroup, .removegroup, .setperm, and .unsetperm.

Frequently Asked Questions:

1. Where are my * nodes? (open) 1. Where are my * nodes? (close)

Bukkit's Superperms has no built-in concept of a global '*' node that automatically gives all permissions, which is intentional - a player can instead be given all permissions by being given 'op' status (that is, listed in ops.txt). Additionally, individual plugins define a parent node (which could be 'pluginname.*' or 'pluginname.all' or anything else) which maps to whatever subpermissions in that plugin the author desires.

An example is PermissionsBukkit, which provides three such permissions: 'permissions.group.*' for all /permissions group commands, 'permissions.player.*' for all /permissions player commands, and'permissions.*' for all /permissions commands (including permissions.group.* and permissions.player.*).

If you are using SuperpermsBridge, you can do something similar to '*' nodes for plugins which use Permissions 2.7/3.1 - see the next FAQ for more information.

2. How do I use SuperpermsBridge? (open) 2. How do I use SuperpermsBridge? (close)

SuperpermsBridge is kind of like FakePermissions for GroupManager or PermissionsBridge for PermissionsEx. Once it's installed, it pretends to be the Permissions plugin and converts any plugins that use Permissions 2.7 or Permissions 3.1 to use Superperms instead.

You can have PermissionsBukkit without SuperpermsBridge or SuperpermsBridge without PermissionsBukkit if you like, but both of these are limited in functionality. If you install SuperpermsBridge without PermissionsBukkit you will not be able to make use of PermissionsBukkit's groups feature or admin commands, and if you install PermissionsBukkit without SuperpermsBridge, plugins that have not updated to use Superperms directly will not function.

For plugins that use Permissions 2.7/3.1, you can use the special node 'superpermbridge.*' to give the equivalent of what used to be the '*' node for plugins that do not use Superperms directly. If you don't want to give the * node, you can also use the node 'superpermbridge.pluginname' to do the equivalent of what used to be the 'pluginname.*' node. Once again, these only apply to plugins that SuperpermsBridge handles and not to plugins using Superperms directly.

3. How do I use the root permissions.yml? (open) 3. How do I use the root permissions.yml? (close)

The file 'permissions.yml' in the root of your server can be used to set up custom parent permissions. Parent permissions are a single node that, when given to a player or group, automatically give all their children node. Here's a simple example:

Code:

server.basics:
    children:
        commandbook.motd: true
        commandbook.say: true
        commandbook.say.me: true
        commandbook.time: true

Now, if you give a player the node 'server.basics', they automatically get all the nodes listed here. Children may also say 'false' instead of 'true', in which case giving the parent will remove the child instead of giving it.

You can also specify a description if you like, which can be used by plugins to provide information on your node (such as PermissionsBukkit's /perm info command). If you want, you can also provide a default, which can be one of "true", "false", "op", or "notop". CraftBukkit will automatically assign everyone, no one (default), ops, or non-ops the children permissions based on the specified default. Without any plugin like PermissionsBukkit, you can use this defaults system as a limited way to assign people permissions. Here's a more complex example:

Code:

server.basics:
    description: Basic permissions for My Cool Server.
    default: true
    children:
        commandbook.motd: true
        commandbook.say: true
        commandbook.say.me: true
        commandbook.time: true
server.admin:
    description: Admin permissions for My Cool Server.
    default: op
    children:
        commandbook.broadcast: true
        commandbook.teleport: true
        commandbook.kick: true
        commandbook.ban: true

You can also define permissions without children, but this is of limited usefulness in permissions.yml (though is important in plugin.yml; see question #6)

4. How do I switch from (other Permissions plugin)? (open) 4. How do I switch from (other Permissions plugin)? (close)

Depends on the Permissions plugin! If you were using PEX's YAML backend, I have a converter done and available on the PermissionsBukkit Tools page. Also available on the tools page is an automatic converter for Essentials GroupManager users.yml and groups.yml files. Automatic converters for Permissions 2.7 and 3.x are on their way, but in the meantime you can still convert your configurations manually.

5. Where are prefixes and suffixes (or option nodes)? (open) 5. Where are prefixes and suffixes (or option nodes)? (close)

Bukkit Superperms has no built-in prefix/suffix settings or non-boolean permission nodes, so individual chat plugins will have to start supporting Superperms in order to make use of non-Permissions-plugin based prefixes and suffixes. Herochat, iChat, and Simple Suffix are all aware of the Superperms update, but in the meantime you can use mChat, which already supports Superperms.

Once you install mChat and configure the mchat.prefix, mchat.suffix, and mchat.group names in its configuration file (see the example), use PermissionsBukkit to give players or groups the permissions "mchat.prefix.admin", replacing "admin" with whatever node you configured. For example, with an mchat configuration that looks similar to this:

Code:

da-name-format: '+prefix+name&e'
date-format: HH:mm:ss
message-format: '+prefix+name&f: +message'
mchat:
    prefix:
        admin: '&4DtK [SO] &7 '
        sadmin: '&9DtK [SA] &7 '
        jadmin: '&aDtK [JA] &7  '
        member: '&cDtK [M] &7 '

You can assign players or groups the mchat.prefix.admin node to get the "SO" prefix, mchat.prefix.sadmin to get the "SA" prefix, and so on.

6. (Coders) How do I set up my plugin.yml? (open) 6. (Coders) How do I set up my plugin.yml? (close)

Take a look at this post in Dinnerbone's FAQ for an example. This is a lot like the setup of permissions.yml (see above), but you can also define non-parent permissions (just include description and default and leave out children).

7. Is PermissionsBukkit outdated? (open) 7. Is PermissionsBukkit outdated? (close)

No! PermissionsBukkit 2.0 was last updated for 1.3.1-R2.0, is verified to work on 1.4.7-R1.0, and is unlikely to break on future releases.

Downloads:
Current Version:

PermissionsBukkit v2.0 (jar) (details)
Old Versions:
PermissionsBukkit v1.6 (jar) (details)



Changelog:

Friday 7 September 2012 (2.0)

• Fixed a case-sensitivity issue with setting per-world permissions that could cause some permissions to fail to apply.
• Added /perm setrank <player> <group> subcommand (alias rank) with per-group permissions (permissions.setrank and permissions.setrank.<group>)
• Added plugin metrics via http://mcstats.org/plugin/PermissionsBukkitMCStats (disableable in plugins/PluginMetrics/config.yml)

Wednesday 29 February 2012 (1.6)

• Fixed some massive issues that were caused due to having uploaded a buggy, in-development version instead of 1.5.
• Note: If your configuration was messed up as a result of this issue, the new build should gradually correct it as needed.

Saturday 25 February 2012 (1.5b)

• Revamped to be compatible with R5.
• Fixed issues with permissions not carrying properly on world change.
• Many internal improvements for performance and stability.
• SuperpermsBridge: in honor of R5 removing deprecated code, SuperpermsBridge is officially gone!

Monday 18 July 2011 (1.1/1.2)

• Fix BukkitContrib incompatibility issues.
• Improved the output of the /perm check command.
• Fixed issues when 'users:' is not specified in the config file.
• Fixed the /permissions reload command.
• SuperpermsBridge: improve wildcard handling; in addition to 'superpermbridge.*' and 'superpermbridge.pluginname', now supported are 'superpermbridge.plugin.*', 'superpermbridge.plugin.subnode.*', and so on.

Monday 18 July 2011 (1.0/1.1)

• SuperpermsBridge: adding the special 'superpermbridge.*' and 'superpermbridge.pluginname' nodes (see #2 in the FAQ for details).

Sunday 17 July 2011 (1.0/1.0)

• Initial release of PermissionsBukkit v1.0 and SuperpermsBridge v1.0.

 

Will there be an api for your plugin? :X

 

I said normal people. At the rate we are seeing simple configuration errors on this forum, I don't expect the average of people to have any way to interface with a database, whether or not it is free/easy to use/easy to find.

 

how do you set up per world permissions. i have a creative world that i would like everyone to be able to spawn things.

 

Im pretty sure with a database layer you WONT see configuration file errors since the are not configuration files to mess up in the first place.
Is it really that hard to add database, host, username, password and let the rest be done ingame?

Sounds to me a lot easier than writing pages upon pages of config file examples and still see YAML indentation error posts every hour in the forums.

Single flat files storing 1000's of records is not an efficient way to store permissions imo. It is easy to edit table records using phpMyAdmin or Navicat/MySQL workbench. But with a good console command set this would not need to be done.

 

Never underestimate a good fool. There are people could break it even if it had no configurable options.

 

*Added to favorite quotes list*

 

McMyAdmin now supports PermissionsBukkit as of release 0.9.6.0.

 

Is this compatible with MySQL yet? I've been reading over the thread and can't figure a definite answer.

 

So im confused, i have permissions with the groups file with all my groups and their permissions and then the users file, i installed permissionsbukkit and bridge. I havent messed with the config file. I'm so confused on what to do, and my players are waiting so they can simply have access to /spawn(lolz). Thanks.

 

so you have your old group/user config from another permissions plugin and want to convert it to use it with the bukkit permissions?
if so there may already be conversion tools or you could post your old configs here but there realy isn't any big differences between old perm and the new setup.

 

No. And I don't believe there are any plans to add MySQL right now. At least, not any that I read.

Keep in mind there's no reason for it to support a database. The plugin's permission list file is only to be read once at startup and then everything is managed by the Bukkit internal system.

 

Well what if I want to remotely access the permissions, organize them, and change them during play?

 

Then the database would still do you no good. The data is only read from the hard drive at launch and written at exit. Superperms (the internal Bukkit mechanism) just uses a list of strings and changing the data store wouldn't make a bit of difference.

If you wanted to change them during play, you'd need to have a plugin that is design to be remoted in to or just log into the game.

 

In other permission plugins it was possible to assign users to a group which allowed them to apply group membership to other users (think along the lines of a moderator group promoting players up/down a given group "path").

I realise there is the /permissions player addgroup <player> <group> command but my question is how would we configure nodes to allow groups to addgroup for a specific group?

Would it be as simple as: permissions.player.addgroup.<groupname> ?

 

Then you use McMyAdmin

 

Is there any way i can intergrate this into my website? Such as promote, demote, list players.

 

I don't get it, exactly what should i have to get all permissions for admin?
'superpermbridge.*':true
'superpermbridge.*'
superpermbridge.*:true
superpermbridge.*

I tried all four at once but still dont work !
Here's my config.yml:

Code:

    users:
        Volun:
            groups:
            - admin
    groups:
        guest
            permissions:
                permissions.build: false
        member:
            permissions:
                permissions.build: true
            worlds:
                creative:
                permissions.*;true
            inheritance:
            - guest
        admin:
            permissions:
                permissions.*: true
                'superpermbridge.*':true
                'superpermbridge.*'
                superpermbridge.*:true
                superpermbridge.*
 
            inheritance:
            - member

    messages:
        build: 'You can't build yet, sign up on the forum for a member status (it's free ;D)!

 

I started to use the permissions on our server but can´t get it started. Perhaps you could tell me where to find the error!

Code:

Could not load 'plugins/PermissionsBukkit-1.1.jar' in folder 'plugins': 
while parsing a block mapping
 in "<reader>", line 29, column 1:
    users:
    ^
expected <block end>, but found BlockMappingStart
 in "<reader>", line 71, column 6:
         admin:
         ^

Code:

# PermissionsBukkit configuration file
#
# A permission node is a string like 'permissions.build', usually starting
# with the name of the plugin. Refer to a plugin's documentation for what
# permissions it cares about. Each node should be followed by true to grant
# that permission or false to revoke it, as in 'permissions.build: true'.
# Some plugins provide permission nodes that map to a group of permissions -
# for example, PermissionsBukkit has 'permissions.*', which automatically
# grants all admin permissions. You can also specify false for permissions
# of this type.
#
# Users inherit permissions from the groups they are a part of. If a user is
# not specified here, or does not have a 'groups' node, they will be in the
# group 'default'. Permissions for individual users may also be specified by
# using a 'permissions' node with a list of permission nodes, which will
# override their group permissions. World permissions may be assigned to
# users with a 'worlds:' entry.
#
# Groups can be assigned to players and all their permissions will also be
# assigned to those players. Groups can also inherit permissions from other
# groups. Like user permissions, groups may override the permissions of their
# parent group(s). Unlike users, groups do NOT automatically inherit from
# default. World permissions may be assigned to groups with a 'worlds:' entry.
#
# The cannot-build message is configurable. If it is left blank, no message
# will be displayed to the player if PermissionsBukkit prevents them from
# building, digging, or interacting with a block. Use '&' characters to
# signify color codes.
users:
baschtianxd:
  permissions:
  groups:
  - user
dealt95:
  permissions:
  groups:
  - mod
domi0535:
  permissions:
  groups:
  - user
enumine:
  permissions:
  groups:
  - user
martingoettel:
  permissions:
  groups:
  - default
senji115:
  permissions:
  groups:
  - user
thomas140185:
  permissions:
  groups:
  - mod
groups:
    default:
          permissions:
            permissions.build: false
    user:
        permissions:
            permissions.build: true
        inheritance:
        - default
mod:
         permissions:
         inheritance:
           - user
     admin:
        permissions:
            permissions.*: true
        inheritance:
        - user
        - mod
messages:
    build: '&cYou do not have permission to built here.

 

You should really add the * global permissions. And also I typed buttonwarp.* in the permissions place but still did not get permissions

 

After installing PermissionsBukkit with SuperpermsBridge, i'll get a flood of this:
[Warning] Can't keep up! Did the system time change, or is the server overloaded?
What can be wrong? Is there a way to block the Message?

Is permissionsbukkit or the bridge lagging my system?

Thanks

// EDIT

Ok, i deactivated some plugins and now it seems to work without the can't keep up msg.
Sometimes i get a error msg of a Permission Loop, but i think this is ok

 

in your groups you have:

Code:

groups:
    default:
          permissions:
            permissions.build: false
    user:
        permissions:
            permissions.build: true
        inheritance:
        - default
mod:
         permissions:
         inheritance:
           - user
     admin:
        permissions:
            permissions.*: true
        inheritance:
        - user
        - mod
messages:
    build: '&cYou do not have permission to built here.
 

but you need to move "mod:" over to the right 4 spaces, and "admin:" over to the left by 1 space, to look like:

Code:

groups:
    default:
          permissions:
            permissions.build: false
    user:
        permissions:
            permissions.build: true
        inheritance:
        - default
    mod:
         permissions:
         inheritance:
           - user
    admin:
        permissions:
            permissions.*: true
        inheritance:
        - user
        - mod
messages:
    build: '&cYou do not have permission to built here.
 

 

OK. Works better now. Thought that this is only a design thing for better reading and not important for the plugin itself

 

better get used to yml, all plugins are going that way.

 

So when setting up per-world permissions, would it look like this?

Code:

worlds:
    world:
        users:
            MattDAngeli
        groups:
            Builder
            ...
    world_nether:
        users:
            MattDAngeli
        groups:
            Builder
            ...

Etc. Because I'm KINDA confused about the added "worlds:"

 

heres a sample, removed a bunch of stuf, btu should get you going in right direction.

Code:

users:
    fffizzz:
        permissions:
            permissions.*: true
        groups:
        - admin
groups:
    default:
        permissions:
            permissions.build: false
            commandbook.spawn: true
        worlds:
            ww:
                stats.log: true
            creative:
                announcer.receiver: true
            start:
                myhome.*: false
    admin:
        permissions:
            permissions.*: true
        worlds:
            creative:
                stealthlogin.join: true
            worldrd:
                stealthlogin.join: true
            start:
                stealthlogin.join: true
            ww:
                stealthlogin.join: true
        inheritance:
        - mod

 

i transfered it all over to bukkit permissions and suddenly there were no groups even though it said i was in that group and nobody had any commands. the * node is just a lot more simpler to understand. do you think that you could do the transfer for me if i hand you my permissions 3.1.x yaml? i cant seem to figure it out

 

@CrispyDiamonds – If you wait another week or so there will probably be an automatic 3.x->PermissionsBukkit converter that you can plug your configs into.

I don't think it's currently possible.

 

Is it possible to split the "permissions.player.setgroup" into:
permissions.player.setgroup.user
permissions.player.setgroup.mod
So that Mods can just promote a player to a mod but not to admin?

 

hi when a user is kicked or banned from the server we get these errors and the server restarts:

Code:

2011-07-25 04:00:00 [INFO] ryan00793 lost connection: user was kicked.
2011-07-25 04:00:00 [SEVERE] Could not pass event PLAYER_QUIT to PermissionsBukkit
java.lang.IllegalArgumentException: Attachment cannot be null
    at org.bukkit.permissions.PermissibleBase.removeAttachment(PermissibleBase.java:134)
    at org.bukkit.craftbukkit.entity.CraftHumanEntity.removeAttachment(CraftHumanEntity.java:104)
    at com.platymuus.bukkit.permissions.PermissionsPlugin.unregisterPlayer(PermissionsPlugin.java:137)
    at com.platymuus.bukkit.permissions.PlayerListener.onPlayerQuit(PlayerListener.java:24)
    at org.bukkit.plugin.java.JavaPluginLoader$2.execute(JavaPluginLoader.java:251)
    at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
    at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:332)
    at net.minecraft.server.ServerConfigurationManager.disconnect(ServerConfigurationManager.java:146)
    at net.minecraft.server.NetServerHandler.disconnect(NetServerHandler.java:117)
    at org.bukkit.craftbukkit.entity.CraftPlayer.kickPlayer(CraftPlayer.java:135)
    at com.mcmyadmin.bukkitcompat.ConsoleCommandHandler.onCommand(ConsoleCommandHandler.java:108)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:35)
    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:129)
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:312)
    at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:480)
    at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:465)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:361)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
2011-07-25 04:00:00 [INFO] Unknown console command. Type "help" for help.
2011-07-25 04:00:00 [INFO] [CONSOLE] Server shutting down immediately. World is being saved. Server restarting to rotate log file.

Edit: the plugins we have installed are:

Code:

AntiCreeper, BigBrother, BorderGuard, Essentials, EssentialsGeoIP, EssentialsProtect, EssentialsSpawn, EssentialsXMPP, FalseBookBlock, FalseBookCart, FalseBookCore, FalseBookExtra, FalseBookIC, HeroicDeath, iConomy, iConomyChestShop, mChat, BukkitCompat, PerformanceTweaks, PermissionsBukkit, Permissions, VanishNoPickup, WorldEdit, LWC

 

Where are the config files... they didn't auto create D: