JsonSyntaxException: Expected STRING but was BEGIN_OBJECT at path $.click_event.payload when using Adventure Click Callbacks

[smutnejmichal]

InteractiveChat fails to deserialize outgoing chat packets when a plugin uses the modern Adventure API feature ClickEvent.callback().

In modern Paper/Folia versions, Adventure allows developers to create click events that run server-side code without a visible command. This is serialized into a JSON structure where click_event.payload is an object/array containing a unique ID, rather than a simple string (which is used for run_command or open_url).

InteractiveChat's GSON/component serializer seems to expect a STRING for the click event value and throws an IllegalStateException when it encounters the BEGIN_OBJECT of a callback payload.

latest.log

[LOOHP]

Which build is your Minecraft server using? And which version of InteractiveChat?

[smutnejmichal]

Folia 1.21.8
InteractiveChat 4.3.4.0

[LOOHP]

Can you try updating to the latest dev build of IC and see if there are any differences?

[smutnejmichal]

I've updated to the latest version and the issue persists. Notably, the error only occurs when there is at least one player online on the server.

[LOOHP]

Seems to be caused by PaperMC/adventure#1335. When Adventure 5.0.0 is out, this issue should be fixed.

[LOOHP]

I pushed a dev build that uses 5.0.0-SNAPSHOT. Feel free to try whether it helps.

[smutnejmichal]

Thank u, but there is another issue: the latest commit (3e81198 – Use Adventure 5.0.0-SNAPSHOT) does not build on Jenkins.

The build fails in InteractiveChat-Abstraction because the Adventure 5.0.0-SNAPSHOT artifacts cannot be resolved:

Could not resolve dependencies:
net.kyori:adventure-*:5.0.0-SNAPSHOT
Could not find artifact ... in dmulloy2-repo / jitpack / codemc

So it looks like the required Adventure snapshots aren’t available in the configured repositories (Kyori snapshot repo is missing). As a result, the dev build doesn’t get produced.

Just wanted to report it — the fix itself makes sense, but the current setup doesn’t build.

[LOOHP]

Just fixed the build issue on the build server!

[smutnejmichal]

The error still persists

[LOOHP]

Well in that case maybe the snapshot doesn't contain the fix yet. We'll see when the full version comes out.