Skip to content

Conversation

danthedaniel
Copy link
Collaborator

@danthedaniel danthedaniel commented Sep 30, 2025

This reverts commit 54a6fe4.

Unfixes: #144

With 1.21.9 coming out tomorrow and #148 unresolved I figured I'd revert it as I'm not in the mood for fixing it.

@creesch
Copy link
Owner

creesch commented Oct 4, 2025

This seems a bit nuclear to me. Can't we just catch that json parsing error and fall back to plain text? If memory serves me right I already did something similar elsewhere.

playerDisplayName,
client.world.getRegistryManager()
);
} catch (JsonParseException exception) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we already catch JsonParseException here, it seems to me that also catching JsonSyntaxException would likely complete the workaround.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would be redundant:

public final class JsonSyntaxException extends JsonParseException

@danthedaniel
Copy link
Collaborator Author

This seems a bit nuclear to me. Can't we just catch that json parsing error and fall back to plain text? If memory serves me right I already did something similar elsewhere.

If you'd like to fix it be my guest. But I looked at the code, figured it was already messy and didn't need more branches, didn't want to understand how the text was actually structured, and decided the feature isn't that important. Nobody asked for it and it's never been in a release.

@creesch
Copy link
Owner

creesch commented Oct 16, 2025

Closing it in favor of the fix here: #163

@creesch creesch closed this Oct 16, 2025
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

Successfully merging this pull request may close these issues.

2 participants