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

claimListSorting error #21

Open
Blackmadman opened this issue Jul 12, 2024 · 4 comments
Open

claimListSorting error #21

Blackmadman opened this issue Jul 12, 2024 · 4 comments

Comments

@Blackmadman
Copy link

If I set claimListSorting: from false to true in config.yml, no more claims are displayed with /claimlist, only the blocks you have. No error message in the console or in the log.

Minecraft 1.21
latest Papoer 1.21

@RoboMWM
Copy link
Collaborator

RoboMWM commented Jul 12, 2024

is clickableclaimslist also set to true?

@RoboMWM
Copy link
Collaborator

RoboMWM commented Jul 12, 2024

also curious if any of these work on spigot vs. paper

@Blackmadman
Copy link
Author

OMG .....
clickableclaimslist was always set to true.
Now I have set this to false and now everything is displayed when claimListSorting is set to true, including the claim names I have given to the 3 claims.

  • claimListSorting to false and clickableclaimslist to false = normal claim list without names

  • claimListSorting set to true and clickableclaimslist set to true = incorrect claim list, only the blocks are displayed.

  • claimListSorting to true and clickableclaimslist to false = normal claim list WITH the names

So the error seems to be in clickableclaimslist. But I haven't tested the last few days and there have been some updates at Paper. So I don't know if that might have been the problem.

2024-07-12_19 55 30

@RoboMWM
Copy link
Collaborator

RoboMWM commented Jul 12, 2024

so paper is silently discarding spigot-formatted stuff is what it sounds like, as I'd imagine this would work on spigot no issues.

If that's the case, I'd need to add something to disable and/or warn in server logs about formatting not being supported in paper.

I'd imagine paper support isn't hard since I know they talk a lot about how great their new api for it is, but alas it do be a new feature, and given that this is a commissioned plugin that I don't use, I don't have any interest in implementing the feature for non-patrons - any other dev is free to implement for free though.

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