Large amounts of sendBlockChange kick player?

I was just trying out a proof of concept for something that was suggested on the plugin request forums. However, every time I use it I get kicked and I'm not sure why.

Brief description: Upon command, the chunk a player is in and the adjacent chunks are sent as glass in a xray-like manner.

Here is my code: http://pastebin.com/K08z0Tg6
It's relatively easy to follow.

I noticed that on line 55, If I made that loop happen less times, sometimes I wouldn't be kicked. However, even when I was not kicked, I did not experience any block changes.

 

Tirelessly
Try looking over this thread, you might get some pointers on it
https://forums.bukkit.org/threads/setting-thousands-of-blocks-in-a-matter-of-seconds.142878/

 

xTrollxDudex As far as I can tell, that's actually setting the block type, not sending false changes.

 

Tirelessly
I never said you needed to copy that.

 

This is when you send too much data in a short period of time to the client. What I ended up doing was splitting the blocks into multiple chunks and send them with some delay in between.

 

Using sendBlockChange() for this is a massive waste of bandwidth and CPU resources. Instead, do it like Orebfucsator and modify the Map Chunk packets (51 and 56) directly.

In fact, I've already implemented this kind of chunk X-Ray with BlockPatcher (source) and ProtocolLib:
https://github.com/aadnk/BlockPatch...ava/com/comphenix/blocktest/BlockTestMod.java

 

Thank you!

 

Sheesh you can do anything with protocol lib