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

Spacial Storage crashes game #3296

Closed
Zacxen opened this issue Dec 29, 2017 · 3 comments
Closed

Spacial Storage crashes game #3296

Zacxen opened this issue Dec 29, 2017 · 3 comments

Comments

@Zacxen
Copy link

@Zacxen Zacxen commented Dec 29, 2017

When I attempt to use any large Spacial Storage system or a small one with an ae2 multi-block crafting unit, everything gets moved into the Storage cell then Minecraft crashes.

I am running Maverick's Tech Overload Modpack. I tried installing the newest version of AE2: rv5-stable-3 and it still crashes. It happens only when transferring the crafting multi-block structure and with 70x70x70+ storage areas. If you reload after the crash everything is then in the storage cell and can be brought back into the overworld just fine.

https://pastebin.com/ruw12uNq

  • Minecraft Version: 1.12.2
  • AE2 Version: rv5-stable-3
  • Forge Version: 14.23.0.2549
@yueh
Copy link
Member

@yueh yueh commented Dec 30, 2017

Please remove the SpatialCompat mod as it will whitelist incompatible TEs and cause crashes/world corruption/etc due to it. But worst case it might already be corrupted in some sort.

@Zacxen
Copy link
Author

@Zacxen Zacxen commented Dec 30, 2017

I removed all mods except ae2, created a new world and attempted to put the multi-block crafting CPU into a storage cell. Minecraft still crashed. Also, this issue was happening before SpacialCompat was installed. Here is the latest crash log.

https://pastebin.com/ZAFCD5VM

@yueh
Copy link
Member

@yueh yueh commented Dec 30, 2017

Yeah, I found a issue with crafting cpus and how forge handles restoring tile entities in some cases causing it to duplicate them. (Which seems to be a bit related to the order the cpu is transfered)

But just in case, the approach that mod uses is extremely dangerous and will result in dataloss at some point.

yueh added a commit that referenced this issue Dec 30, 2017
Updating the blockstate of invalid TEs will cause Forge to restore the
block including the TE leading to invalid TEs sticking around after
being moved.
@yueh yueh closed this in a7a65ae Dec 31, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants