For starters, when I have a schematic placement in an unloaded chunk and then enter the end I bug out like as if you were stuck in a block but can't mine it. I have to relog in order to fix that but when i spawn in, my armour that shows above your hearts disappears even though i am wearing armour. Then if I die and respawn my character is in a semi-void world that has 16x16x16 cubes of random blocks, then a second later I crash. Another issue is that if I try to remove that loaded schematic my game crashes.

This is the crash report for the schematic removal:
https://hastebin.com/misuronigo.php

This is the crash report for the Die then crash:
https://hastebin.com/tozeseqomo.cs

This is the picture of the weird void world:
https://imgur.com/a/6HHkwWL

Can you post the full list of mods and their versions you have installed?

Also can you post the console log (starting from when you launch the game) from a case where you get the bugged out chunks? That seems like there is something breaking the normal client chunk handling somehow. I have heard of a similar report before, but I have never seen that happen myself.

As for the crashes that happen... have you modified (overwritten) the schematic after you first created that placement? Could you zip up and post the config files and the schematic in question which causes that crash? (The config is at config/litematica/litematica_world_or_server_name_dim1.json for The End. Feel free to rename the file for the zip to protect the server IP.) Although I think I've already fixed that crash during the later 1.12 development versions, but I'd still like to know how that crash happens. The only reason I can think of is that the schematic got changed/replaced after the placement was fist created.

You could try toggling the loadEntireSchematics option in the Generic category to false. I don't remember how that stuff works in the current 1.13.2 version (which is pretty old by now, from before mid-December development-wise) , but in the later 1.12 versions it was set to false by default, as in the later 1.12 dev versions things work a lot better with that option disabled.

Closing due to inactivity. If this is still an issue in the current versions, and ruled out from being in another mod (as I've never seen this), then feel free to re-open the issue.

Yes and yes))

Regular users can't reopen issue, if someone with write access closed it. There is just no button.

Even their own issues? Kinda weird... 🤔

Can you try if this still happens in the latest builds that were released a few days ago?