Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

mv.bypass.gamemode problems #1030

Closed
aikar opened this Issue · 4 comments

3 participants

@aikar

1) this.ignoreperm = new Permission("mv.bypass.gamemode." + this.getName(),
"Allows players wit this permission to ignore gamemode changes.", PermissionDefault.FALSE);

Why isn't this default Op?

2) Can we have a way to disable all of this logic.

I don't use MV for managing flght/gamemode, and it's a bit annoying as Op in dev testing to keep getting plummeted to the ground, see 3:

3) Any idea why MV is still ENABLING before my plugin which has loadbefore: ["Multiverse-Core"]?
My plugin doesn't get time to add the permission nodes on a reload, and sends me to the ground.

Adding the bypass nodes is at least working for join, but MV runs before our code does on /reload and drops me.

@main--
Owner

Why isn't this default Op?

Once upon a time, this was default for ops but then users complained because it didn't work for them. Having a "right" default value here is simply impossible.

Can we have a way to disable all of this logic.
I don't use MV for managing flght/gamemode, and it's a bit annoying as Op in dev testing to keep getting plummeted to the ground, see 3:

There is a way to disable all this: Just change the bypass permissions to true default in the permissions.yml.

Any idea why MV is still ENABLING before my plugin which has loadbefore: ["Multiverse-Core"]?

I have no idea, that's maybe a Bukkit issue.

@main-- main-- closed this
@aikar
Once upon a time, this was default for ops but then users complained because it 
didn't work for them. Having a "right" default value here is simply impossible.

It's pretty expected behavior that Ops have all permissions -- So why not default it to Op
and then the people who want the awkward experience can be the ones to suffer from weird behavior.

There is a way to disable all this: Just change the bypass permissions 
to true default in the permissions.yml.

I can not find documentation on this feature - http://wiki.bukkit.org/Permissions.yml
Can we please just have an easy boolean value in the multiverse config to turn off
these checks so it behaves like the old version of Multiverse did?

I have no idea, that's maybe a Bukkit issue.

Most likely, was just asking here to see if it triggered any ideas or incase it was
due to some special actions on Multiverse. Someone in BukkitDev told me that
Multiverse had load: STARTUP and that was the issue, but it doesn't it
seems... so figured I'd least bring it up.

@main--
Owner

It's pretty expected behavior that Ops have all permissions -- So why not default it to Op
and then the people who want the awkward experience can be the ones to suffer from weird behavior.

It's impossible to do this the right way and flipping it around once again would only create confusion.

I can not find documentation on this feature - http://wiki.bukkit.org/Permissions.yml

It's right there:

default: The default value for the parent-node if it's value is not set. The four values that can be set are: true, false, op, and not-op.

Explains everything.

Can we please just have an easy boolean value in the multiverse config to turn off
these checks so it behaves like the old version of Multiverse did?

Why? That config option would be completely redundant.

Someone in BukkitDev told me that Multiverse had load: STARTUP and that was the issue, but it doesn't it seems... so figured I'd least bring it up.

You could now either set your plugin to load: STARTUP or try adding your plugin to the dependencies in MV's plugins.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.