Bukkit

Pastebin link to your Config (I will ignore your ticket if it doesn't contain this:

What steps will reproduce the problem?
1. Rebooting the server
2.
3.

What is the expected output? What do you see instead?
expecting plugin to be enabled as before

What version of the product are you using?
2.9.3

Do you have an error log of what happened?
yes, will place below

Please provide any additional information below.

29.07 11:35:19 [Server] INFO at java.lang.Thread.run(Thread.java:745) [?:1.8.0_66]
29.07 11:35:19 [Server] INFO at net.minecraft.server.v1_9_R2.MinecraftServer.run(MinecraftServer.java:532) [custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO at net.minecraft.server.v1_9_R2.DedicatedServer.init(DedicatedServer.java:200) [custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO at org.bukkit.craftbukkit.v1_9_R2.CraftServer.loadPlugins(CraftServer.java:297) [custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:219) [custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO org.bukkit.plugin.UnknownDependencyException: ClearLag
29.07 11:35:19 [Server] ERROR Could not load 'plugins/KeepDeathDrop.jar' in folder 'plugins'
29.07 11:35:19 [Server] INFO Set PluginClassLoader as parallel capable
29.07 11:35:19 [Server] INFO ... 5 more
29.07 11:35:19 [Server] INFO at org.bukkit.plugin.java.JavaPluginLoader.getPluginDescription(JavaPluginLoader.java:150) ~[custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO at java.util.jar.JarFile.<init>(JarFile.java:130) ~[?:1.8.0_66]
29.07 11:35:19 [Server] INFO at java.util.jar.JarFile.<init>(JarFile.java:166) ~[?:1.8.0_66]
29.07 11:35:19 [Server] INFO at java.util.zip.ZipFile.<init>(ZipFile.java:149) ~[?:1.8.0_66]
29.07 11:35:19 [Server] INFO at java.util.zip.ZipFile.<init>(ZipFile.java:219) ~[?:1.8.0_66]
29.07 11:35:19 [Server] INFO at java.util.zip.ZipFile.open(Native Method) ~[?:1.8.0_66]
29.07 11:35:19 [Server] INFO Caused by: java.util.zip.ZipException: error in opening zip file
29.07 11:35:19 [Server] INFO at java.lang.Thread.run(Thread.java:745) [?:1.8.0_66]
29.07 11:35:19 [Server] INFO at net.minecraft.server.v1_9_R2.MinecraftServer.run(MinecraftServer.java:532) [custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO at net.minecraft.server.v1_9_R2.DedicatedServer.init(DedicatedServer.java:200) [custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO at org.bukkit.craftbukkit.v1_9_R2.CraftServer.loadPlugins(CraftServer.java:297) [custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:133) [custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO at org.bukkit.plugin.java.JavaPluginLoader.getPluginDescription(JavaPluginLoader.java:162) ~[custom18.jar:git-Spigot-798f32d-0cd0397]
29.07 11:35:19 [Server] INFO org.bukkit.plugin.InvalidDescriptionException: Invalid plugin.yml
29.07 11:35:19 [Server] ERROR Could not load 'plugins/Clearlag.jar' in folder 'plugins'

29.07 11:35:19 [Server] INFO org.bukkit.plugin.UnknownDependencyException ClearLag 29.07 11:35:19 [Server] ERROR Could not load 'plugins/KeepDeathDrop.jar' in folder 'plugins'

You don't have Clearlag installed.

@bob7l: Go

I understand that the deathdrops error is because clearlag.jar didn't load, but that is where the problem was.

When the latest clearlag.jar was pushed on update, it wouldn't load. We manually replaced it with the 1.9 version from the files page and now it is working. Could it have pushed the 1.1 or 1.8 version of the 2.9.3 update because our spigot jar has a custom name?

29.07 11:35:19 [Server] INFO org.bukkit.plugin.InvalidDescriptionException Invalid plugin.yml 29.07 11:35:19 [Server] ERROR Could not load 'plugins/Clearlag.jar' in folder 'plugins'

BTW, we're on Spigot 1.9.4 but rename the jar file to Custom18.jar because that tells our host to run java 8 (I have no idea why they do it that way).

@flapjack1968: Go

The update error was due to Curse API randomly altering the downloads without updating the JSON download links returned by the API. So when an update was detected, clearlag would follow the link provided by the API. This time however, it returned a HTML_PAGE_MOVED error resulting in the download being of the HTML page rather then the Clearlag JAR. This was a sudden and terrible move by Curse's API developers and i have no idea why they thought it'd be a good idea.

If you open the "update" clearlag jar with notepad, you'll see what I'm talking about.

The good news is I've included some HTML header readers within the newest Clearlag release (2.9.3) that'll follow the MOVED URL.

Awesome. Crisis averted. Thanks for the quick responses. I know it can't be easy to keep up with plugin support (especially with Curse adding to the list).