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

Work out a way to "Full-block-ify" ME Interface P2P #90

Open
ChromaPIE opened this issue Nov 18, 2024 · 0 comments
Open

Work out a way to "Full-block-ify" ME Interface P2P #90

ChromaPIE opened this issue Nov 18, 2024 · 0 comments

Comments

@ChromaPIE
Copy link
Contributor

ChromaPIE commented Nov 18, 2024

First of all this is for NAE2 + AE2FCR.

Every ME Interface has targeted (wrenched, arrows on its sides) and non-targeted mode, but its P2P Tunnel, as a micropart, is born targeted, meaning that its ability to separate items and fluids to its different sides is lost, because it only has one side.

Can't you just use more P2Ps on one cable? Nah it's not the same thing. Check this:

Unlike replacing the cable and the P2Ps with an untargeted, separate mode ON ME Interface, obviously this will not separate items and fluid to one container that can't hold fluid, and the other one that can't hold items, because the two P2Ps are treated independently, so instead it tries to see if the container can hold both item and fluid, and if not, the auto-crafting sequence is dead, making it fatal when dealing with multiblock automations.

So I'd suggest a helper block (Interface Proxy?) that when you attach the output side of P2P Tunnel - ME Interface to it, it will function as all source Interfaces of the tunnel. Yes, that's exactly how the thing goes when you simply use the micropart P2P, but as you can tell, it's a full block. Besides being able to handle unlimited amount of patterns it has different sides to do the separation.

There might exist better ways to resolve this.

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

No branches or pull requests

1 participant