You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally I would append the -Ddiscordfix=" net.minecraft.client.main.Main " to the end of the java launch arguments to allow discord to detect Minecraft as a game.
While I am able to set the Java Arguments Globally or per Instance, I noticed that doing so would cause Minecraft to launch in vanilla. Checking the logs shows that the first line when launching the game is
After messing around more with the settings, I came to the conclusion that all custom java launch arguments are placed before the necessary arguments for the forge to launch properly.
Request: The ability to choose to add the java arguments after the forge launch arguments
The text was updated successfully, but these errors were encountered:
Normally I would append the
-Ddiscordfix=" net.minecraft.client.main.Main "
to the end of the java launch arguments to allow discord to detect Minecraft as a game.While I am able to set the Java Arguments Globally or per Instance, I noticed that doing so would cause Minecraft to launch in vanilla. Checking the logs shows that the first line when launching the game is
GDLauncher@N/A: Completely ignored arguments: [", -Dorg.lwjgl.util.Debug=true, cpw.mods.bootstraplauncher.BootstrapLauncher, --launchTarget, forgeclient, --fml.forgeVersion, 43.3.5, --fml.mcVersion, 1.19.2, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20220805.130853]
After messing around more with the settings, I came to the conclusion that all custom java launch arguments are placed before the necessary arguments for the forge to launch properly.
Request: The ability to choose to add the java arguments after the forge launch arguments
The text was updated successfully, but these errors were encountered: