Cracking the XP seed in Minecraft and choosing your enchantments.
- Original video tutorial
- Updated picture tutorial
- The UI is subject to change and may have updated since the tutorials
Download the latest zip file from the releases page and extract into a place you won't lose it, such as your Desktop.
If you're a Windows user, you should double-click the batch file in the bin folder. Batch files
have a cog icon next to their name.
If you're not using Windows, you should instead run the other file in the bin folder (called enchcracker,
not enchcracker.bat). How to "run" a shell script like this may differ from system to system and I
can't give instructions for every system.
You must have Java installed to run the enchantment cracker. You may install Java from here.
Feel free to report bugs and ask any questions you may have on the issue tracker, but make sure to search whether anyone has reported your bug or asked your question before.
Assuming you have git installed, run the following commands from the
Command Prompt/Terminal.
git clone https://github.com/Earthcomputer/EnchantmentCracker
cd EnchantmentCracker
gradlew build
On Linux/MacOS, run ./gradlew build instead of gradlew build.
The resulting zip file may be found in the build/distributions folder.
Alternatively you can run directly from source without building, using
the gradlew run command.
All (sensible) contributions are welcome!
If you use Eclipse, run gradlew eclipse to generate an Eclipse project,
then use File > Import > General > Existing Projects into Workspace inside
Eclipse. Navigate to the EnchantmentCracker folder and click import.
If you use IntelliJ IDEA, it can import the Gradle project directly.
Most contributions are accepted via pull requests.
If you want to add translations to the project, you are welcome to do so!
You do this by adding a new .properties file under resources/i18n
representing your added language, then create a pull request adding that file.
As creating a pull request may be tricky if you are not used to coding,
translators may instead create an issue and upload their properties file, and
I will add it in myself.
Note that if you do make translations, I will not be able to update most of them in line with the default English translations, as I do not speak those languages, so you may have to keep them updated yourself.