Skip to content
This repository has been archived by the owner on Nov 5, 2019. It is now read-only.

Disable using "/mstore sponsor" for operators by default #256

Closed
wants to merge 1 commit into from

Conversation

LaxWasHere
Copy link

No description provided.

@ravkr
Copy link

ravkr commented Apr 18, 2016

We need that change! it is very important!

@sweepies
Copy link

-1

@fynntimes
Copy link

Commit message should be "change massivecore.sponsor permission to be not default" or something along those lines.

@magnusulf
Copy link
Contributor

Do you mind sharing why this change is needed? Per default we give all permissions to operators, that is kinda the point of operators.

@RoboMWM
Copy link

RoboMWM commented Apr 18, 2016

The message also clutters server logs; this PR in my opinion doesn't go far enough. 👍 for at least getting the ball rolling in the right direction.

@markhughes
Copy link
Contributor

Thank you for your support!! 😄

We really love it when people want to help out with the Factions plugin. However, I think disabling this permission by default will annoy a lot of server owners.

As this is the permission required to run the /mcore sponsor command - which disables the message. 🐳

@LaxWasHere
Copy link
Author

Having the message enabled by default is annoying enough so why not take the owners ability to disabled it? That way the advertisers can give the developers more money and everyone will be happy.

@markhughes
Copy link
Contributor

markhughes commented Apr 19, 2016

Hey Lax - I don't think thats a very good idea.

Please consider that although you're happy to leave the message enabled that not everyone would be.

Thank you again. I will lock this conversation for now so that other developers can consider your pull request.

@MassiveCraft MassiveCraft locked and limited conversation to collaborators Apr 19, 2016
@markhughes markhughes changed the title Fixes stupid bug that makes the plugin stupid. Disable using "/mstore sponsor" for operators by default Apr 19, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants