Redstone Requester: Packages fail to send from multiple containers when requesting same item in multiple slots

[eternurity]

Description

When the Redstone Requester is configured to request the same item across multiple separate slots (e.g., 2 slots each requesting 1 iron ingot for a total of 2), and the item is stored across multiple containers, only the first container outputs the item's package fragment—other containers output nothing. The insufficient fragments cannot be merged by the Packager into a complete package matching the Requester’s configuration.

Expected Behavior:
All containers storing the target item should output the corresponding package fragments, and the Packager should merge all fragments into a complete package that exactly matches the Requester’s slot configuration.

Note: The request logic for different items is independent. For example, gold ingots may output normally from all containers as configured, while iron ingots still only output from the first container (issues with iron ingots do not affect gold ingot output).

Game Log

https://mclo.gs/SzB4whx

Debug Information

Reproduction Steps

Scenario 1: Iron ingots distributed + Gold ingots partially concentrated

1. Container setup: Container A has 1 iron ingot; Container B has 1 iron ingot + 2 gold ingots.
2. Requester configuration 1: 4 slots requesting "1 iron ingot, 1 iron ingot, 1 gold ingot, 1 gold ingot" in sequence.
3. Trigger the Requester and observe output:
   • Gold ingots: Container B outputs 2 gold ingots normally (split into 2 fragments with 1 gold ingot each);
   • Iron ingots: Only Container A outputs 1 iron ingot fragment; Container B outputs no iron ingots (the gold ingot fragments from B contain no iron ingots, and there are no subsequent iron ingot fragments).
4. Requester configuration 2: 3 slots requesting "1 iron ingot, 1 iron ingot, 2 gold ingots" in sequence.
5. Trigger the Requester and observe output:
   • Gold ingots: Container B outputs 2 gold ingots normally (a single fragment with 2 gold ingots);
   • Iron ingots: Only Container A outputs 1 iron ingot fragment; Container B outputs no iron ingots.

Scenario 2: Both iron ingots and gold ingots distributed

1. Container setup: Container A has 1 iron ingot + 1 gold ingot; Container B has 1 iron ingot + 1 gold ingot.
2. Requester configuration 1: 4 slots requesting "1 iron ingot, 1 iron ingot, 1 gold ingot, 1 gold ingot" in sequence.
3. Trigger the Requester and observe output:
   • Iron ingots: Only Container A outputs 1 iron ingot fragment;
   • Gold ingots: Only Container A outputs 1 gold ingot fragment;
   • Container B outputs no iron/gold ingot fragments;
   • Container A outputs 2 independent fragments (1 iron ingot, 1 gold ingot) in total.
4. Requester configuration 2: 3 slots requesting "1 iron ingot, 1 iron ingot, 2 gold ingots" in sequence.
5. Trigger the Requester and observe output:
   • Gold ingots: Containers A + B output 2 gold ingots in total (normal);
   • Iron ingots: Only Container A outputs 1 iron ingot fragment; Container B outputs no iron ingots.

Expected Behavior

• After triggering the request, all containers storing the target item output the corresponding package fragments;
• All output fragments can be merged by the Packager into a complete package that exactly matches the Requester's configuration.

Actual Behavior

• Only the first container storing the target item outputs the item's package fragment; other containers output nothing;
• The number of output fragments is insufficient, making it impossible to merge into a complete package matching the Requester's configuration via the Packager;
• The request logic for different items is independent (e.g., normal output of gold ingots does not affect iron ingots triggering the issue).