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

%claimchunk_am_trusted% does not work #299

Open
timmyb4 opened this issue May 30, 2024 · 6 comments
Open

%claimchunk_am_trusted% does not work #299

timmyb4 opened this issue May 30, 2024 · 6 comments

Comments

@timmyb4
Copy link

timmyb4 commented May 30, 2024

Versions
Spigot Version: 1.20.6
ClaimChunk Version: 0.0.25-fix1

Describe the bug
plahoderapi tag %claimchunk_am_trusted% does not work.

To Reproduce
Steps to reproduce the behavior:

  1. update placeholder api and chunckclaim
  2. start server

Expected behavior
%claimchunk_am_trusted% must game trusted or not trusted text.

additional issues
[ClaimChunk] An update for ClaimChunk is available! Your version: 0.0.25-FIX1 | Latest version: 0.0.25

@cjburkey01
Copy link
Owner

cjburkey01 commented May 30, 2024

Ah crap I knew that'd come back to bite us, thank you for the report!

We disabled that in 0.0.24 to allow the new access flags to work, but we can do a dirty fix if you'd like (maybe just lists which permissions players have access to in a given chunk?)

So instead of saying yes or no, it would be like "break, place, interactEntities" etc.

Would that work for your use case?

Also renaming it might be in order, like to %claimchunk_am_trusted_with% instead

Also my dang version checker system didn't account for post-release tags like FIX1...dang it

@timmyb4
Copy link
Author

timmyb4 commented May 30, 2024

I use it to display the claim so you can see of you can do something on someone chunk
2024-05-30_20 28 16

@cjburkey01
Copy link
Owner

Hm, maybe on top of the new permissions system, a /chunk trust command would just give people the same kind of access older versions used, then the placeholder would work. For now I guess, are you able to just remove that placeholder there until I get a solution?

@timmyb4
Copy link
Author

timmyb4 commented May 30, 2024

you can try do it with access that you are trusted with all permissions.
and with a few or one partially trusted.
and with no permissions not trusted.

@cjburkey01
Copy link
Owner

Ok, so FIX2 that I just released re-adds the placeholder and just behaves the same, but shows a player is trusted if they have any permissions granted for a given chunk, would you be alright waiting a few days for 0.0.26 so I can get a nicer solution (like the one you suggested, maybe a specific "not owned" value as well so it doesn't show "not trusted" in unclaimed chunks (it used to do that, right?))

@timmyb4
Copy link
Author

timmyb4 commented Jun 3, 2024

That is no problem thanks.
Maybe you can also add by ur own chunk it says owned.

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