Description

Please reference these images:

What is expected: If in 'config' I have 16 'essences', and I remove 16 from the system, it should always replenish the min 16 I have configured.

Actual behaviour: I'm unsure what exactly triggers this, but please see the images I provided. What is expected does function sometimes, but often not. For example, if I remove a higher tier 'essence', the AE system uses the lower tier 'essence' to create the new one. This means it also removes the lower tier essences inside the ME Interface (that were crafted to match my configured minimum. This is good and desired!). However after the system created the higher tier essences, the lower tier essences do not replenish to their desired configured minimums! This negates the elegant design and point of the system.

Oddly enough, if I left-click on the blank section (2nd picture in the link I gave above you will see on the left 16 of a green essence and a blank slot below it. I have to manually click the blank slot to force the ME interface to notice nothing is there. It then starts creating 16 more, as you see in the third picture) under where the low tier essences should be replenishing, this finally triggers the ME Interface to notice that nothing is there, and only then starts to automate itself again. (There seems to be a need for a check every so often and this forces a check where none are present). Unfortunately, outside methods to force the ME Interface to check itself (lever to Redstone turning on and off) aren't working, but those would only be workaround anyway.

Suggestion:
Have the ME Interface check itself every few seconds if it needs to be doing something. Whatever trigger that is happening now is missing something.

Environment

I did this in a very simple SP creative world connecting a ME Interface to an ME Storagebus. I will link a video of what I do to better illustrate the issue. This is also present in my MP server in project ozone lite.

• Minecraft Version: 1.10.2
• AE2 Version: rv4-stable-1
• Forge Version: 12.18.3.2422

I found a work around that gave (me at least) more insight into the issue.

*** Workaround ***
Do not place items you want to keep a certain amount of in the same ME Interface config as another item that will directly use it in its own recipe.
Example going back to the essences again. Lets say 4 green essence can create 1 red essence. You do not want to keep a green essence config and a red essence config in the same ME Interface. Because when a red is removed, it will directly remove the green essence inside the config first, and then wont replenish.

This makes me think there is only one check that happends during this time and the fact that there is no longer any greens left is forgotten during that check. Seems to be fixable with one if then or && line added possibly being missed in the code?