Skip to content
This repository has been archived by the owner on Jun 19, 2021. It is now read-only.

Cloning chests leads to "Chestban" #370

Open
Archie-osu opened this issue Jan 27, 2021 · 3 comments
Open

Cloning chests leads to "Chestban" #370

Archie-osu opened this issue Jan 27, 2021 · 3 comments
Labels
low priority ticket is of low priority vanilla issue is present in vanilla

Comments

@Archie-osu
Copy link

Expected behavior
I can have whatever I want in my inventory without getting kicked / "banned".

Observed behavior
I get kicked after cloning (Ctrl + Middle Click in Creative Mode) a Chest with 3 shulkers of ban books (books filled up with random characters on all 50 pages). After getting kicked, you cannot join back unless an Admin wipes your inventory, hence me calling it a "ban".

Steps to reproduce (if known)

  1. Get ForgeHax and ViaForge (I used the 1.12.2 version to write these)
  2. Download the randombook.txt file (Click here)
  3. Set up BookBot
  4. Follow this video (Click here)

Installed plugins
None.

> plugins
[18:11:45 INFO]: Plugins (0): 

Version
Latest Yatopia 1.16.5 (non-staging)

> version
[18:11:47 INFO]: This server is running Yatopia version git-Yatopia-17 (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT)
[18:11:47 INFO]: Previous version: git-Yatopia-14 (MC: 1.16.5)
[18:11:47 INFO]: ¯\_(ツ)_/¯

Additional context
This doesn't only happen with books, it happens with any items with NBT (player heads, enchanted items, etc.) - it just needs more shulkers. Books seem to be the most effective. I also tried using Droppers to drop three separate shulkers of these ban books to the player (at once), yet the player doesn't get kicked that way.

@Titaniumtown
Copy link
Collaborator

Can you reproduce this upstream? I think this happens in vanilla too.

@Archie-osu
Copy link
Author

Archie-osu commented Jan 27, 2021

Can you reproduce this upstream? I think this happens in vanilla too.

Yeah, it happens with Vanilla too, but with a different error:
Internal Exception: io.netty.handler.codec.DecoderException: Badly compressed packet - size of 2254248 is larger than protocol maximum of 2097152

@Titaniumtown
Copy link
Collaborator

So this is a vanilla issue then. But would be interesting to implement a fix for this.
@duplexsystem thoughts?

@Titaniumtown Titaniumtown added low priority ticket is of low priority vanilla issue is present in vanilla labels Jan 27, 2021
@Titaniumtown Titaniumtown changed the title [Problematic] Cloning chests leads to "Chestban" Cloning chests leads to "Chestban" Apr 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
low priority ticket is of low priority vanilla issue is present in vanilla
Projects
None yet
Development

No branches or pull requests

2 participants