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

Add more permissions (Fixes #50 & #40) #52

Open
wants to merge 2 commits into
base: 1.13
Choose a base branch
from

Conversation

Phoenix616
Copy link

This adds permissions to all commands (default to the previous op value besides the checkforupdate one which was changed to op too as players should not be able to change that value in the config...) and one for using the server integration. (vive.use, allowed by default so it behaves like before) Also moved the climb bypass permission to the plugin.yml to actually be registered properly. (Default is the same as before: op)

Also use alias for the command instead of registering it twice, update old server version in build.gradle and add all permissions to readme.

Also update old server version in build.gradle and add all permissions to readme.
@@ -59,6 +59,10 @@ public void onPluginMessageReceived(String channel, Player sender, byte[] payloa
return;
}

if(!sender.hasPermission("vive.use")) {
Copy link
Collaborator

@Techjar Techjar Jun 1, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not really okay with this permission. It's meant to be a thing that just works, no conditionals.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It just works with the default settings unless the vive.use permission is manually revoked by the server administrator. (Which basically makes it behave like he didn't install the plugin in the first place to the player in question but out of the box it just works)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I know, but I do not understand the purpose of that, and I believe it's nothing more than user-hostile.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So rather than allow some trusted users to have access to a better Vivecraft experience you want server admins to choose between either giving everyone access to game-breaking functionality or not providing a better integration at all? I don't see the logic in that... do I really need to waste time writing a mod to exploit this?

plugin.yml Outdated Show resolved Hide resolved
plugin.yml Outdated Show resolved Hide resolved
Copy link

@RoboMWM RoboMWM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good quality PR

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

Successfully merging this pull request may close these issues.

3 participants