Fixed AE2 integration when AE2's channels are disabled #3134
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.
I believe I properly fixed the issue referenced in #3090
The previous fix did not seem to correctly fix the issue, and resulted in a
NoSuchElementException
being thrown when attempting to connect an adapter to an AE2 ME Interface, when AE2's channels were disabled. Controllers don't exist when channels are disabled, thus the exception.Prior to that commit, it checked if ME Controllers exist before defining the integration for both ME Controllers and ME Interfaces. For controllers this check was necessary, but not for interfaces. The fix removed the checks from both.
By re-implementing the check only when defining ME Controllers, this fixed the exception and allows ME Interfaces to be used when channels are disabled.
Sorry for the potentially poor description!