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

[Enhancement Request] Server access permissions check #41

Open
TheLecturer opened this issue Apr 26, 2014 · 0 comments
Open

[Enhancement Request] Server access permissions check #41

TheLecturer opened this issue Apr 26, 2014 · 0 comments

Comments

@TheLecturer
Copy link

Hi -

Please consider adding the following permission set / check.

Scenario.
Server A can be accessed by all players.
Server B should only be accessed by certain players (based on a permission).

Today, access via PORTAL can be controlled using permissions to use appropriate portals. But access to a server can be gained using other geSuit plugins.

Example.
Player A is on Server A, and is not allowed on Server B.
Player B is on Server B, and is allowed on Servers A and B.
Player A sends a TPA request to Player B, Player B accepts. Player A is teleported to Server B, bypassing the Portal entry system.

Why not use BungeeCord's server access control in config.yml? Because it is "hard-coded" to the player, and cannot be dynamically controlled via a normal permissions plugin going through Vault (FYI, I use zPermissions).

Request
Add a "gesuit.server." (for example) permission which is checked for true before allowing access to a server by geSuit teleport / portals / warps / home.

I hope this makes sense.
Many thanks for considering.

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

No branches or pull requests

1 participant