MC-156852 fix#2396
Merged
Merged
Conversation
mikroskeem
reviewed
Aug 2, 2019
HeyBanditoz
approved these changes
Aug 2, 2019
HeyBanditoz
left a comment
There was a problem hiding this comment.
Tested on a survival 1.14.4 server. Seems to work without issue. Thanks!
|
Thank you so much, I have merged this into my local clone of the async chunk io PR. |
As suggested by mikroskeem
electronicboy
requested changes
Aug 2, 2019
Added suggested change from electronicboy
electronicboy
approved these changes
Aug 7, 2019
zeanrivera
added a commit
to zeanrivera/Paper
that referenced
this pull request
Sep 7, 2019
the Ghost/Phantom Block Fix PaperMC#2396 The reason for this is that this fix re-introduces this bug https://bugs.mojang.com/browse/MC-156013 This gives server owners a way to opt out of the fix. It defaults to false, which is keeping the fix.
zeanrivera
added a commit
to zeanrivera/Paper
that referenced
this pull request
Sep 7, 2019
the GhostBlockFix PaperMC#2396 The reason for this is that this fix re-introduces this bug https://bugs.mojang.com/browse/MC-156013 This gives server owners a way to opt out of the GhostBlockFix. It defaults to false, which is keeping the GhostBlockFix.
zeanrivera
added a commit
to zeanrivera/Paper
that referenced
this pull request
Sep 8, 2019
…hostBlockFix PaperMC#2396 The reason for this is that this fix re-introduces this bug https://bugs.mojang.com/browse/MC-156013 This gives server owners a way to opt out of the GhostBlockFix. It defaults to false, which is keeping the GhostBlockFix. From: Zean Rivera <zean@zean.org> Date: Sat, 7 Sep 2019 03:11:05 -0700 Subject: [PATCH] Add a flag, "disable-ghost-block-fix", to allow for turning off the GhostBlockFix PaperMC#2396 The reason for this is that this fix re-introduces this bug https://bugs.mojang.com/browse/MC-156013 This gives server owners a way to opt out of the GhostBlockFix. It defaults to false, which is keeping the GhostBlockFix.
zeanrivera
added a commit
to zeanrivera/Paper
that referenced
this pull request
Sep 8, 2019
…hostBlockFix PaperMC#2396 The reason for this is that this fix re-introduces this bug https://bugs.mojang.com/browse/MC-156013 This gives server owners a way to opt out of the GhostBlockFix. It defaults to false, which is keeping the GhostBlockFix. From: Zean Rivera <zean@zean.org> Date: Sat, 7 Sep 2019 03:11:05 -0700 Subject: [PATCH] Add a flag, "disable-ghost-block-fix", to allow for turning off the GhostBlockFix PaperMC#2396 The reason for this is that this fix re-introduces this bug https://bugs.mojang.com/browse/MC-156013 This gives server owners a way to opt out of the GhostBlockFix. It defaults to false, which is keeping the GhostBlockFix.
LeonTG
pushed a commit
to LeonTG/Paper
that referenced
this pull request
May 17, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixed MC-156852
This corrects the 1.14.4 of "phantom" blocks that the client thinks are deleted but the server does not.
It uses the same solution that fixed the glitch that caused the same issue in 1.8-1.12.
Originally solved by Gnembon on MC-5694 at bugs.mojang.com
1.14 https://bugs.mojang.com/browse/MC-156852
1.12 https://bugs.mojang.com/browse/MC-5694