Wired interface to autocrafting broken, wireless terminal works fine (in dimension) #2647

Closed
tekacs opened this Issue Nov 21, 2016 · 2 comments

Projects

None yet

3 participants

@tekacs
tekacs commented Nov 21, 2016 edited

In an RFTools dimension, interacting with the AE system in the overworld works fine, crafting works fine from a wireless terminal - but trying to craft from any wired, static terminal causes problems.

Description

Setup:

  • Quantum Network Rings in the overworld and in the dimension.
  • Wireless Access Point, pattern terminal, crafting terminal, interface terminal connected like this in the dimension.
  • The overworld is chunkloaded to cover the entire AE system and its subsidiaries.

Working cases:

  • Using a wireless terminal in the dimension, I can access items, initiate autocrafting and see crafting status fine.
  • Using the interface terminal in the dimension, I can see and manipulate recipes in everything, including all of the molecular assemblers.
  • Using any wired or wireless terminals for any purpose in the overworld works fine.

Broken cases:

  • If I attempt to initiate any kind of autocraft only from the wired pattern or crafting terminals, the interface GUI closes itself - no error appears in the server console or in the client interface.
  • If I attempt to see crafting status in the wired pattern or crafting terminals, the server crashes (but the client does not) with this crash log: https://gist.github.com/tekacs/c97c33a91a1f1ef51e9305db540f656a - seemingly crashing on this line
  • This also applies if I extend any of the cabling and put down a new terminal, or replace the existing ones. This persists across crashes/restarts.

Environment

All The Mods pack, version 1.46 (https://mods.curse.com/modpacks/minecraft/242462-all-the-mods)
Running in multiplayer with a server.

  • Minecraft Version: 1.10.2
  • AE2 Version: rv4-alpha-6
  • Forge Version: 12.18.2.2125
@tekacs tekacs changed the title from Terminal interface to autocrafting broken, wireless terminal works fine (in dimension) to Wired interface to autocrafting broken, wireless terminal works fine (in dimension) Nov 21, 2016
@yueh
Member
yueh commented Nov 22, 2016

It does call detectAndSendChanges() on an invalid container. Should clearly not happen and I cannot remember it ever happen with 1.7.10. Maybe mojang changed the order of updating a container and checking it for a valid one with 1.10?

@yueh yueh added the type-bug label Nov 22, 2016
@yueh yueh added this to the rv4 beta - 1.10 milestone Nov 22, 2016
@yueh yueh closed this in 86908b1 Dec 8, 2016
@JelmarG
JelmarG commented Dec 8, 2016

Related to 2347 perhaps?

@phit phit added a commit to Stonebound/Applied-Energistics-2 that referenced this issue Dec 19, 2016
@yueh @phit yueh + phit Fixes #2647: Prevent crafting status from crashing due to missing net…
…work.
92dacf4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment