Doesn't look like it is fixed.

-QA Testing-

New feature broke existing mechanic -> Prio= pre release QA.

Not fixed.
Chest cant hit full anymore the usual way by exact numbers.

Example:

chest is pulling display modules, 1 per tick and cannot add any more of them.
We cannot expect to ever get a 100% (floating point?) match on the load.

It should either:

a)

• throw the full state whenever it did not complete a pull request due to space limitations (items available to pull >0, pulled in tick = 0)
• reset the full state on a completed pull cycle (pulling >0 items)

or b)

• throw the full state on a fixed cargo limit, like 90%

or c)

• throw the full state whenever there is less than one space for the biggest item in config.

Presumably a) is the most practical solution, that covers almost every blockconfig, storage config.

Also adding T938 as separate bug report.

Gate update on manual interaction DID work for quite a while.

inventories will now send to connected activation/OR-blocks instead of adjacent
also the signal for full will be sent if a pull could not be done
and the signal for "ok" will be sent on pull otherwise

-QA Testing-

Fix confirmed:

New intended behavior:
Send a false to linked activators (link from chest, to activator) on every tick when:

• a pull could not be filled AND
• there were items to pull present

Send a true to linked activators (link from chest, to activator) on every tick when:

• a pull could be filled OR
• there were no items to pull present

Notes:

• this way the "false" is only sent when the cargo space really prevents the chest from doing its job to pull stuff. If there is nothing to do, there is no reason to alert a "full state"
• empty source chest, disables full detection,
• NO connected chest to pull from, also makes the test always succeed and send a "true"