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

Remove Blacklist module #822

Closed
dualspiral opened this issue May 2, 2017 · 1 comment
Closed

Remove Blacklist module #822

dualspiral opened this issue May 2, 2017 · 1 comment

Comments

@dualspiral
Copy link
Member

The item blacklist module was a hangover from EssCmds that does not function well. It's not seen much love, and it's never been something that fully fits in an Essentials style plugin, more suited for protection plugins.

As a result, we will remove the blacklist module and provide migration paths to other plugins.

The obvious migration path is GriefPrevention and I will get support from @bloodmc to do this, but I invite other protection plugins to supply migration too.

Anyone is welcome to provide other migrators, and I will build a system to snap them in.

@Mohron
Copy link
Member

Mohron commented May 2, 2017

This is a good call!

@dualspiral dualspiral self-assigned this May 2, 2017
dualspiral added a commit that referenced this issue May 2, 2017
dualspiral added a commit that referenced this issue May 7, 2017
dualspiral added a commit that referenced this issue May 9, 2017
The Blacklist module was poorly maintained, and there are much better solutions out there. We are there retiring the module, it does not really belong in an essentials like plugin.

A migrator for ProtectionPerms is available, GP will come soon after they version bump. An API is available to get the old data.

* Fix @scan scanner not being restricted to a specific Java package.

Fixes #822
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants