Skip to content
This repository has been archived by the owner on Dec 31, 2023. It is now read-only.

Setting permissions for a WS world #47

Open
CrazyCloudCraft opened this issue Jul 18, 2022 · 0 comments
Open

Setting permissions for a WS world #47

CrazyCloudCraft opened this issue Jul 18, 2022 · 0 comments
Labels
new-feature New feature or request

Comments

@CrazyCloudCraft
Copy link
Member

CrazyCloudCraft commented Jul 18, 2022

Is your feature request related to a problem? Please describe
Problem with setting permissions inside a WorldSystem world.

Describe the solution you'd like
There is already the option in the plugin config.yml to execute commands on the get command. This makes it possible to add permissions for the creator of the plugin. But this is only for the creator and not for added players and if the world is deleted, the permission still exists and they will pile up over time. Adding commands on deleting of a world, so the permission could also be deleted, would be the solution.

Describe alternatives you've considered
With the LuckPerms API a custom contex for WorldSystem could be added. This would allow for totaly custom permissions on the world and enable options, like permissions for added players.

A not so ellegant alternative would be to add a placeholder for PlaceholderAPI, like %worldsystem_in_ws_world% which would be true if someone is in a WS world. With the ExtraContext plugin from Luckperms the Placeholder clould be added as a context.

Suggested by: @Xaver106

@CrazyCloudCraft CrazyCloudCraft added the new-feature New feature or request label Jul 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
new-feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant