-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Gameplay permissions #5544
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
Open
dktapps
wants to merge
26
commits into
minor-next
Choose a base branch
from
gameplay-permissions
base: minor-next
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Gameplay permissions #5544
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Blocking items:
|
the remaining bool flags are user input toggles, not abilities, so it doesn't make sense to move them to permissions. permissions are intended for what the player is *allowed* to do, not what they *want* to do.
this eliminates all remaining usages of isCreative(), except for reach distance checks. Reach distance can't be migrated to a permission in an obvious way.
Member
Author
|
Sticking points I have with this:
|
Contributor
|
This probably doesn’t apply to this PR, maybe it’s worth creating issue for it? It would also be useful to allow granting a player permission for a specific |
Member
Author
|
There's already an open issue for that. It's not super clear how that would be implemented at the moment. |
these functions have been booby traps for a while since they don't actually do a strict game mode check by default. In any case, most if not all uses of game mode checks can be superseded by permission checks now. I think the only cases left uncovered are noclip-entities and spectator mode hiding (not spawned and no sounds sent).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Category: Core
Related to internal functionality
Category: UI
Related to the user interface (e.g. commands, terminal output)
Type: Enhancement
Contributes features or other improvements to PocketMine-MP
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduction
This PR implements #5512.
The motivation for this PR is described in #5512.
Relevant issues
Closes #5512
Changes
API changes
Behavioural changes
CanPlaceOnandCanDestroycheckstrueon the player.Backwards compatibility
Should be fully backwards compatible.
Follow-up
Add further permissions for the following:
Tests
This has been tested in-game.
Full list of permission changes per generated documentation