Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amidst can't run with custom non-Mojang launchers #761

Closed
user21944 opened this issue May 17, 2020 · 5 comments
Closed

Amidst can't run with custom non-Mojang launchers #761

user21944 opened this issue May 17, 2020 · 5 comments

Comments

@user21944
Copy link

I primarily use MultiMC to play Minecraft which does not save to .minecraft however because of this I can't start Amidst. It brings up an error of not being able to find .minecraft (which obviously doesn't exist). I don't know which files within there it needs but copying my saves and version JAR/JSON didn't work.

It most likely needs the files for instances but it would be nice if you could set up "custom" instances within Amidst using the path to a JAR and save directory. Otherwise I have to install Mojang's launcher just to use Amidst, which I don't want to have to do. I would really appreciate if this could be addressed.

@moulins
Copy link
Contributor

moulins commented May 17, 2020

Closing as duplicate of #126.


You can start "custom instances" from the command-line (see here), by specifying the -mcjar and -mcjson arguments. I've never tested it with MultiMC, but it should work as long as you have a vanilla Minecraft JAR.

@moulins moulins closed this as completed May 17, 2020
@conorthedev
Copy link

You can start "custom instances" from the command-line (see here), by specifying the -mcjar and -mcjson arguments. I've never tested it with MultiMC, but it should work as long as you have a vanilla Minecraft JAR.

This doesn't work for me
image

@moulins
Copy link
Contributor

moulins commented May 21, 2020

Oh, yeah, my bad; you also need to use the -mcpath option to specify the location of the MultiMC directory.
You'll have to add some dummy files at the root of the folder for Amidst to recognize it as a valid Minecraft directory:

  • an empty saves folder
  • an empty versions folder,
  • an empty launcher_profiles.json file.

@ghost
Copy link

ghost commented Jun 19, 2020

What do you mean the MultiMC directory?

I currently have my setup as java -jar amidst-v4-4.jar -mcpath /Users/alexis/Applications/MultiMC.app/Contents/MacOS/instances/1.16/ -mcjar /Users/alexis/Applications/MultiMC.app/Contents/MacOS/libraries/com/mojang/minecraft/1.16-rc1/minecraft-1.16-rc1-client.jar -mcjson /Users/alexis/Applications/MultiMC.app/Contents/MacOS/meta/net.minecraft/1.16-rc1.json.

I've also tried /Users/alexis/Applications/MultiMC.app/Contents/MacOS/instances/ and /Users/alexis/Applications/MultiMC.app/Contents/MacOS/instances/1.16/.minecraft/ for the mcpath and I keep getting the error `invalid '.minecraft' directory at: <one of the directories I've tried>.

Edit: Yes, I've created the empty file and folders too for each of them.

@moulins
Copy link
Contributor

moulins commented Jun 23, 2020

I'm talking about the <MultiMC root> directory mentionned here. In your case, it should probably bz /Users/alexis/Applications/MultiMC.app/Contents/MacOS/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants