CraftBook 3

CraftBook 3

139k Downloads

Latest ProtocolLib breaks chairs and Craftbook.

crumpkatrina opened this issue ยท 3 comments

commented

CraftBook Version

3.10.6 Build 4739

Platform Version

Paper 1.17.1 Build 409

Confirmations

  • I am using the most recent Minecraft release.
  • I am using a version of WorldEdit compatible with my Minecraft version.
  • I am using a version of CraftBook compatible with my Minecraft version.
  • I am using the latest or recommended version of my platform software.
  • I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
  • I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)

Bug Description

Latest commits:
dmulloy2/ProtocolLib@073bfa2
dmulloy2/ProtocolLib@0d4e4c8
dmulloy2/ProtocolLib@d361526

Have broken CraftBook.
It will not load, states Chairs requires ProtocolLib, and instead shoots the following errors continously:
https://pastebin.com/raw/ZAsynKKh

Rolling back to:
dmulloy2/ProtocolLib@f0059f3

Fixes all issues.

Expected Behavior

Craftbook to function.

Reproduction Steps

  1. Use latest ProtocolLib dev builds with above CraftBook version.

Anything Else?

No response

commented

You're missing the initial part of the error that actually shows what went wrong

It doesn't seem there was any intention for ProtocolLib to have breaking changes in those 3 commits, so it's most likely this is a bug in ProtocolLib - from the looks of it you're using dev builds of it, so it's likely due to that

commented

Yes, I am using development builds of Protocollib.
There is nothing else earlier regarding errors, this is all that is shown.

commented

It seems ProtocolLib dev builds are currently working towards a new major release. For us to support those would mean we'd lose support for the released versions. Don't use ProtocolLib 5 if you're wanting plugins that use ProtocolLib 4 to work. Once ProtocolLib 5 is the released version we can update to that, but breaking the plugin for everyone using the releases is not something we can do.