Shell Constructor Stops Working After World Reload - Requires Breaking/Replacing Every Time (Wastes Energy)

[eriksporre1994-pixel]

Shell Constructor stops functioning after exiting and reloading the world/game. Player gets stuck in spectator mode on death, regardless of prior use. Must break and replace the Shell Constructor every time after reload saves (wastes energy).

Steps to Reproduce:

1. Build Shell Constructor and fully supply power (complete construction).
2. Exit and reload the world/game.
3. Die in-game.
4. Observe: Stuck in spectator mode; Shell Constructor doesn't respawn player.

Expected Behavior:
If the Shell Constructor is finished and fully powered, it should always respawn the player even after exiting and loading the game.

Actual Behavior:
Shell Constructor always works if it's fully constructed and powered, but if the player exits the game, loads the game, and dies, it will not respawn the player.

Thanks for the great modpack! Let me know if you need more details.

no respawn on death after load saves
https://github.com/user-attachments/assets/d40bb199-570d-4246-b70e-ac9fd887acd9

Replace Dies Once And Relog In And Dies Again
https://github.com/user-attachments/assets/8b5f4335-a6ad-4693-81d8-1b8d5cd3b5f8

Replace And Relog And Dies
https://github.com/user-attachments/assets/63c79e6f-3d81-4268-afc5-b6c9a6180af8

[pawjwp]

This is an issue I've had about a dozen reports on on our discord server. Even though it seems to be very widespread, I have never been able to reproduce it when testing on my own device, making it almost impossible for me to test/fix. However, this report is the most detailed information I have been able to get and if you are still experiencing the issue reliably, I may be able to track down what's causing it. Most other people that have had the issue can't recreate it after it happens the first few times.

I've been asking players a standard set of questions when they report this, and you've already answered some of them, but I'm curious to hear your answers for 6 and 10:
1. How recently had your shell been created when you died and didn't sync properly? Almost immediately
2. Had you left the game and rejoined since creating the shell? Yes
3. Were you playing multiplayer No
4. What power generation method were you using to create the shell? Thermal/Mekanism Power Storage
5. Had you already died and synced to your shell on the world or would this have been the first time? Yes
6. Roughly how many times have you died and experienced this issue and how many times have you died and synced correctly?
7. Does the issue still happen? (If so, I could send you experimental builds of the mod to see if they fix it) Yes
8. How close were you to the shell constructor/storage when you died? Within 50 blocks
9. Were the shells in a shell constructor or shell storage? Constructor
10. How would you estimate the speed/quality of your computer? High/medium/low-end hardware?

Finally, I have an experimental build of the Sync mod I have been working on. It fixes a couple small edge cases that could cause failure to sync, though the symptoms of your issue don't exactly line up with what those changes fix. (It also adds better compatibility with Curios, Thirst, and Diet.)

Here's a download link, it's also shared in our Discord. Let me know if the download doesn't work and I could try to properly post it somewhere instead. Could you try to play with the testing build and let me know if the syncing problems still happen? In the meantime, I'll look into some other issues that could be related based on what you've sent.

[eriksporre1994-pixel]

Thanks for the detailed response. Here's my answers to 6 and 10

---

6. Roughly how many times have you died and experienced this issue and how many times have you died and synced correctly?

I died once the day before, and it functioned correctly. I exited the game, and the next day after reloading, I died again and it didn't work. From what I tested, I can die as many times as I want and it will work as long as I don't exit the game—it stops functioning as soon as I reload the world.

---

10. How would you estimate the speed/quality of your computer? High/medium/low-end hardware?

Mid-tier I'd say—it has 32GB DDR4 RAM, Intel i3, and a Cerberus 1070Ti.

---

From my current world save that I luckily backed up before, I was able to consistently repro the issue and it occurs every time from the repro I provided. My first playthrough: Used Shell Constructor, died — it functioned. Afterward, I built a bed to skip night and it stopped working (could not remember if i did exit the game or not). Thought the bed interfered, so next run I avoided using bed but it still occurred. Confirmed it's reliable from reloading the save/game

I'll try testing this again from a fresh start world and on a faster computer later, and I'll update you with the results. Thanks again, really enjoying the modpack!

[eriksporre1994-pixel]

Findings:
Shell Constructor works normally without shaders — no issues after reload/death.

With shaders enabled: Issue reproduces 100%. After world reload, death leaves player stuck in spectator. Must break/replace Shell Constructor to fix (recurs every reload).
(Only tested with ComplementaryReimagined_r5.6.1. on current release of the modpack on a same saves as before)

shaders are the clear trigger.

Repro with Shaders:

1. Enable shaders.
2. Build fully powered Shell Constructor.
3. Exit/reload world.
4. Die — stuck in spectator (no respawn).

No Shader>Dies>Reload>Dies = No Issue
https://github.com/user-attachments/assets/0a7d4d48-43cd-44ff-9ff1-d89734e18b6c

No Shaders>Dies>Enable Shaders>Dies>Reload>Dies = Issue
https://github.com/user-attachments/assets/6e9e20c9-2667-4e1e-93f3-d8554ebb1980

[pawjwp]

Interesting, I can't believe it might be that simple. I'll do some testing tomorrow, though I worry if it's an issue with shaders, this will be a hard bug to fix.

[eriksporre1994-pixel]

Yeah, I discovered it by testing on different computers (can't tell you where the other one was, wink wink*), and I couldn't get the issue to occur at first. I thought it was a mid-low end PC problem, until I realized the difference, shaders are disabled by default on a new modpack install. When I was playing at home, I enabled them, Very strange how shaders make it non-functional.

If you look closely during shell construction in the clip I attached:

Shaders enabled: Pixel-by-pixel body build isn't visible until 100% complete, the body just pops in fully.

Shaders disabled: Body builds pixel-by-pixel all the way through.

i wonder if LAN multiplayer the host has shaders off and the joiner has them on, then the joiner logs off/on, could the perspectives differ? Couldn't test 2-player/servers yet, this weekend I'll try different shaders to see if it's all of them or specific ones.