Almura SDK

Prerequisites

• Java 7
• Gradle 2.1+

Cloning

To clone AlmuraSDK, simply run git clone git@github.com:AlmuraDev/AlmuraSDK.git

Setup

Note: If you do not have Gradle installed then use ./gradlew for Unix systems or Git Bash and gradlew.bat for Windows systems in place of any 'gradle' command.

For Eclipse

1. Run gradle setupDecompWorkspace --refresh-dependencies
2. Make sure you have the Gradle plugin installed (Help > Eclipse Marketplace > Gradle Integration Plugin)
3. Import AlmuraSDK as a Gradle project (File > Import)
4. Select the root folder for AlmuraSDK and click Build Model
5. Check AlmuraSDK when it finishes building and click Finish

For IntelliJ

1. Run gradle setupDecompWorkspace --refresh-dependencies
2. Make sure you have the Gradle plugin enabled (File > Settings > Plugins).
3. Click File > Import Module and select the build.gradle file for Almura.

Running

Note: The following is aimed to help you setup run configurations for Eclipse and IntelliJ, if you do not want to be able to run AlmuraSDK directly from your IDE then you can skip this.

For Eclipse

1. Go to Run > Run Configurations.
2. Right-click Java Application and select New.
3. Set the current project.
4. Set the name as AlmuraSDK (Client) and apply the information for Client below.
5. Repeat step 1 through 4, then set the name as AlmuraSDK (Server) and apply the information for Server below.
   5a. When launching the server for the first time, it will shutdown by itself. You will need to modify the server.properties to set onlinemode=false and modify the eula.txt to set eula=true (this means you agree to the Mojang EULA, if you do not wish to do this then you cannot run the server).

For IntelliJ

1. Go to Run > Edit Configurations.
2. Click the green + button and select Application.
3. Set the name as AlmuraSDK (Client) and apply the information for Client below.
4. Repeat step 2 and set the name as AlmuraSDK (Server) and apply the information for Server below.
   4a. When launching the server for the first time, it will shutdown by itself. You will need to modify the server.properties to set onlinemode=false and modify the eula.txt to set eula=true (this means you agree to the Mojang EULA, if you do not wish to do this then you cannot run the server).

Client

Property	Value
Main class	GradleStart
VM options	-Xincgc -Xmx1024M -Xms1024M -Dfml.coreMods.load=net.malisis.core.asm.MalisisCorePlugin,com.almuradev.almurasdk.core.AlmuraSDKCoreMod
Working directory	./run (Included in project)
Module classpath	AlmuraSDK (IntelliJ Only)

Server

Property	Value
Main class	GradleStartServer
VM options	-Xincgc -Dfml.ignoreInvalidMinecraftCertificates=true -Dfml.coreMods.load=net.malisis.core.asm.MalisisCorePlugin,com.almuradev.almurasdk.core.AlmuraSDKCoreMod
Working directory	./run (Included in project)
Module classpath	AlmuraSDK (IntelliJ Only)

Building

Note: If you do not have Gradle installed then use ./gradlew for Unix systems or Git Bash and gradlew.bat for Windows systems in place of any 'gradle' command.

In order to build AlmuraSDK you simply need to run the gradle command. You can find the compiled JAR files in ./build/libs but in most cases you'll only need 'almura-x.x-xxxx.jar'.

FAQ

Why do I get javac: source release 1.7 requires target release 1.7 in IntelliJ when running the client configuration?

Sometimes another project can mess with the settings in IntelliJ. Fixing this is relatively easy.

1. Go to 'File > Settings'.
2. Click the drop down for 'Compiler' on the left-hand side and select 'Java Compiler'.
3. Select AlmuraSDK and set the 'Target bytecode version' as '1.7'.
4. Click Apply and OK and try running it again.

Why do I get Zip file rt.jar failed to read properly in IntelliJ?

This is the result of Forge attempting to classload the Java runtime JAR, overall it is not an error that will cause any harm to your development and should be ignored.

A dependency was added, but my IDE is missing it! How do I add it?

If a new dependency was added, you can just restart your IDE and the Gradle plugin for that IDE should pull in the new dependencies.

Help! Things are not working!

Some issues can be resolved by deleting the '.gradle' folder in your user directory and running through the setup steps again, or even running gradle cleanCache and running through the setup again. Otherwise if you are having trouble with something that the README does not cover, feel free to join our IRC channel and ask for assistance.