Error in the transport system

Question

Error in the transport system

ArturilloD opened this issue 4 years ago · 7 comments

ArturilloD commented 4 years ago

The pipes eject the transported elements out of the system, it occurs when the pipes try to insert items into a container and I don't know very well if it is because it is already full or something similar, then it seems as if I wanted to return to the place of origin, although instead it's like the pipes have an element limit or something like that and instead of going into the container they just fly (literally) out of the system and float to the ground. If you require it then I could send you a video. Regards

ArturilloD · Answer 1 · 2020-08-31T15:45:14.000Z

I have tested it with the stack limiter module and unless small numbers are entered that continues to happen El lun., 31 ago. 2020 a las 17:03, Ellpeck (<[email protected]>) escribió:

…

Closed #35 <#35>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APPCIAWOWNG44PPTWVBSLO3SDO3VTANCNFSM4QQTRUPA> .

Ellpeck · Answer 2 · 2020-08-31T15:49:12.000Z

When using the stack limiter module with a higher amount than the items' maximum stack sizes, the extraction/retrieval module used to insert into the containers also needs to prevent over-sending. If that is the case for you, and the issue still occurs, then please re-open this issue.

Ellpeck · Answer 3 · 2020-08-31T15:03:38.000Z

You need to use modules that prevent over-sending. The description of the modules states if they do, so you can just search "over" in Just Enough Items (if you have that installed) to find all the ones that prevent over-sending.

ArturilloD · Answer 4 · 2020-08-31T16:55:49.000Z

I think I have discovered what happens, apparently it is with the Workbench Factory (https://www.curseforge.com/minecraft/mc-mods/workbench-factory), it has the exit slot and they do not allow you to enter items, the others do not work, since the output item is different from the input item, so they end up jumping. Demo video: https://youtu.be/XQ51T-voYAY By the way, as a note or suggestion is to say that the ender chests cannot be connected to the pipes. Greetings and thanks El lun., 31 ago. 2020 a las 17:49, Ellpeck (<[email protected]>) escribió:

…

When using the stack limiter module with a higher amount than the items' maximum stack sizes, the extraction/retrieval module used to insert into the containers also needs to prevent over-sending. If that is the case for you, and the issue still occurs, then please re-open this issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APPCIASX5J6UGQZCTP5TX53SDPBAPANCNFSM4QQTRUPA> .

ArturilloD · Answer 5 · 2020-09-02T14:52:59.000Z

The problem persists. To replicate it is very simple with Storage Drawers ( https://www.curseforge.com/minecraft/mc-mods/storage-drawers), since the drawers do not accept a lot of variety of items. Steps to reproduce it: 1.- Put a chest with different items and to make it faster that they are not stackable or put one or two of each one. 2.- Put several drawers connected to that chest. 3.- Send those elements to the drawers. 4.- Cut the outlet pipe of the chest when some items have come out. END - At that moment the elements that are in the pipe will jump out. Why it occurs: The collapse occurs since several elements go out towards the same chest / drawer, then one type of item enters the drawer chest, then two things can happen here: 1.- The item cannot enter because that chest / drawer is already full or blocked because another type of item cannot enter 2.- The outlet box is full or the pipe no longer exists and then the element has no "place to go" and jumps out of the system. How to solve it: The problem occurs when the element is blocked because where it was assigned to enter it cannot and then it returns to the original chest to be reassigned another destination, at that moment if the chest from which it has left is full the element jumps out of the system and is lost, a possible solution would be for that element to look for another chest / drawer where it could enter before returning to the original chest / drawer or not to leave without confirming that it will surely be able to enter, since that way it does not leave the slot empty and it doesn't allow you to enter any other element in its place, so that way you don't have a place to stay. El lun., 31 ago. 2020 a las 18:55, Arturo Beltrán Sánchez (< [email protected]>) escribió:

…

I think I have discovered what happens, apparently it is with the Workbench Factory ( https://www.curseforge.com/minecraft/mc-mods/workbench-factory), it has the exit slot and they do not allow you to enter items, the others do not work, since the output item is different from the input item, so they end up jumping. Demo video: https://youtu.be/XQ51T-voYAY By the way, as a note or suggestion is to say that the ender chests cannot be connected to the pipes. Greetings and thanks El lun., 31 ago. 2020 a las 17:49, Ellpeck ***@***.***>) escribió: > When using the stack limiter module with a higher amount than the items' > maximum stack sizes, the extraction/retrieval module used to insert into > the containers also needs to prevent over-sending. If that is the case for > you, and the issue still occurs, then please re-open this issue. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#35 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/APPCIASX5J6UGQZCTP5TX53SDPBAPANCNFSM4QQTRUPA> > . >

Ellpeck · Answer 6 · 2020-09-02T14:59:01.000Z

Just to confirm: You are using extraction/retrieval modules whose tiers prevent over-sending, that is: An extraction module of at least tier 3, or a retrieval module of at least tier 2, correct?

If you are not using modules of this kind, then the behavior you are describing is expected. If the input pipe no longer exists entirely, this behavior is expected regardless of the over-sending setting.

ArturilloD · Answer 7 · 2020-09-02T15:02:59.000Z

Right, it even happens by also putting a stack limiter El mié., 2 sept. 2020 a las 16:59, Ellpeck (<[email protected]>) escribió:

…

Just to confirm: You are using extraction/retrieval modules whose tiers *prevent over-sending*, that is: An extraction module of at least tier 3, or a retrieval module of at least tier 2, correct? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APPCIASUPXBVQUVPBWQUNH3SDZMULANCNFSM4QQTRUPA> .

Share to