Mac OSX Installation

Jan 15, 2022
Mac OSX Installation
  • Spigot Installation: Mac

    A quick guide to downloading Spigot for Mac (OSX)

    Spigot has many ways of being decompiled on Mac, no Windows, no Linux, but this method will mention one of them, probably the easiest and most familiar.

    1. Download the latest BuildTools.jar file from the Spigot Jenkins page.

    Download the file here

    2. Take your build tools file and place it in a separate folder on your Mac
    3. Open up TextEdit and type in the following:

    For MacOS with bash
    Code (shellscript (Unknown Language)):

    cd "$(dirname "$0")"
    exec java -Xms1G -Xmx1G -jar minecraft_server.jar nogui
    For MacOS with Catalina/Big Sur
    Code (shellscript (Unknown Language)):

    cd "$(dirname "$0")"
    exec java -Xms1G -Xmx1G -jar minecraft_server.jar nogui
    You don't necessarily need TextEdit, in fact, TextEdit is a pretty terrible text editor. This code shown above is Shell Script, which is litterally a scripting language made for your bash/terminal. Kind of odd if you ask me.

    4. Save the following to the same folder as your BuildTools.jar as build.command

    I made up build.command, you can use anything, as long as it ends in .command. .command is an extension for shell script. When you double click it, it automatically runs in terminal. With the normal shell script (.sh extension), you have to put it into a script, save it, then drag it into terminal and hit enter to run it. That's why we use .command when working with server JARs

    5. Now the tricky part.
    • Open terminal
    • Type chmod a+x with a space after it. DON'T HIT ENTER
    • Drag in the build.command file. Hit enter.

    What this does is grants you permission to open up build.command. We drag the file in, because it automatically writes out the directory for you, otherwise, you'd need to type out the entire directory (not fun)

    6. Now for the easy part. Double click your build.command file. It should take 5-10 minutes for the entire BuildTools file to decompile, but when it does, you'll find a craftbukkit and spigot JAR in your directory. Yay!

    Congratulations, you've just started to decompile build tools. Nope, no windows required.


    MacOS complains after double clicking start.command stating that the file is corrupt:

    This occurs when you (accidentally) write bash instead of sh in the script. Apple then puts your script into quarantine and you manually need to remove it from there in order to run it correctly.
    View quarantine: xattr -l /PATH/TO/
    Delete from quarantine: xattr -d /PATH/TO/
    More info here.
    Note that you have to repeat this process every time Mac tells you the file is corrupt.

    Script starts but "Permission denied" error when the script accesses the jar file:

    Step 5 should have solved that issue but you can also grant yourself and 'root' access to the file with sudo chmod 755 /PATH/TO/

    Things to note:

    While your file is decompiling, do NOT disrupt it in any way. I once closed ForkedBooter during the process, because it looked suspicious (I didn't know at the time that it was actually part of the Maven software, I thought it was a virus). Big mistake. I had to start ALL over again, re decompiling, which is easy, you just reopen build.command (you just have to wait 5-10 extra minutes).

    So as you know, ForkedBooter isn't a virus. If you see any suspicious programs however, just leave a comment, and I'll tell you if it's part of Maven or not.

    Quick mention before this guide ends: Maven is a software API used for just about anything in Java, including Bukkit and Minecraft.

    Lastly, if you want to learn how to set up an actual server, you can follow this custom guide, or you can follow the minecraft wiki guide (shows you how to set up a vanilla server, but basically it's the same thing)

    1. Open text edit, or the text editor you like
    2. Type this in:
    cd "$(dirname "$0")"
    exec java -Xms1G -Xmx1G -jar minecraft_server.jar nogui

    3. Save this in the folder your spigot.jar is in as start.command
    4. Open terminal
    5. Type chmod a+x with a space after it. DO NOT HIT ENTER
    6. Drag in start.command
    7. Hit enter
    8. Open start.command
    9. The server will stop, and say you need to accept the EULA. Open eula.txt in your server folder. Change eula=false to eula=true
    10. Re open the server
    11. No, I won't give a guide on port forwarding, sorry :/

    NOTE: Sorry about Custom guide, there's something bugging it that won't allow me to make a single one
  • Loading...
  • Loading...