Post by Roadhog360 on Jul 20, 2020 17:59:12 GMT -5
How to Install New Frontier Craft 1.8.7_02(_01) on a Server
If you run into any issues, are stuck, or have any questions, contact us on our Discord server!
discord.gg/HvGx8vE
Patching CraftBukkit
Part 1: Preparing the CraftBukkit jar to patch
The first file you'll need is obviously a vanilla CraftBukkit jar. Build 1060 is used, and that one's recommended, we cannot guarantee other builds will work.
Unfortunately due to legal issues we cannot provide a download to this. Simply Google something along the lines of "Minecraft CraftBukkit 1.7.3 1060".
Canyon and other derivatives of 1060 WILL NOT WORK!
The jar should have a SHA-256 hash of aa7e750cea03b1fd9e0feb3c2214a7f5d18fee5677fd39ec7784f3a9f820eb28 & an MD5 hash of 3a7c88414eb684d5a582b6c53ce23296
Then, you'll want to download this file: files.gamebanana.com/bitpit/nfcpatch_187_01_s1_b257f.xdelta
If this opens a page full of confusing text, right click it and save it.
After that, go to your OS below and use the guide to setup an application called 'xDelta', to patch your jar.
Windows:
NOTE: 7-Zip (Recommended) or WinRAR may be required to extract the files from the .rar below!
Download and extract the xDelta GUI here from the .zip to a folder: github.com/marco-calautti/DeltaPatcher/releases
If you want to use the command line instead, grab this .exe instead: github.com/LO6AN/New-Frontier-Craft/blob/master/runtime/bin/xdelta3.exe
Linux:
Simply run the following commands:
Note that some distros of Linux may not use 'apt'. For example, on Red Hat, Fedora and CentOS, replace 'apt' with 'yum'.
macOS:
Install Homebrew to get the 'brew' command needed for the next step: brew.sh/
Now run this command:
Part 2: Patching the jar
Now, for the best part. Let's make this boring old vanilla Bukkit 1.7.3 jar into an NFC jar!
Windows:
If you choose to use the command line version and downloaded that, open the folder with CMD or PowerShell(Untested).
Then go to the Linux/MacOS portion of the guide and run the command but instead of "xdelta3" type "xdelta3.exe"
For 'original file', select the vanilla Bukkit jar, for 'patch file', select the .xdelta file you downloaded in the last step of part 2.
Open the xdeltaUI.exe, make sure you're in the 'xDelta Patch' tab.
Now, for the output, it can be named anything you want, but you must add the .jar suffix to the file name manually, it will not be added for you.
Linux/MacOS:
Open a terminal and use 'cd' to navigate to the folder your files are in.
Run the command below, where 'bukkit' is for whatever your bukkit jar is named, 'nfcpatch' for whatever the .xdelta patch is named, and 'jarname' for what you want your server jar to be named. File paths work too.
Do not erase the quotation marks, this ensures the command runs with no errors regardless of the file name or path.
If you came here from the Windows guide, remember to change "xdelta3" to "xdelta3.exe" before running this.
Running the Jar
Windows:
NOTE: 7-Zip (Recommended) or WinRAR may be required to extract the files from the .rar below!
Download and extract the xDelta GUI here from the .zip to a folder: github.com/marco-calautti/DeltaPatcher/releases
If you want to use the command line instead, grab this .exe instead: github.com/LO6AN/New-Frontier-Craft/blob/master/runtime/bin/xdelta3.exe
Linux:
Simply run the following commands:
sudo apt update |
sudo apt install xdelta3 |
macOS:
Install Homebrew to get the 'brew' command needed for the next step: brew.sh/
Now run this command:
brew install xdelta |
Part 2: Patching the jar
Now, for the best part. Let's make this boring old vanilla Bukkit 1.7.3 jar into an NFC jar!
Windows:
If you choose to use the command line version and downloaded that, open the folder with CMD or PowerShell(Untested).
Then go to the Linux/MacOS portion of the guide and run the command but instead of "xdelta3" type "xdelta3.exe"
For 'original file', select the vanilla Bukkit jar, for 'patch file', select the .xdelta file you downloaded in the last step of part 2.
Open the xdeltaUI.exe, make sure you're in the 'xDelta Patch' tab.
Now, for the output, it can be named anything you want, but you must add the .jar suffix to the file name manually, it will not be added for you.
Linux/MacOS:
Open a terminal and use 'cd' to navigate to the folder your files are in.
Run the command below, where 'bukkit' is for whatever your bukkit jar is named, 'nfcpatch' for whatever the .xdelta patch is named, and 'jarname' for what you want your server jar to be named. File paths work too.
Do not erase the quotation marks, this ensures the command runs with no errors regardless of the file name or path.
If you came here from the Windows guide, remember to change "xdelta3" to "xdelta3.exe" before running this.
xdelta3 -d -s "bukkit.jar" "nfcpatch.xdelta" "jarname.jar" |
Running the Jar
Is NFC your first server jar and you have no idea how to run this thing? Don't worry, we got you!
NOTE: If you already know how to run a server jar, skip parts 1 and 3, but DO NOT skip part 2! It's important to NFC!
With part 2, check it every time you make a new server jar, just in case we've updated the dependencies.
Part 1: Downloading Java
If you already have 64-bit Java, you can skip this step.
Go to this website: www.java.com/en/download/manual.jsp
Download the one for your operating system. (If you're on Windows, you want the 'Offline' versions)
If you've got a 64-bit system, it's highly recommended you get the 64-bit version to be able to allocate more RAM to Minecraft if needed.
Part 2: Setting up dependencies
Create a folder named 'lib' in the folder you want your server jar to run in.
Download this: files.gamebanana.com/bitpit/lib.zip
... And extract the contents of it to the 'lib' folder you created.
... And extract the contents of it to the 'lib' folder you created.
If you have an existing NFC server, the dependencies haven't changed since 1.8.7. So if your server is for NFC 1.8.7 or newer, you can skip this step, as you already have all the dependencies you need.
Part 3: Running the jar
Now, we'll need to create a script to run our server.
First of all, if you're running on Windows, it's recommended you go to your file explorer, view, and then untick the option to hide file extensions.
For Windows, create a ".bat" file with any name. For Linux, create a ".sh" file with any name, and for macOS, create a ".command" file
Make sure you create it in the same folder that your jar is in.
Copy the following arguments into it, where "jarname" is replaced with what you named the server jar.
Windows | java -jar -Xmx4G -Xms4G -Duser.language=en "jarname.jar" |
Linux | java -Xmx4G -Xms4G -Dfile.encoding=UTF8 -jar -Duser.language=en "jarname.jar" |
MacOS | exec java -Xmx4G -Xms4G -Dfile.encoding=UTF8 -jar -Duser.language=en "jarname.jar" |
The numbers before the "G"s are the amount of gigabytes of RAM used. I use 4 gigabytes in this example. You can change this to any number you want, or you can change the "G" to an "M" for megabytes instead.
Now, run it, and there you go! If everything worked out the server should be up and running, and /version should mention it's a custom NFC build of Bukkit.
If you're on Linux, and you're running the .sh with a GUI instead of the terminal, edit the file's properties, tick 'Allow executing files as program' and then when running it, click 'run in terminal'.
If you get some sort of error after launching, something about file utils, be sure the 'lib' folder is in the same folder as your jar and has all the libraries in it.
If you're on Linux, and you're running the .sh with a GUI instead of the terminal, edit the file's properties, tick 'Allow executing files as program' and then when running it, click 'run in terminal'.
If you get some sort of error after launching, something about file utils, be sure the 'lib' folder is in the same folder as your jar and has all the libraries in it.