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
ServerInternalException: Attempted to place a tile entity where there was no entity tile! #437
Comments
Will work on mitigation soon, likely just remove these corrupt TEs. |
I still get the error.
|
Have you enabled the option to remove corrupt tile entities? Your servers map has an issue in that there is TileEntity data stored for a block on the map that is air |
Sorry, but where’s that option?
…On 27 Apr 2017, 10:20 PM +0800, Shane Freeder ***@***.***>, wrote:
Have you enabled the option to remove corrupt tile entities? Your servers map has an issue in that there is TileEntity data stored for a block on the map that is air
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
paper.yml remove-corrupt-tile-entities |
Will it break any blocks thats not air? Should I keep it enabled? |
@BirkhoffLee While you're waiting for an answer, I'd recommend to make a backup of your world and check it yourself. You'll need a backup anyway in case that option goes wrong. |
No, it won't remove any blocks from the map, that option will only remove a TE, not any blocks themselves, in the event that it's considered invalid: e.g. there is a TE where there is no block for a TE, it shouldn't have any negative effects for most people, however, is left configurable and disabled by default, you could theoretically fix this manually by modifying the map, however that's out of scope. |
Alright, thank you all! I enabled that option and I no longer see that error.
…On 27 Apr 2017, 11:13 PM +0800, Shane Freeder ***@***.***>, wrote:
No, it won't remove any blocks from the map, that option will only remove a TE, not any blocks themselves, in the event that it's considered invalid: e.g. there is a TE where there is no block for a TE, it shouldn't have any negative effects for most people, however, is left configurable and disabled by default, you could theoretically fix this manually by modifying the map, however that's out of scope.
it should be safe to leave that option enabled
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hey, I'm now facing this same error and I'm wondering why this option doesn't exist anymore? |
Because the entire TE system changed in a way that outside of generation bugs or janky plugins meant that this was much less likely to occur, and given the patch was broken nobody cared to update it given such |
Paper (Spigot 1.10.2) dev 881
WorldEdit v6.1.5 dev 3623
These errors occur all the time for me when loading chunks that had a worldedit schematic pasted and undone, or a player fully rolled back from a grief. Even seemingly random in areas that don't look to have been touched by worldedit / a player rollback.
Should some form of recovery or suppression be added or just safe to ignore all the exceptions that occur?
The text was updated successfully, but these errors were encountered: