Sponge "Layered" Permissions API Proposal

[IDragonfire]

I disagree with you @gratimax

Not all servers need the 6 points you listed.
The infrastructure looks similar, but the implementation of the permission plugin is different.
It is good if the user can choice from plugins. If one plugin is perfect then nobody would start a new plugin
In my opinon the Permission API need three things (similar to @SpaceManiac)

Specification of a Permission API

1. Has user X permission Y
2. Give user X permission Y
3. Remove Permission Y from user X

Optional - Syntax Sugar

1. List all permissons for each plugin
2. Give a description for each perm

Not part of the API

1. List users that have permission X
2. Groups

Sponge should have X!

I know I can’t be the only one to notice this. Almost on a daily basis, new users join the forums, and request that one of the following be added: Permissions Economy Anti-Cheat Log-Block Super Awesome Mega Great Feature That Is Explained In One Sentence While its all well and good that people would like to contribute ideas, suggestions, and feedback to Sponge, I think its critical that a couple of things are addressed, at a global pinned level. Please note none of this is meant as a personal…

Keep it Simple - SpongeAPI = Interfaces != Utils

keep it simple - atm we need no syntax sugar KISS SpongeAPI is an API, an interface to modify the minecraft server. Complex things, like Persistence API AnnotationBased Config System AutoPluginUpdate ComplexPrefixbased Annotation Command System PermissionAliases RxEvents … can we later build on top. Keep that in mind (I learned it, too) I like the discussions on IRC of cool complex systems, but atm. we need a clean, simple, leightweight and BASIC Interface. We have already a thre…