Simplify build process about altoclef HOT 3 CLOSED

This is only true for Fabritone.
I think it's better to focus on #36 and solve this(#41) issue in that way...

from altoclef.

Well not really, the issue is that fabritone/baritone would be included as a SEPARATE jar. Your mods folder should look like this:

mods
- alto-clef-SNAPSHOT.jar
- baritone-1.16.jar
- other potential jar files also must be put here!

However, when you run build in the altoclef project, it only generates the alto-clef-SNAPSHOT.jar, not the other jars. Doesn't matter if the separate project is using fabritone or baritone. The user should have easy access to those jars when building, otherwise every time they want to test it online they have to open up the project that can build baritone-1.16.jar AND also locate all the other dependencies that I may add in the future. That's no fun, and I'd like to fix that before making an official build/release.

from altoclef.

Shadow works with extra libraries, but the baritone jar is still needed and I couldn't figure out how to package it together.

Will abandon this idea for now, as external libraries can now be added without changing the build process.

from altoclef.