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

Spatial IO Entities Not Returning #3484

Closed
DarKaron opened this Issue May 7, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@DarKaron

DarKaron commented May 7, 2018

When a Spatial IO Port absorbs entities in version rv5-stable-10, they do not return to the material realm when you load the stored space back in.

Description

Essentially, I performed tests with a variety of entities and objects, and this is my discovery:
Chests and their contents are saved.
Of course, without editing the config, modded blocks are ignored by the Spatial Storage Unit.
However, any entities, be it mobs, paintings, item frames, dropped items, and even Players do what I like to refer to as "Exiting Existence". They vanish immediately and permanently, never to return.

  • Minecraft Version: Minecraft 1.12.2
  • AE2 Version: AppliedEnergistics2-rv5-stable-10
@bkbarbee

This comment has been minimized.

bkbarbee commented May 8, 2018

Can confirm as still an issue with rv5-stable-11.

@fscan

This comment has been minimized.

Member

fscan commented Jun 15, 2018

Please post a full log file or a crash log (F3-c).

@fscan fscan added the state-waiting label Jun 15, 2018

@fscan

This comment has been minimized.

Member

fscan commented Jun 26, 2018

Ok, i'm also getting this now. This is strange, i definitely tested with entities.
I get a lot of error messages from journemap, maybe TeamJM/journeymap#57 disrupts the transfer.
I'll investigate this.

@fscan fscan added type-bug and removed state-waiting labels Jun 26, 2018

@mindforger

This comment has been minimized.

Collaborator

mindforger commented Jun 27, 2018

there seems to be an issue with journeymap when using the server side version, it seems to be built from an newer forge version, using it with another forge version may trigger this issue, if you don't strongly need the server side of journeymap you can try disabling until it gets updated

TeamJM/journeymap#42
TeamJM/journeymap#54

at least that is what i understand from those issues

@fscan fscan closed this in #3569 Jun 28, 2018

fscan added a commit that referenced this issue Jun 28, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment