[SEC] Lockette - Simple chest and door lock, no databases! [Moved to BukkitDev]

Discussion in 'Inactive/Unsupported Plugins' started by Acru, Feb 14, 2011.

  1. Offline

    Acru

    Lockette - The sign-based container and door lock for Bukkit! - by Acru Jovian

    ElgarL has been assigned as the current maintainer of this project, please forward any important issues to him as well. This post is abandoned, but proceed to BukkitDev for updates.

    Download it at BukkitDev! (Alternate) (JAR) (Source), also view the Change Log on BukkitDev.



    Supported external plugins:
    • Permissions - Permissions/Groups
    • GroupManager - Permissions/Groups
    • PermissionsBukkit - SuperPerms/Groups
    • PermissionsEx - SuperPerms/Groups
    • bPermissions- SuperPerms/Groups
    • Towny - Groups/Zones
    • SimpleClans - Groups
    • mcMMO - Groups (Disabled by default now, due to issues.)
    • Factions - Groups
    • LWC - Zones
    • Register - Economy
    Alternate languages included:
    Confirmed compatible plugins: ColorSign, SpeedSign.
    Conflicting plugins: ChestShop, Most sign editors!


    The active Lockette information page will commute to BukkitDev soon, but the forum thread is still the best place for discussion.



    Overview:

    The purpose of this plugin is to restrict access to the contents of chests, dispensers, furnaces, and doors without the use of a database to track containers.

    To use, simply place a signpost on the floor directly beside a chest or other container to be locked. Enter [Private] as the first line. Your own name will automatically be entered on line 2 as the chest owner. Optionally type in the full names of two other users allowed to access the chest's inventory on lines 3 and 4.

    When done correctly, the sign will automatically fix itself to the side the target chest, protecting it from unauthorized access! Only the chest's owner can then break the sign or chest. (Warning: Anyone with permission to use WorldEdit commands or similar can circumvent the protection by removing the sign.)

    [​IMG]

    Additionally, you can enter [Everyone] on lines 3 or 4 instead of a user name to allow everyone access to the contents of a private container, or [Operators] to allow ops access. If a Permissions plugin is available, you can use groups like [Moderator] or [Admins] or others as defined in the Permissions settings files.

    The owner of a container can add more users by placing additional signs beside the container with the heading [More Users], where lines 2-4 specify the names of the additional users. You can edit the users on previously placed signs by right clicking the sign, and using the command '/lockette <line number> <text>' to change it.


    Working with Doors:

    To protect a door, you can use the same method as protecting a container, the sign will attach to the door automatically. In addition, you can attach a [Private] wall sign to any side of the blocks just above or just below a door. For double doors only one side needs a sign. Door support is enabled by default in the config file.

    Once a door is protected it will only open for someone listed as a user, and will not respond to redstone power or switches unless [Everyone] is listed as a user. Iron doors which usually won't open from clicking will work just as wooden doors. In addition, double doors will open together automatically!

    You can also use [More Users] signs as with containers, with the caveat that the sign cannot be placed on the block above the door if the [Private] sign is not above the door as well! (This is done to prevent a security uncertainty issue.)

    Protected doors will be closed automatically if a timer is set. A timer can be set globally with a configuration option, or individually for each door by using the tag [Timer: #] on line 3 or 4 of the [Private] sign, where # is the number of seconds that the door should remain open. If the timer is set to 0, this means the door will never automatically close. If no timer is specified, protected doors will use a global timer set in the configuration file. If the server is shut down cleanly any open doors will be closed, but in the event of a server crash while a door is open, it may remain so. Note that the initial state of a door is assumed to be closed.

    Care must me taken to place protected doors on a stable block. Building a door on sand, gravel, leaves, TNT and et cetera are allowed by the plugin, but cannot be secured fully. :3 Additionally, it should be noted that most status messages still refer to locked blocks as containers, so for the purpose of simplicity, doors should be considered as a type of container.


    Features:
    • No passwords or databases needed!
    • Permission checks run in constant time, no matter how many protected containers.
      • One owner and up to 11 additional users supported. (17 for double chests!)
      • Allows access to [Everyone] while still protecting the container from vandalism.
      • Allows group names in conjunction with many other plugins.
    • Special powers for ops or admins, configurable with permissions.
      • Reports when an admin does something naughty.
    • Protects single and double chests, dispensers, and furnaces.
      • Explosion and block-break protection for the protected container and sign.
        • Option to protect all containers from explosions.
    • Full support for doors, both wooden and iron!
      • Double doors are handled automatically, with no redstone.
      • Doors can be set to close automatically, via a timer setting.
      • Redstone hacking is disabled for protected doors.
    • Prevents creation of chests larger than 2 blocks.
    • Informative or helpful messages when interacting with containers.
      • The first time a chest is placed, a help message will be shown.
      • Types of messages shown are configurable in settings.
      • Additional language support.

    Advanced Setup (Permissions) (open)

    Advanced Setup:
    There are a few things you can now customize in the configuration files for the plugin, found in the plugins/Lockette folder. After running the plugin for the first time, two files will be created, config.yml and strings.yml. The first holds the following settings:
    • enable-permissions - Allows the use of permission nodes to specify who can do what. If this is disabled, groups will still be used but admin status is taken from the ops file. Defaults to false.
    • enable-messages-* - Enables or disables groups of messages listed in the strings.yml file. Not counting the broadcast ones.
    • broadcast-*-target - Sets the group or player that specific broadcast messages should be sent to. This can be set to "" for no one.
    • explosion-protection-all - Enabling this extends explosion protection to all containers on the server, not just [Private] ones. Default is disabled.
    • allow-admin-bypass - Allows admins to go though any protected door. Default is true.
    • allow-admin-snoop - Allows admins to peek into chests owned by other people. Default is false, and this setting is recommended! A broadcast message will be sent each time an admin snoops in a protected container where the admin doesn't have permission to. The message will be sent to a player or group as specified in another option. Admins can still break protection on chests if this is disabled, however.
    • enable-protection-doors - Enables support for private doors, defaults to true.
    • default-door-timer - Sets the door closing timer for all protected doors on the server, unless overridden by a specific sign. Defaults to 0, which disables the door closing timer.
    In the strings.yml file, you can set alternate language tags for [Private] and such, in ANSI format. If you need characters not in ANSI then you might try UTF-8 format, though it seems bugged tight now. The default alternate tags are in French, but server ops are free to translate the whole file into the language of their choice. If you do this, please share it back to me~ :3 If you want to disable only a specific message, you can set it to "", the empty string. Admins can use the command '/lockette reload' after editing the configuration files, to reload them.

    If a Permissions plugin is not available or the enable-permissions option is set to false, Lockette will use the ops file to determine who are admins. Admins can break the protection on any chest, and look inside protected chests (only if the related option is set), as well as reload the plugins configuration files. All non-ops will be able to create protected containers for themselves.

    If a Permissions plugin is available and the enable-permissions option is set to true, the following nodes will be used instead of the ops file and are included by default in the '*' node:
    • lockette.user.create.* - Permission required to create a protected container or door. Possible sub-nodes include chest, dispenser, furnace, and door. (The permission lockette.create.all is still supported, but obsolete.)
    • lockette.admin.create.* - Allows admins to create containers and doors for other users. Possible sub-nodes include chest, dispenser, furnace, and door. Leave line 2 blank for the default behavior or enter the name of your choice. Capitalization matters.
    • lockette.admin.break - Allows breaking protection on containers.
    • lockette.admin.bypass - Allows opening of any locked door.
    • lockette.admin.snoop - Allows peeking in protected containers. (The setting allow-admin-snoop must be true.)
    • lockette.admin.reload - Allows use of the reload command.

    Technical Information (open)

    Technical Information:

    This plugin has been tested and shown to be working for many builds of CraftBucket though a number of the more recent builds had a serious issue, so I'm suggesting a minimum build of 561 now. If you update past what is listed in the post's title and the plugin seems to break, it is probably not my fault. Post a note anyway and I'll see about fixing. I'll try and keep up with the new recommended build system, but for latest builds that break things, you should expect some time to pass before I take care of the issue, as this plugin is now mature. :3

    If there are multiple containers by the placed sign, the plugin will use the NESW rule to choose the first container that is not yet private. To elaborate, the plugin will check to the north of the sign first, and if no container or door is available to the north, it will continue checking clockwise around the sign.

    Due to the current implementation of the explosion event, this plugin will cancel all explosions that would damage the container or sign, rather than just remove the container and sign from the blocks to be damaged. Canceled explosions still knock signs off the walls. Canceled explosions leave signs looking blank, but this is just a graphic glitch, reconnect to fix.

    Bonus: This plugin will prevent chests bigger than 2 blocks from being created via glitches. (Again, this could be circumvented using WorldEdit commands, so take care who has access to such a plugin.)

    This plugin was inspired by the old hmod plugins Lock by Roman "kingseta" Pramberger and ChestCapsule by Fernando "Fergo".

    Hooking into Lockette (open)

    Hooking into Lockette:

    If you are a plugin author and want to connect to Lockette, you can use a public static function to get information about the protected status of a block.

    More info later, perhaps, but if you need the details now then go poke through the source~

    Future Possibilities:

    There are a number of things that have been suggested, and they tend to be added to the list below if I think they might be a good idea. However, some sort of locked container limit is requested often but this is not possible without a database to track the number of locked containers someone has. All things considered, this will not be supported. On the up side, without a database you can have literally millions of locked containers without any sort of lag, and there are permissions to restrict who can create locked chests. Perhaps only allow Moderators to create locked chests for other users, if you don't want to allow infinite locked chests.

    Aside what has already been implemented, the following may or may not appear in future versions:
    • Furnace/dispenser clusters, protected by a single sign.
    • [Log] sign to list recent users of a container or door.
    • iConomy fee for protecting containers/doors.
    • Worldguard connection.
    • [Protected] tag for viewing only.
    • Specific time range that doors can be opened.
    • DataLog plugin support.
    • More types of protected blocks, such as brewing stands.
    If you want any of the above features sooner than never, let me know! However, I currently see Lockette as functionally complete, for the most part, in that it already has all the functionality it needs. Future updates will mostly be to account for changes in Minecraft and Bukkit.


    Final Note:

    Please leave a reply if there are any bugs or suggestions, and if you like this plugin you can click the like button at the bottom of this post~ Thanks to those few that have donated! [​IMG]
     
  2. Offline

    1hacker

    I think you should change return true; to continue; in BlockListener.java -> private boolean onChestPlace(Player player, Block block) -> Line 121
    Code:
                if (owner.equals("") || owner.equals(Util.truncate(player.getName())))
                    continue;
    
     
  3. Has someone taken this plugin on as there own yet :/?
     
  4. Offline

    daemitus

    Typically, if theres more than 1 chest adjacent to an empty block, default minecraft will disable it due to it being a triple chest. I see your point though. 3 extra iterations never hurt anyone.

    The one ive been working on is pretty much done. Just need to make sure that everything works exactly as specified.
     
  5. Offline

    Hopium

  6. Awesome, ill take a look.
    Edit: Is it finished :D?
     
  7. Offline

    daemitus

    https://github.com/daemitus/Lockette/blob/master/dist/Lockette.jar?raw=true
    For functionality, should be. At this point we're just bug hunting and looking for possible features.
    FYI, [Group] functionality is not in atm. Im working on a bridging type of system where you can register any plugin with an isAuthorized(name, names) return boolean function. This way, I can get my [TownyTownName], [TownyNationName], and [PermissionsGroup] names on signs.
     
    Rockstar04 likes this.
  8. Ok my friend, i shall try it now for you and report back.
    Will it load the current Lockette signs that are already in place?

    Edit: Awesome! It works fine, good job! Thanks alot for helping us all!

    [diamond][diamond][diamond][cookedmeat][cake]
     
  9. Offline

    daemitus

    Sign syntax hasnt changed. Ive tried to keep everything the same as it was in the original.
    The only difference in protected blocks should be the following:
    Protected doors expand their protection to the block below AND above.
    Protected trapdoors protect the block that they are attached to. Sign can go on either the hingeblock, or the trapdoor itself.

    If anything doesnt work as advertised, drop me an issue on github, here, or in a pm.
     
  10. Offline

    iKickHobbits

    daemitus (or other developer), I'm playing on a server in which sometimes lockette works perfect. Others, it doesnt. Sometimes the doors to my home work, and then I'll log in the next day and they wont. I'll break the doors/sign and try again and it just goes "[?]" However, other doors that I have set work.

    Not sure why this is. I'm not the owner of the server so I cant tell you the configs but I do know that nothing is being changed/modified. Any insight as to why sometimes this [?] occurs and then suddenly works again?
     
  11. Offline

    didzym

  12. Offline

    daemitus

    I have all sorts of different strings and such.
    Initially it should download an english.yml from github for usage.
    You can specify in config.yml under language: if you want to use something else.
    This way, if someone decides to send me a french.yml, you can change that in the config and it would pull it down.
    Alternatively, modify the file yourself. It only downloads if nothing is there.

    Strings.yml is not used regardless.


    Best guess, chunks are bugging out and not loading one one end or the other. No idea other than that. Both versions only iterate the nearby blocks for valid matches, nothing is stored. If its not detecting the doors due to the chunk being wonky, that might do it.
     
  13. Offline

    brnr72

    Things are a mess all around right now. ARGH! Please make this work with PermissionsBukkit.
     
  14. Offline

    daemitus

    It does. Im not touching Permissions 2.x or 3.x at all

    Working on a bridge to get [GroupName] functionality on signs atm.
    Already have one for Towny [TownName] or [NationName]

    Only 11pm and nothing else to work on? Things are wrapping up quickly.
    Framework for hooking bridges to your favorite plugin is complete.

    Take for example the Towny one I just finished (some extraneous code is removed for clarity).
    Code:
    public class LocketteTownyBridge extends JavaPlugin implements LocketteBridge {
    
        public static final Logger logger = Logger.getLogger("Minecraft");
        private static final String patternBracketTooLong = "\\[.{14,}\\]";
        private Towny towny;
    
        public void onDisable() {
        }
    
        public void onEnable() {
            towny = (Towny) this.getServer().getPluginManager().getPlugin("Towny");
            Lockette.registerBridge(this);
        }
    
        public boolean isAuthorized(Player player, List<String> names) {
            try {
                Resident resident = towny.getTownyUniverse().getResident(player.getName());
                Town town = resident.getTown();
                if (names.contains(truncate("[" + town.getName() + "]").toLowerCase()))
                    return true;
                Nation nation = town.getNation();
                if (names.contains(truncate("[" + nation.getName() + "]").toLowerCase()))
                    return true;
            } catch (NotRegisteredException ex) {
            }
            return false;
        }
    
        private String truncate(String text) {
            if (text.matches(patternBracketTooLong))
                return "[" + text.substring(1, 14) + "]";
            return text;
        }
    }
    
    Whenever you try to open a door/chest/whatever, itll check if your name is on the sign itself. then if [everyone] is on it, failing that, will goto each bridge that has been registered. In this case, itll reflect the isAuthorized and call it from inside Lockette.

    I have another for PermissionsBukkit, checking for [SomeGroupName].
    Also recursively checks any groups that inherit from it, just like the original functionality.
    So (Admin) inherits (User) inherits (Default), a sign with [Default] would let all 3 groups use it.

    Any requests for some random permissions system or other plugin(factions?) in use on your server? Until you give me some bug or other task to work on, I may as well just start banging out a new post and release this sucker.

    PEX Current features

    1. Bukkit Permissions (SuperPerms) compatible.
    Already taken care of by them.


    Ah ha, touche sir. On it

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 18, 2016
  15. Offline

    Inscrutable

    Oh yeah. Thanks daemitus, I really appreciate the attention to detail! .And Trapdoors, FTW!
    Hopefully it will cope properly with PEX users in multiple groups (and related inheritances).
    Are you going to take over this thread, or Fork It?
     
  16. Offline

    daemitus

    Ill probably just fork the thread, incase Acru ever shows his head again and decides to do something with it. (ill probably end up copying most of the first post anyways).

    PEX Bridge is done. [GroupName] all day every day. The methods they use seemed a little counterintuitive, but I got it working. Im not entirely sure how that ranking system works, even after reading the wiki, but unless you specifically inherit a group, or its subgroups, you wont have access to a sign with it.
     
  17. Offline

    Inscrutable

    @daemitus You Rock, Sir! ... so, any link to a DL so I (we!) can give it a road-test? Or should I await your Fork?
    (Impatiently champing at the bit.) -- Regards, Inscrutable
     
  18. Offline

    daemitus

    Everything is on github
    https://github.com/daemitus
    Find the one youre looking for, head to the /dist folder, click the .jar, then mash 'view raw' and itll download.

    https://github.com/daemitus/Lockett...t/zzzLockettePermissionsExBridge.jar?raw=true
    https://github.com/daemitus/Lockett...zLockettePermissionsBukkitBridge.jar?raw=true
    https://github.com/daemitus/LocketteTownyBridge/blob/master/dist/zzzLocketteTownyBridge.jar?raw=true
    https://github.com/daemitus/Lockette/blob/master/dist/Lockette.jar?raw=true

    Ill also give a shoutout for BetterFurnaces.
    Hold smeltable item, left click furnace, poof, its in the smeltable spot.
    Hold fuel item, left click furnace, poof, its in the fuel spot.
    Hold neither of the above, left click furnace, whatever's ready drops to the ground.
    https://github.com/daemitus/BetterFurnaces/blob/master/dist/BetterFurnaces.jar?raw=true
     
  19. Offline

    1hacker

    Are you using Spout? I have had similar problems which I think was Spout related. Haven't had that bug in the latest Spout updates.
    It could also be another plugin interfering.

    Yes, you are right, minecraft already takes care of that :p

    I can place a protected chest on top of another players protected chest, and then the other player can't open his chest.

    I was thinking, it would be great if a protected chest could be opened by e.g. sneak + right clicking the sign. Then it would be possible to place protected chests in walls and still be able to access them + it would not matter if someone places a chest on top of yours.

    Or, maybe better, if it is possible to always be able to open chests by right clicking them, even if there is a block on top of them.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 18, 2016
  20. Offline

    R4Z0R49

    daemitus,
    Nice job taking this on wonder if you can add support for SimpleClans which would also give your LocketteXL(new name idea) a bridge into PreciousStones.

    Having both of these linked would give a much better native feel to the servers much more then using groups within permission systems alot like you have done with towny another good idea btw. But we use a more free build system where simpleclans fits better.

    Anyhow nice job looking forward to this release.
     
  21. Offline

    daemitus

  22. Offline

    R4Z0R49

    Hello daemitus,

    Sorry my wording isnt very good. SimpleClans is allready linked to PreciousStones meaning we can now allow clans within fields from PreciousStones. If you also bridge Lockette into Simpleclans we gain both access to Clan fields and clan chests/doors/furnace/traps. Giving an overall feel everything is linked. I didn meant to directly link lockette and PreciousStones.

    Sorry for the misunderstanding.
     
  23. Offline

    didzym

    Thanks, but I have a problem of character. And it is really a problem because the chests use [privé].

    Error:[SEVERE] Error occurred while enabling Lockette v1.0 (Is it up to date?): special characters are not allowed
     
  24. Offline

    daemitus

    Intresting. ill see what i can do

    Its an issue with .yml files being saved in ANSI, which is the default, when they SHOULD be saved in UTF-8. I found an old essentials help file that explains it.

    # If you want to use special characters in this document, such as accented letters, you MUST save the file as UTF-8, not ANSI.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 18, 2016
  25. Offline

    didzym

    Thank you it work now.
     
  26. i'm the owner of the server in groupmaneger i am admin so i can do every command but if i try to open a chest from somebody else with sign on it i can't see what's in it how can i fix that?
     
  27. Offline

    Frogging101

    Aww. This is [INACTIVE] now? I loved this plugin :(
     
  28. Offline

    daemitus

    Not for long.
     
  29. Offline

    slater96

    Are you taking over development for it?
     
  30. Offline

    daemitus

    Ive pretty much redone the entire thing. Read the past couple days worth of posts.
     
  31. Offline

    Inscrutable

    OK, @daemitus, I gave your new version of Lockette a spin. (MC1.7_3, RB#1060, PermissionsEx 1.13, with your pEx bridge)
    I let the new Lockette make its own config file, and removed the old version.
    I got errors on startup with ChestShop (3.02) and Cenotaph
    (1.66). This is a great pity, as it's kinda essential for Cenotaph.

    Heres hoping its an easy fix (or a stupid mistake on my part):

    Code:
    2011-08-31 09:21:27 [SEVERE] Could not pass event PLUGIN_ENABLE to ChestShop
    java.lang.NoClassDefFoundError: org/yi/acru/bukkit/Lockette/Lockette
        at com.Acrobot.ChestShop.Listeners.pluginEnable.initializePlugin(pluginEnable.java:72)
        at com.Acrobot.ChestShop.Listeners.pluginEnable.onPluginEnable(pluginEnable.java:54)
        at org.bukkit.plugin.java.JavaPluginLoader$44.execute(JavaPluginLoader.java:548)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:338)
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:892)
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:278)
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:178)
        at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:161)
        at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:286)
        at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:273)
        at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:149)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:337)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    Caused by: java.lang.ClassNotFoundException: org.yi.acru.bukkit.Lockette.Lockette
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:36)
        at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:24)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        ... 14 more
    
    Code:
    2011-08-31 09:21:29 [INFO] [Cenotaph] Using Lockette (v1.0)
    2011-08-31 09:21:29 [SEVERE] Could not pass event PLUGIN_ENABLE to Cenotaph
    java.lang.NoClassDefFoundError: org/yi/acru/bukkit/Lockette/Lockette
        at com.MoofIT.Minecraft.Cenotaph.Cenotaph$sListener.onPluginEnable(Cenotaph.java:1476)
        at org.bukkit.plugin.java.JavaPluginLoader$44.execute(JavaPluginLoader.java:548)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:338)
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:892)
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:278)
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:178)
        at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:161)
        at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:286)
        at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:273)
        at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:149)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:337)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    Caused by: java.lang.ClassNotFoundException: org.yi.acru.bukkit.Lockette.Lockette
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:36)
        at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:24)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        ... 13 more
    
     

Share This Page