When using a Remote Orderer on a chassis pipe, everything requested is rejected. For example, I use a remote orderer on a Logistics Chassis MkII connected to a Macerator. I request a stack of Cobblestone. The cobblestone are requested, but do not enter the Macerator, they just return to their chest. This occurs on all machines and chests I have tested (BC Objects, Forestry objects, Factorization objects)

Edit: Forge 6.6.0.515, Logistics pipes 83, 84, and 85

the pipe you click on to do the requests is not considered, so doing it on the actual pipe connected to the macerator won't work. Do it on another pipe.

On Feb 11, 2013, at 8:16 PM, charles7926 [email protected] wrote:

When using a Remote Orderer on a chassis pipe, everything requested is rejected. For example, I use a remote orderer on a Logistics Chassis MkII connected to a Macerator. I request a stack of Cobblestone. The cobblestone are requested, but do not enter the Macerator, they just return to their chest. This occurs on all machines and chests I have tested (BC Objects, Forestry objects, Factorization objects)

?
Reply to this email directly or view it on GitHub.

But that's still a bug, MrTJP.

i know its a "bug" but its been that way forever. Just throwing that out there.

On Feb 11, 2013, at 9:42 PM, Benedikt Ziemons [email protected] wrote:

But that's still a bug, MrTJP.

—
Reply to this email directly or view it on GitHub.

I remember being able to do this in previous versions.

Edit: Yep, just checked on a backup I have. Using Forge 6.5.0.489 and LogisticsPipes-MC1.4.6-0.6.9.74, I can click the remote orderer on a chassis MkII connected to a macerator and the cobblestone will enter the macerator and be macerated into sand. Doing the same on LogisticsPipes-MC1.4.7-0.7.0.85 the cobblestone is rejected from the macerator is sent back to its chest.

On Feb 11, 2013 9:47 PM, "MrTJP" [email protected] wrote:

i know its a "bug" but its been that way forever. Just throwing that out
there.

On Feb 11, 2013, at 9:42 PM, Benedikt Ziemons [email protected]
wrote:

But that's still a bug, MrTJP.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/520#issuecomment-13415764.

somewhere along the way i think, while fixing a bug to do with passive providers sinking more items than were requested, we change things to bounce un-requested items. When a chassi revives the items the remote orderer requested it finds that they are not able to be sunk by any module, and as such get bounced as undeliverable.

i thought this was about the bug where if you requested it from a crafting pipe, the item that THAT pipe crafts would be unavailable…

On Feb 11, 2013, at 10:04 PM, Andrew Hill [email protected] wrote:

somewhere along the way i think, while fixing a bug to do with passive providers sinking more items than were requested, we change things to bounce un-requested items. When a chassi revives the items the remote orderer requested it finds that they are not able to be sunk by any module, and as such get bounced as undeliverable.

—
Reply to this email directly or view it on GitHub.

Pretty sure this is the same change that prevents passive suppliers from oversupplying their attached inv...
I guess we could just check if the item arriving at a chassi destination is activerouted, and if so unconditionally try to sink it (no chassi module can actively request things, so by exclusion anything activerouted to it must have been from remote ordering on it).

The above setup works on latest dev branch, the chest contains ore and requesting that ore at the chassis inserts the ore into the macerator. Was it fixed at some point in 2020-21?

Probably. Thanks for checking!

The above setup works on latest dev branch, the chest contains ore and requesting that ore at the chassis inserts the ore into the macerator. Was it fixed at some point in 2020-21?