Describe the bug

Hello Everyone,
The Issue i am having is related to me removing the mod out of the Modpack after deciding that it would not fit the idea i had with how my modpack is supposed to be played.

How to reproduce the bug

The way i was able to Produce this bug is by simply making a modpack, adding Ae2 (V1.19.2) and then removing the mod again. After removing the mod i was no longer able to launch the modpack without Error Code -1

Expected behavior

.

Additional details

i dont know if this is just an issue with my modpack or if this happens if you only install AE2 alone and do the same procedure

Which minecraft version are you using?

1.19

On which mod loaders does it happen?

Forge

Crash log

https://pastebin.com/PqtvEEq8

Your error report does not even mention AE2. It mentions iris ( java.lang.IncompatibleClassChangeError: class net.coderbot.iris.gui.option.ShadowDistanceOption cannot inherit from final class net.minecraft.client.OptionInstance)

to be clear here i have never installed Iris on this modpack. Im actually confused on why that shows up on the crash logs as this is forge and Iris is on Fabric and like i said before the modpack has never EVER interacted with Iris before.
One last note is that this Crash report occurs after AE2 is Deleted from the modpack and the modpack works again after reinstalling AE2 so Clearly it has something todo with AE2
but it might have something todo with Oculus which is a Port from Iris ill do some Testing

Your error report does not even mention AE2.
It mentions iris (
java.lang.IncompatibleClassChangeError: class net.coderbot.iris.gui.option.ShadowDistanceOption cannot inherit from final class net.minecraft.client.OptionInstance)