search

MrTJP / ProjectRed

Redstone Engineering
MIT License
471 stars 182 forks source link

Comparators not updating on inventory status change of droppers or hoppers. (#1186 ?) #1705

Closed VorpalLemur closed 10 months ago

VorpalLemur commented 2 years ago

Describe the bug Comparators don't seem to update correctly on inventory status changes when reading droppers or hoppers, while they do seem to work with vanilla chests. May apply to other inventories, droppers and hoppers are just the ones I tested with.

This seems similar to bug 1186 which was marked as resolved by a tester who verified it worked with vanilla chests.

(issue encountered in the Create Above & Beyond modpack)

To Reproduce Steps to reproduce the behavior:

  1. Hook a comparator up to read the inventory level of a dropper or hopper. Hook a vanilla comparator up to the same block for comparison.
  2. Change the inventory level of the block... note that the vanilla comparator reacts, while the projectred one does not.
  3. In some instances I noticed the comparator suddenly did give a reading... it changed, but it didn't continue to react to inventory changes. Seemed to update when I placed a redstone dust or wire next to it. In no case was I able to get it to continuously update like a vanilla comparator.

Expected behavior Projectred comparator reacts in real-time to changes in inventory status of the block its monitoring, just like vanilla comparator.

Crash Log Required for crash. DO NOT paste the entire crash log here. Use pastebin or similar.

Versions

(sorry, I'm unable to resolve some of these names by looking at my mods list. I'm using the Create: Above & Beyond modpack (version 1.3.0))

Screenshots/Videos If applicable, add screenshots or video links to help explain your problem.

djmattyg007 commented 2 years ago

I'm experiencing a similar issue with the ProjectRed comparator working with the Factory Hopper from the Engineer's Decor mod. I'm playing the Enigmatica 6 modpack, where I've manually added Project Red.

MrTJP commented 10 months ago

Was fixed in 1.18 on CBM side (https://github.com/TheCBProject/CBMultipart/commit/c66f0d7b887c96997afa97146db3235c12a4059c)