Potions won't be pulled by logistical pipes from chests
AallynReed opened this issue · 5 comments
Issue description
I am trying to pull from chests potions to automate brewing stands but it just won't do it
Steps to reproduce
Minecraft version
1.16.x or earlier (No longer being developed)
Forge version
36.2.34
Mekanism version
Older
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
No response
Healing I potions...but ye I am sorry I bothered you with an old version I
managed to get it working using logistical sorters
… Message ID: ***@***.***>
Which potions in particular are you trying to insert? I am testing this in 1.18 (as we are no longer actively developing for 1.16) and I am unable to reproduce this.
Yeah I am not able to reproduce this in 1.18 so I am going to go ahead and close this as if I had to guess even in 1.16 it might only happen as some sort of mod interaction. presuming you are on the latest 1.16 version. (10.1.2)
Have you tested other input methods, say using the RS exporter to make sure it'll take input from the front like you want?
I actually solved this problem another way.
While it still persists as originally attempted, I've gone ahead and used
logistical sorters, however it didnt pull potions either, not until I
ticked the "single" option.
But before doing so, I went on creative and attempted to pu from 1 chest,
over to another, no RS involved, I put 1 glowstone and 3 healing potions,
connecting the 2 chests I placed a logistical pipe, set it to pull on the
chest with contents, push on the chest without them, and it had only moved
the glowstone, once again failing to move.
Then I tested my current setup which ill drop a screenshot later, using
logistical sorters, this works with some filters and that single option
ticked on, nothing else required.
…On Mon, May 9, 2022, 05:44 leadwolf32 ***@***.***> wrote:
Have you tested other input methods, say using the RS exporter to make
sure it'll take input from the front like you want?
—
Reply to this email directly, view it on GitHub
<#7472 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJFO3OC2GUOMQRLZAD5TODVJCJ2DANCNFSM5VL2PJ6Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>