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

Flight is maintained after switching world via end portal; even if essentials.fly was denied for that end world. #5040

Closed
ultraic-space opened this issue Aug 8, 2022 · 1 comment
Labels
status: duplicate Duplicate of another ticket.

Comments

@ultraic-space
Copy link

ultraic-space commented Aug 8, 2022

Type of bug

Other unexpected behaviour

/ess dump all output

https://essentialsx.net/dump.html?id=ab1b82ddcc92426cb6f17a010c4d0870

Bug description

We have a player on another world (in my case, world_spawn) who has the essentials.fly permission enabled in that world via contexts.
If the player has essentials.fly denied via contexts to the end world, and they enter an end portal in world_spawn while flying; they will keep their flight. This is unlike if they enter the end world via commands like ./warp, in which case their flight is removed.

Minecraft.2022.08.08.-.16.32.22.15.mp4

I'm not exactly sure if this is a bug with Essentials or Luckperms, so please let me know if I'm in the wrong place.

Steps to reproduce

  1. Give the player essentials.fly in context world=world, and deny essentials.fly in context world=world_the_end.
  2. Go to an end portal, do ./fly and fly into the portal.
  3. The player will have flight after entering the portal.

Expected behaviour

The player will no longer have flight if they enter an end portal to a world where they do not have permissions to use essentials.fly.

Actual behaviour

If entering a portal, the player maintains flight even if the entered end world has the appropriate permission essentials.fly denied for that end world.

@ultraic-space ultraic-space added the bug: unconfirmed Potential bugs that need replicating to verify. label Aug 8, 2022
@JRoy
Copy link
Member

JRoy commented Aug 18, 2022

Duplicate of #4325

@JRoy JRoy marked this as a duplicate of #4325 Aug 18, 2022
@JRoy JRoy closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2022
@pop4959 pop4959 added status: duplicate Duplicate of another ticket. and removed bug: unconfirmed Potential bugs that need replicating to verify. labels Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate Duplicate of another ticket.
Projects
None yet
Development

No branches or pull requests

3 participants