William GaylordandGitHub 665bf9b7c7 Fix handling FeatureSet related entities in 1.20.3/4 (#16)
* Fix handling FeatureSet related entities.

* Add 1.20.4 to build.yml

* Turns out jsut need to enable the feature set in the server.properties

* Remove the server.properties

Lets not enable feature sets since they could change alot of stuff on use.

The other fix in the PR still works as it makes it so that the entities don't show up as player type, just as unknow if we can't get them.

* Use the same way of getting the entity in all parts of the generator.

This should help deal with entities from features, since using the factory directly gets around the feature check.

* Would be helpful to call the function correctly...
2024-03-17 16:13:09 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 23:07:36 +01:00
2023-12-31 20:25:13 +01:00
2023-12-31 20:25:13 +01:00
2023-12-31 20:25:13 +01:00
2023-12-31 20:25:13 +01:00
2022-12-29 16:45:15 -05:00
2022-12-29 16:45:15 -05:00
2022-05-05 16:09:16 -04:00
2023-12-31 23:07:36 +01:00

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:

./gradlew :<version>:runServer

For Windows:

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. 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.

S
Description
No description provided
Readme MIT
691 KiB
Languages
Java 99.5%
JavaScript 0.4%
Kotlin 0.1%