Impact Forge - Modpack Incompatibility

[TheWoolsinator]

Describe the bug Various bugs exist across interactions with multiple mods within the Technic 1.12.2 Modpack.

I will describe installation fixes I've found for a few mods in the hope that others can utilize my findings to stabilize Impact installs in unsupported environments (modpack installs).

To Reproduce Steps to reproduce the behavior:

1. Install a modpack in MultiMC
2. Use Impact installer to generate an Impact forge jar
3. Place Impact jar file into the MultiMC instance mods folder
4. launch
5. observe crash report
6. (if you are really bored, add and remove some of these fixes one by one and view all the layers of errors. some are not as straightforward to diagnose as others and produce some interesting output)

Expected behavior Expected behavior is to observe and work through crashes... since Impact is known to be incompatible with MANY mods that are used in nearly all modpacks.

Screenshots N/A

Game output

``` N/A ```

Crash report

``` N/A ```

Additional Client Info

- Impact Version: Tested with 4.6 - 4.9 - Using Optifine? No - Enabled mods: > 300 mods - Compatibility fixed mods: buildcraft, loliASM, foamFix, randomPatches, mixinBooter - Operating System: - Java Version:

Additional context I've fixed incompatibilities with a few mods by adjusting configs and load order. Some of the incompatibilities are related to Impact itself, and some others are related to the Baritone package within Impact. See below list of fixes:

1. Buildcraft -> Impact incompatibility (update cfg file in configs directory)
   • Set config objects.cfg::items.plug_facade to false
2. Mixinbooter -> Impact Incompatibility (change mod load order)
   • Ensure mixinbooter is first in load order by prefixing the filename with '!', Example: ('!mixinbooter...')
   • Move Impact jar to last in load order by prefixing the filename with 'z', Example: ('zImpact...' )
3. Loliasm -> Baritone Incompatibility (update cfg file in configs directory)
   • Set config loliasm.cfg::remapper.B:optimizeFMLRemapper to false
4. foamFix -> Baritone Incompatibility (update cfg file in configs directory)
   • Set config foamfix.cfg::coremod.optimizedBlockPos to false
5. randomPatches -> Baritone Incompatibility (update cfg file in configs directory)
   • Set config randompatches.cfg::B:patchMinecraftClass to false

Doing all of the above produces a (fairly) stable and usable installation of Impact on the Technic 1.12.2 modpack. It is also possible to use Baritone standalone (in lieu of Impact) with this configuration setup (sans the load order fix). These mod interactions are likely very similar or exactly the same across many modpacks, so I hope that this is helpful and informative for others facing the same challenges.

Thanks for reading, and good luck tweaking things!