Minecraft MCMA + Fabric

  • 57 Views
  • Last Post 17 March 2019
fixer117 posted this 17 March 2019

Hi! I've been running a snapshot server via MCMA 2 for a month now just fine. I recently decided to switch to Fabric to handle commands past base vanilla minecraft, however I ran into an issue that occurs on startup when adding the fabric-loader jar aside minecraft in the custom-opts=

joptsimple.UnrecognizedOptionException: X is not a recognized option

at joptsimple.OptionException.unrecognizedOption(OptionException.java:108) ~[?:?]

My JVM Argument list is as follows:

-server -XX:MaxGCPauseMillis=500 -XX:ParallelGCThreads=10 -XX:+UseStringDeduplication -XX:+UseAES -XX:+UseAESIntrinsics -Xmn2560M -Xmx9G -Xms4096M -XX:UseSSE=3 -jar fabric-loader-0.3.7.109.jar minecraft_server.jar

Order By: Standard | Newest | Votes
Mike posted this 17 March 2019

A lot of your flags are invalid. -server doesn't even apply to 64 bit system at all.

What you should enter into MCMA2s customopts is:

-XX:MaxGCPauseMillis=500 -XX:ParallelGCThreads=10 -XX:+UseStringDeduplication -XX:+UseAES -XX:+UseAESIntrinsics -Xmn2560M -Xmx9G -Xms4096M -XX:UseSSE=3

But MCMA2 may not work properly with loaders as it was never designed to, you'd need to use MCMA3 for that.

fixer117 posted this 17 March 2019

So, I gave MCMA 3 a go, AMP and here's what I get. I've tried with and without arguments.

joptsimple.UnrecognizedOptionException: j is not a recognized option at joptsimple.OptionException.unrecognizedOption(OptionException.java:108) ~[?:?] at joptsimple.OptionParser.validateOptionCharacters(OptionParser.java:633) ~[?:?] at joptsimple.OptionParser.handleShortOptionCluster(OptionParser.java:528) ~[?:?] at joptsimple.OptionParser.handleShortOptionToken(OptionParser.java:523) ~[?:?] at joptsimple.OptionParserState$2.handleArgument(OptionParserState.java:59) ~[?:?] at joptsimple.OptionParser.parse(OptionParser.java:396) ~[?:?] at net.minecraft.server.MinecraftServer.main(MinecraftServer.java:867) [?:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0201] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0201] at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0201] at net.fabricmc.loader.launch.knot.Knot.init(Knot.java:347) [fabric-loader-0.3.7.109.jar:?] at net.fabricmc.loader.launch.knot.KnotServer.main(KnotServer.java:26) [fabric-loader-0.3.7.109.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0201] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0201] at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0201] at net.fabricmc.loader.launch.server.stagetwo.FabricServerLauncherStageTwo.launch(FabricServerLauncherStageTwo.java:172) [fabric-loader-0.3.7.109.jar:?] at net.fabricmc.loader.launch.server.stagetwo.FabricServerLauncherStageTwo.stageTwo(FabricServerLauncherStageTwo.java:78) [fabric-loader-0.3.7.109.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0201] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0201] at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0201] at net.fabricmc.loader.launch.server.FabricServerLauncher.setup(FabricServerLauncher.java:99) [fabric-loader-0.3.7.109.jar:?] at net.fabricmc.loader.launch.server.FabricServerLauncher.main(FabricServerLauncher.java:55) [fabric-loader-0.3.7.109.jar:?]

Mike posted this 17 March 2019

Your java arguments are still wrong. "joptsimple.UnrecognizedOptionException: j is not a recognized option" - put AMP into debug mode (Monitoring.LogLevel=0 in AMPConfig.conf) and drop in what full set of arguments its passing to Java are.

Close