search

PluginBugs / Issues-ServerBooster

Repository used to keep track of issues of my plugin ServerBooster
2 stars 0 forks source link

[BUG] #30

Closed thboehi closed 4 years ago

thboehi commented 4 years ago

Describe the bug

I bought the plugin and tested it on a cloned server. After finishing to configure it, I added it on the main server, but get this error when loaded:

>....=>.... [10:39:45 WARN]: Unexpected exception while parsing console command "serverbooster"
org.bukkit.command.CommandException: Cannot execute command 'serverbooster' in plugin ServerBooster v1.0.46 - plugin is disabled.
at org.bukkit.command.PluginCommand.execute(PluginCommand.java:37) ~[patched_1.16.3.jar:git-Paper-244]
at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:159) ~[patched_1.16.3.jar:git-Paper-244]
at org.bukkit.craftbukkit.v1_16_R2.CraftServer.dispatchCommand(CraftServer.java:802) ~[patched_1.16.3.jar:git-Paper-244]
at org.bukkit.craftbukkit.v1_16_R2.CraftServer.dispatchServerCommand(CraftServer.java:764) ~[patched_1.16.3.jar:git-Paper-244]
at net.minecraft.server.v1_16_R2.DedicatedServer.handleCommandQueue(DedicatedServer.java:405) ~[patched_1.16.3.jar:git-Paper-244]
at net.minecraft.server.v1_16_R2.DedicatedServer.b(DedicatedServer.java:372) ~[patched_1.16.3.jar:git-Paper-244]
at net.minecraft.server.v1_16_R2.MinecraftServer.a(MinecraftServer.java:1211) ~[patched_1.16.3.jar:git-Paper-244]
at net.minecraft.server.v1_16_R2.MinecraftServer.w(MinecraftServer.java:999) ~[patched_1.16.3.jar:git-Paper-244]
at net.minecraft.server.v1_16_R2.MinecraftServer.lambda$a$0(MinecraftServer.java:177) ~[patched_1.16.3.jar:git-Paper-244]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_262]

To Reproduce Steps to reproduce the behavior:

  1. Insert the plugin on a test server
  2. Config it
  3. Transfer the plugin and the files on the main server and the LoneLib.jar.
  4. Launch server.

Info (please complete the following information):

thboehi commented 4 years ago

I had to delete folder and configure it again...

LoneDev6 commented 4 years ago

A full log would have been better as the plugin disabled itself because of a problem which I can't see in this log. This error just tells me that the plugin got disabled.

Anyway I'm happy you fixed :D