2c423f77f8
* 1.20.5 recipes: null over -1 * add 1.21 * 1.21 (#26) * update classname * update moved class * updated to equivelant method since gettranslatekey removed * added isCursed list as bandaid alternative for now since isCursed() removed * added isTreasure list as bandaid alternative for now since isTreasure() removed * found alternative method to canCombine() since removed * modified getEnchantmentTarget name to handle registryEntryList since getApplicableItems dosnt return tagKey anymore * bandaid list solution for "tradeable" property since isTradeable removed and no alternative in mappings * bandaid solution for discoverable property since removed and no alternative to isAvailiableForRandomSelection in 1.21 mappings * removed .toPath since apparently it dosnt exist * no longer outputs in tagkey format * fixed not adding enchantcategories for items properly * added SuperGamerTron tag solution * Update build.yml --------- Co-authored-by: Madlykeanu <96554689+Madlykeanu@users.noreply.github.com> Co-authored-by: Romain Beaumont <romain.rom1@gmail.com>
39 lines
1.5 KiB
Markdown
39 lines
1.5 KiB
Markdown
# minecraft-data-generator-server
|
|
|
|
This tool generates minecraft-data files based on a running server using a fabric mod.
|
|
The supported versions can be read in the directory structure.
|
|
Every version has its own directory.
|
|
|
|
## Usage
|
|
|
|
You can put any version that has a directory into the command below.
|
|
Just replace `<version>` with the version you want to generate.
|
|
|
|
For Linux/Mac OS:
|
|
|
|
```bash
|
|
./gradlew :<version>:runServer
|
|
```
|
|
|
|
For Windows:
|
|
|
|
```bash
|
|
gradlew.bat :<version>:runServer
|
|
```
|
|
|
|
You can then find the minecraft-data in the `<version>/run/minecraft-data` directory.
|
|
|
|
## Adding a new version
|
|
|
|
To add a new version, you need to create a new directory in the root directory with the version name.
|
|
Then you need to add the version to the list in the `settings.gradle.kts` file.
|
|
Then also add it to the `.github/workflows/build.yml` file.
|
|
Then copy the code of the most recently released version into the new directory.
|
|
Then you need to change the values in the `gradle.properties` file.
|
|
At last, you need to fix all code issues that are caused by the new version.
|
|
if there are any new curse, treasure, or non-tradeable, or non-discoverable enchantments in the new version, you need to add them manually to the `EnchantmentsDataGenerator` class.
|
|
For that, use an IDE like IntelliJ IDEA to fix the issues.
|
|
Once everything compiles, you can commit the changes, push them to your fork and create a pull request.
|
|
Once your PR was accepted and merged, the new version will be available in the next release.
|
|
|