Skip to content

Latest commit

 

History

History
65 lines (43 loc) · 3.34 KB

develop.md

File metadata and controls

65 lines (43 loc) · 3.34 KB

Development Guide

Get it Running (IDE)

James Green's setup guide!

James Green's Intellij Setup video on YouTube

Text tutorial

Clone project and import. I'd suggest using JetBrain's IntelliJ to import the project. Make sure you're using jdk 16 in your Project & Gradle Settings!

  1. Open Intellij

Click File > New > Project from Version Control... image

  1. Copy + Paste the altoclef clone URL and Clone (find here: )image
  2. Go to File > Settings, search Gradle and make sure your Gradle JVM is set to a JDK that's version 16 (IntelliJ lets you download open source JDKs, any of those should be fine) image
  3. Go to File > Project Structure, then under Project Settings/Project make sure "Project SDK" is set to version 16 image
  4. On the right side of the screen open the gradle tab and navigate to Tasks/fabric/runClient. Click runClient image

If the gradle tab doesn't exist, try View > Tool Windows > Gradle

Get it Running (Command line)

  1. Git Clone project
  2. cd into cloned local repo
  3. sudo / doas chmod +x gradlew (skip this step if you are on windows)
  4. ./gradlew build or ./gradlew runClient

Modifying Baritone (dev mode)

Alto Clef uses a custom fork of baritone that gives you more control over how baritone works. If you wish to make edits to that fork you can do so locally if you follow these steps:

  1. Clone The baritone fork into the same directory containing altoclef. For example, if you cloned altoclef into your desktop, baritone should be in your desktop as well.
  2. Run gradle build within the fork you just cloned. You may open the folder in an IDE and run the build task.
  3. There should now be various .jar files starting with baritone in the following folder: baritone/build/libs
  4. Now within altoclef, pass -Paltoclef.development as a parameter when running gradle build (In IntelliJ, go to the build dropdown -> Edit Configurations, then duplicate the altoclef [build] configuration. In this duplicate, paste -Paltoclef.development into the Arguments text field.)
  5. When you build and pass -Paltoclef.development, Alto Clef should now use the jar file inside of your custom baritone fork instead of pulling from online. This lets you rapidly test local changes to baritone.

Task Development Guides

Task Programming Tutorial Stream

More Recent AltoClef Task Programming VOD

Old (Post Stream) Tutorial VOD

Rough AltoClef Tutorial VOD