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

TE2 - Essentia storage in Subnets #384

Open
RohitMoni opened this issue Aug 7, 2019 · 3 comments
Open

TE2 - Essentia storage in Subnets #384

RohitMoni opened this issue Aug 7, 2019 · 3 comments

Comments

@RohitMoni
Copy link

Describe the bug
In AE2 you can create sub-networks via a storage bus attached to an interface. This gives the network on the storage bus side access to the inventories and storage on the interface side network.

This doesn't seem to work with Essentia storage via TE2. Specifically, importing essentia from a warded jar via an import bus doesn't work (doesn't do anything) if all the essentia drives are on a sub-net.

Steps to Reproduce
Steps to reproduce the behavior:

  1. Create a configuration similar to the second image shown below (Main network. Sub-network accessible via essentia storage bus attached to an ME interface. Storage on the sub-network. Import bus on the main network).
  2. Make sure the sub-network has an accessible / open essentia storage cell.
  3. Place a jar of essentia infront of the import bus.
  4. Nothing happens

Expected behavior
The essentia is imported into the storage cell on the sub-network.

Screenshots
Regular network (this works):
Using an import bus to import essentia into a drivebay with an essentia storage cell.
image

Essentia storage in a sub-network (this doesn't work):
Using an import bus to attempt to import essentia into a drivebay accessible via a subnetwork.
image

Version Information

  • Minecraft: 1.12
  • Forge: 14.23.5.2836
  • Applied Energistics: rv6-stable-6
  • Thaumcraft: 6.1.BETA26
  • Thaumic Energistics: 2.2.3
  • Modpack: FTB Revelations (with some lightweight additions like TE2)
@BrockWS
Copy link
Collaborator

BrockWS commented Aug 7, 2019

This isn't actually a bug as it hasn't actually been implemented since there is no "ME Essentia Interface". I might be able to come up with a different way but right now I have no ideas about it.

@RohitMoni
Copy link
Author

RohitMoni commented Aug 7, 2019

Oh, interesting. I was under the impression it worked for TE1, assumed that when TE2 was developed that was brought over as well.

Edit: See #151 and #124

@someguyfromdownthestreet

this is a necro but i figured out a way to do this, so if you have your essentia generation on the same subnet that your using for storage then you can just use an essentia storage bus on an infusion provider and it works, if you want to have the essentia generation somewhere else in the system then you need a 2 way system, you need the abova and you need a system on the main network using a storage bus filtered to every aspect facing a warded jar and then have an import bus on the subnetwork facing the jar (id recommend speed upgrades

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

No branches or pull requests

3 participants