Powered machines not updating state correctly #1006
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
State was only being updated when canUse returned true. This meant that if the state changed so that canUse went from true to false the state change was not applied.
An example of this occurring is turning on 'only active with redstone signal'. This results in canUse returning false so the the check fails and the state update is not made. This results, for example, the StirlingGen block still showing its active 'running' block on the client when it has been disabled.
Checklist