search

FastFelix771 / TownyWands

A highly customizable GUI plugin for Towny to make the life of Minecraft players a little bit easier.
http://dev.bukkit.org/bukkit-plugins/townywands/
GNU General Public License v3.0
4 stars 2 forks source link

BungeeCord / VentureChat netty-kick #6

Closed bnussman closed 8 years ago

bnussman commented 8 years ago

Whenever I push Done when i am entering a value into a sign, I get disconnected from that spigot server and get sent to the hub of the bungee server. I get the following message in chat, and no errors in console. capture

bnussman commented 8 years ago

Here are my plugins on the server that disconnects me when i submit a value on a sign. capture2

bnussman commented 8 years ago

This is what it looks like when I am disconnected when i press 'done'. capture3

bnussman commented 8 years ago

This is the error in the Bungee console. It must be a Bungee issue? I am on the latest version of bungee too. (Build 1168) capture4

FastFelix771 commented 8 years ago

VentureChat - for some reason its incompatible with TownyWands. And there are also some general issues with ProtocolLib and BungeeCord, but this issue is probably caused because of VentureChat. Try with VentureChat disabled, if the issue is still there, i'll take a look whats wrong there. :)

bnussman commented 8 years ago

Well dang! I really need venture chat! But thanks for the support!

FastFelix771 commented 8 years ago

https://github.com/FastFelix771/TownyWands/issues/2 This guy had the same problem, but only with special BungeeCord versions. It was able to work with VentureChat with another version.. very strange things.

I was not able to find the true source of that issue, also author of VentureChat wasn't and i guess dmulloy2 would also send us to the BungeeCord authors. - There must be something in BungeeCord that screws up the SIGN_UPDATE packet.

You could try out some of the latest Bungee versions, maybe you find one that works... maybe not, but as long as i can't find the source of that bug, i can't do something against it. :(

But maybe it fixes itself with the full switch to ProtocolLibs API... i'll try to reproduce your problem with the very latest version i've created so far - maybe it magically starts to work.