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

Separate permission nodes #10

Open
jnsnow opened this issue Oct 20, 2011 · 3 comments
Open

Separate permission nodes #10

jnsnow opened this issue Oct 20, 2011 · 3 comments

Comments

@jnsnow
Copy link

jnsnow commented Oct 20, 2011

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:

  1. The ability to convert old multiverse signs into 'new' ones,
  2. The ability to create a new sign-based obsidian portal to any arbitrary destination.

The arbitrary destination availability pending permissions, of course. (E.g, users cannot sign-portal into worlds they are otherwise restricted from.)

@fernferret
Copy link
Member

For 1 this is already possible: multiverse.signportal.validate

For 2 I'll file this as a feature request (seperating the perms) and stage it for 2.2.

The arbitrary destination availability pending permissions, of course. (E.g, users cannot sign-portal into worlds they are otherwise restricted from.)

This is handled automatically by Core.

@ghost ghost assigned fernferret Oct 20, 2011
@timothyekl
Copy link
Contributor

Pushing to 2.3.

@fernferret
Copy link
Member

Doing some issue management. I will do this, but it's gonna take more time than I have tonight.

@fernferret fernferret removed their assignment Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants