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

Jmap Viewing / Usage Restrictions. #147

Open
1 task done
StoneLegion opened this issue Dec 7, 2024 · 1 comment
Open
1 task done

Jmap Viewing / Usage Restrictions. #147

StoneLegion opened this issue Dec 7, 2024 · 1 comment

Comments

@StoneLegion
Copy link

Your GTNH Discord Username

StoneLegion

Feature Request

This might be a bit too complex and something people might not be as interested in. I have a couple things I like to see and change and maybe use the permission system for it.

  1. Permissions based on who can see chunks on the map
  2. Permissions based on who can see loaded chunks on the map. Honestly not anyone's business to see what chunks someone has loaded on a public server besides the admins.
  3. Permission system to add Server Side Claimed Chunks to be able to see them via the map... So the ones admins use to protect spawn, railway and maybe special projects and such. Where we use the manual command to create the team.
  4. Be nice to restrict or have permission for claim snipping. Basically people should not be able to sit at 0,0 and claimed land 32,000 blocks away.

Hope these idea's are sound, I'm not sure if their too difficult, but I think they would really help admins have a bit more control.

Thanks, PS I hope I'm not over spamming the github, feel free to close things you guys have no interest in.

Final Checklist

  • I have searched the issues and haven't found a similar issue.
@Lyfts
Copy link
Member

Lyfts commented Dec 7, 2024

There's already a permission node for your first point

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