Closed Jack-McKalling closed 2 years ago
Thanks for reporting!
When following your steps, the item in the chest is (correctly) not moved, so it seems I can not reproduce your problem. Can you try again and double-check the steps to reproduce? If you can still reproduce it, please share a minimal world with me.
Strange, that you cannot reproduce it. I just created a blank world with the exact setup and it still happens exactly the same. World download: Spooky Action At A Distance.zip
Dynamics: 1.9.4 Tunnels: 1.8.6 Core: 1.11.9 CC: 2.7.0 Minecraft: 1.16.5 Forge: 36.2.5
Thanks, managed to reproduce it. Looks like it is related to a recent Forge version.
Issue type:
Short description:
An Item Interface doesn't need to be attached to a Logic Cable in its own blockspace (as long as its blockspace is adjacent to a Logic Cable) for it to be targetable by an Item Exporter. Eventhough you cannot open it for configuration.
Steps to reproduce the problem:
Video: https://drive.google.com/file/d/1YzrSodjTQjp-OH0iTPpizWWYeO9aamxF/view?usp=sharing
Expected behaviour:
When a cable part doesn't connect to a network directly yet because it is missing a cable, I would expect it not to be able to perform its function.
Further testing:
It doesn't matter in which blockspace the Item Interface is placed, as long as that blockspace is adjacent to a Logic Cable of the network in question. Items are not transferred as intended if the Logic Cable is more than 1 block away. It seems that the Logic Cable requirement only applies to opening the part GUI, but not to the part's function, as long as it would connect to the network if it had a Logic Cable of its own.
Versions:
Log file: