I have been noticing a steady rise of cases whereby Mion's Auto-Installer doesn't seem to work, and although in some cases it is due to legacy residuals causing problems (e.g., the old Minecraft Launcher, Magic Launcher), in an overwhelming majority of cases it is due to the fact that the custom JVM arguments required to launch Gulliver Forged do not get added to the new profile. It's a mystery to me why this occurs (often rather inconsistently), and although I'm quick to blame Windows on it (since it's almost always on a Windows box that these issues get reported), it could very well be a Minecraft Launcher update that is interfering with Mion's Auto Installer.
In the meantime, I have updated my Auto-Installer guide to urge a review of the JVM arguments before continuing...
https://www.dropbox.com/s/958pdolca8sqo55/Gulliver162Installation_ForgeAutoInstaller.pdf
When helping new players install Gulliver, should they have issues getting Gulliver Forged to launch (even after carefully reviewing the guide), always be sure to have them check whether their Launch profile looks exactly like the below image, with the line:
-XMx1G -Dfml.ignorePatchDiscrepancies=true
...clearly typed in the JVM Arguments line.
Thank you. ^^
If you are having trouble still try this JVM Argument:
ReplyDelete-Dfml.ignoreInvalidMinecraftCertificates=true -Dfml.ignorePatchDiscrepancies=true