Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kicked when chatting on recent Bungee/Waterfall #97

Open
datatags opened this issue Nov 9, 2023 · 2 comments
Open

Kicked when chatting on recent Bungee/Waterfall #97

datatags opened this issue Nov 9, 2023 · 2 comments

Comments

@datatags
Copy link

datatags commented Nov 9, 2023

When VentureChat v3.6.0 is installed on Waterfall 552 or BungeeCord 1769, I am kicked whenever I send a chat message. In the console I get:

00:21:51 [WARNING] [datatags] <-> DownstreamBridge <-> [hub] - could not decode packet! io.netty.handler.codec.DecoderException: java.lang.IllegalArgumentException: No enum constant net.md_5.bungee.api.chat.ClickEvent.Action.

I tried removing the click events from the chat formatting, but it didn't seem to change anything. Let me know if any other details are needed. Thanks!

(This doesn't seem to be related to #91 as I don't have this issue on Waterfall 548, which didn't exist at the time of the most recent comment.)

@Aust1n46
Copy link
Owner

Aust1n46 commented Dec 4, 2023

I downloaded BungeeCord 1774 the other day and had no issues. Pretty sure I don't use any click events from BungeeCord.

@datatags
Copy link
Author

datatags commented Dec 7, 2023

Apparently this happens when certain placeholders are used in the channel format, including invalid ones. For example, setting the channel format like this causes it for me:

format: '{invalidplaceholder}&f:'

I also have a PAPI expansion that causes it, but invalid placeholders are probably the easiest thing to check with

Edit: Never mind, it's not that, still not sure what's going on

Edit again: No, it was that, and it was also that the format of the jsonformatting block had changed and my config hadn't been migrated. Both of those seem to cause the issue I'm having

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants