-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TE Satchel + IItemHandler Mod Incompatibilities #20
Labels
Comments
MaxNeedsSnacks
changed the title
TE Satchels don't like having IItemHandler added to them
TE Satchel + IItemHandler Mod Incompatibilities
Apr 28, 2019
I'll look into it asap, thanks for reporting! |
(I'll give this a higher priority) |
Pushed a fixed release (2.2.1) to CurseForge, also requires a CyclopsCore update. For reference, all mod compacts can be disabled separately using the CommonCaps config file, just in case similar problems would arise in the future. |
Awesome, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue type:
Short description:
(Related issues: Direwolf20-MC/BuildingGadgets#280, Direwolf20-MC/BuildingGadgets#289, EnigmaticaModpacks/Enigmatica2Expert#1138)
Recently, a couple of users have recently reported a problem happening with the mod interaction between Thermal Expansion and other mods such as Dire's Building Gadgets or Better Builder's Wands. The problem ended up being closed as unresolved on the Building Gadgets tracker, but we whittled it down to there being some mod that interferes with Satchels and adds Item Handler Capabilities to them where there were none originally.
I went through all the mods in the pack (Enigmatica2Expert v1.62) and the only one I could really find which modified TE satchels at all was Common Capabilities. Now I'm not sure whether the issue actually lies with your mod in this case, but if not, I'm pretty sure I could just disable the Satchel capability in your mod's config and be done with it (most likely), but if this actually is a bug that can be fixed, I just wanted to let you know ^^
Steps to reproduce the problem:
from Direwolf20-MC/BuildingGadgets#289 (comment)
Expected behaviour:
The client should crash producing a log similar to this
Versions:
The text was updated successfully, but these errors were encountered: