Tags
Creators
Details
All versions
1.1.0
Release
Dragon Mounts Remastered 1.1.03 years ago 916
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.4
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Added 4 new config options:
- base_health: The base health dragons should have when fully grown
- base_damage: The base damage dragons should have when fully grown
- allow_respawn: Should dragons be able to be re-summoned after they die? If this is turned off a dragon is completely lost on death, even if the owner isnt online when playing on a server
- respawn_time: The time in seconds that you have to wait to resummon a dragon after it dies, this is by default 60 seconds
Added dragon whistles
- Summoning a dragon now requires that you have a dragon whistle in your inventory that has been linked to a dragon.
- To use the dragon whistle, craft one of a specific dye color and shift right click on a dragon that hasnt already been linked.
- When using the summon keybind the top most valid whistle in the inventory will be used to determine what dragon is summoned
- With the introduction of whistles you can now have more then one dragon that you are able to summon
- The whistles functions similarly to modded ender chests and similar items, where crafting 2 of the same color of whistle will function the same, so losing a whistle doesnt lose the dragon.
New system for dragon armor
- Dragon armor has been made into its own item rather then using horse armor
- The icon and armor textures are still a work in progress but the armor itself is functional
- The armor can be found in some of the same locations as their horse counterparts
Misc
- Change the player model to use the position of the "rider" bone when found, PR from NordAct
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:DUx05jFK:AqLvntI6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DUx05jFK:AqLvntI6"
}

