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

Installation on Mac #44

Open
lschult2 opened this issue Jul 5, 2019 · 2 comments
Open

Installation on Mac #44

lschult2 opened this issue Jul 5, 2019 · 2 comments

Comments

@lschult2
Copy link

lschult2 commented Jul 5, 2019

I'm working on installing on a Mac (MacOS Mojave), and am having issues. I copied the files listed in README (into mods/ and mcpipy/), but that does not appear to be sufficient. Did I miss something?

I also tried running "sh build.sh", but get a syntax error on line 4.

I'm using the latest version of Minecraft and Forge: 1.14.3. It is a version compatibility issue? Does this only work on Minecraft 1.12.2 and lower?

@perfectlyGoodInk
Copy link

Yes. As far as I understand, it currently only works on 1.12.2 and lower.

@Marcinosoft
Copy link

Marcinosoft commented Jul 10, 2019

If you want to install mod for python coding or run samples - all you need to do is unpack:
https://github.com/arpruss/raspberryjammod/blob/master/mods.zip
into Minecraft mods folder (I assume that Minecraft and Forge are already installed). Zip contains RaspberryJamMod.jar for different MC versions, but up to 1.12.2. Forge will load jar from folder with name equal to MC version you'll launch.
Next copy
https://github.com/arpruss/raspberryjammod/tree/master/mcpipy
folder where you want to place python source codes. It means anywhere. From this folder you can run samples.

But if you want to develop code of this plugin in java, then build.sh is shell script to compile project into jar files for different MC versions, currently up to 1.12.2. If you have syntax error then probably your default shell (sh) is not able to handle for loop syntax. There is no shebang in first line, so you may add it by your own as very first line, specyfying for example bash:
#!/bin/bash
or run "bash" before running script or execute it like this:
bash build.sh

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

No branches or pull requests

3 participants