We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is it technically feasible to separate the "creation" permission node for sign-based portals into (A) Standalone portals and (B) Obsidian portals?
I'd like to restrict essentially all Multiverse permissions from users, except:
The arbitrary destination availability pending permissions, of course. (E.g, users cannot sign-portal into worlds they are otherwise restricted from.)
The text was updated successfully, but these errors were encountered:
For 1 this is already possible: multiverse.signportal.validate
multiverse.signportal.validate
For 2 I'll file this as a feature request (seperating the perms) and stage it for 2.2.
This is handled automatically by Core.
Sorry, something went wrong.
Pushing to 2.3.
Doing some issue management. I will do this, but it's gonna take more time than I have tonight.
No branches or pull requests
Is it technically feasible to separate the "creation" permission node for sign-based portals into (A) Standalone portals and (B) Obsidian portals?
I'd like to restrict essentially all Multiverse permissions from users, except:
The arbitrary destination availability pending permissions, of course. (E.g, users cannot sign-portal into worlds they are otherwise restricted from.)
The text was updated successfully, but these errors were encountered: