Links
Tags
Creators
Details
2.4.0
Compatibility
Required content
Changes
-
Added
baby_texture,baby_model,baby_animationandbaby_saddlemodel redirect fields- They act exactly the same as their counterparts without
baby_prefix - Anything placed in those fields will be applied only if dragon is baby
- If those fields are not specified, baby models, animations and textures will be applied normally
- They act exactly the same as their counterparts without
-
Improved readability of model redirect data, hitbox redirect and variant spawn debug prints in logs
- They also are now printed in normal log instead of debug one
-
Added options
log_model_redirectsin client config andlog_variant_spawnsandlog_hitbox_redirectsin common config. Both are set tofalseby default- If
log_model_redirectsset tofalse, information about registered model redirects will not be printed in logs - If
log_variant_spawnsset tofalse, information about registered variant spawns will not be printed in logs - If
log_hitbox_redirectsset tofalse, information about registered hitbox redirects will not be printed in logs
- If
-
Added
dragonfield for model redirects, hitbox redirects and variant spawns.dragonfield allows to specify dragon ID to which this file belongs. If specified, file name will be ignored- If
dragonis not specified, it'll attempt to define dragon ID from file name as before - Field must be specified outside entry list for all cases, i.e.:
{ "dragon": "some_dragon", "redirects": [ ... ] } -
Now if mod is unable to recognize dragon ID in model redirect, hitbox redirect or variant spawn file, file will be skipped and warning will be printed in console
-
Added Jade integration for displaying dragon and egg variants in tooltip
- Additionally added
display_original_variant_nameclient config option that can enforce display of string formVariantNameNBT in dragon variant tooltip
- Additionally added
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:XepXTAL4:PJ00bFZD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XepXTAL4:PJ00bFZD"
}


