InventivetalentDev / MapManager

MIT License
54 stars 20 forks source link

Spigot 1.8.8 Startup Error #30

Closed w1nst0nDEV closed 5 years ago

w1nst0nDEV commented 5 years ago

When does this error occur? Startup of Spigot 1.8.8, latest version.

What effects does it have? It completely disables the plugin.

What's the error? The error can be viewed on this pastebin.

Do you have all dependencies installed? Yes. I have PacketListenerAPI installed.

Th3Shadowbroker commented 5 years ago

Hi @w1nst0nDEV, which version of PacketListenerAPI are you using?

w1nst0nDEV commented 5 years ago

https://github.com/InventivetalentDev/MapManager/issues/30#issuecomment-473525235

I am using 3.7.1_SNAPSHOT. Am I supposed to use a different version?

Th3Shadowbroker commented 5 years ago

I were able to reproduce and solve the described problem. I've used spigot 1.8.8-R0.1-SNAPSHOT and PacketListenerAPI 3.7.1_SNAPSHOT combined with the MapManager v1.7.2-SNAPSHOT as you described and the same error occurred. However I were able to solve it in the end by replacing the PacketListenerAPI v3.7.1_SNAPSHOT with 3.7.2-SNAPSHOT. 3.7.2-SNAPSHOT is not available on spigot at the moment, so I will attach it to my comment.

PacketListenerAPI_v3.7.2-SNAPSHOT.zip

Let me know if this solved your problem or if it still persists (for whatever reason). 😄

EDIT: So in the end, this is a duplicate of #29

w1nst0nDEV commented 5 years ago

I were able to reproduce and solve the described problem. I've used spigot 1.8.8-R0.1-SNAPSHOT and PacketListenerAPI 3.7.1_SNAPSHOT combined with the MapManager v1.7.2-SNAPSHOT as you described and the same error occurred. However I were able to solve it in the end by replacing the PacketListenerAPI v3.7.1_SNAPSHOT with 3.7.2-SNAPSHOT. 3.7.2-SNAPSHOT is not available on spigot at the moment, so I will attach it to my comment.

PacketListenerAPI_v3.7.2-SNAPSHOT.zip

Let me know if this solved your problem or if it still persists (for whatever reason). 😄

EDIT: So in the end, this is a duplicate of #29

Works perfectly! I'll look at closed issues if I encounter any type of error again from now on! (If it's no where to be found, I'll submit a new issue!)