Tags
Creators
Details
0.1.5
Compatibility
Changes
- added lefonti nether terraforms
- added lefonti revive dead coral
All dragonization potions which will base off thick potions. In Minecraft, thick potions aren't used and since molten crystals are typically thick, it's a cool path to take giving an additional use of glow stone and giving life to the thick potions.
- added lefonti dragonization potion
- renamed meteorite to chondrite for a more scientific naming
- added chondrite bricks and polished chondrite
- fixed dragonization effect not randomizing nausea effect chance (5% chance per tick)
Dragonight abilities are now in the mod for lefonti. After having the lefonti dragonization effect for about 2 minutes and 50 seconds you will become a life dragonight and gain their plant related abilities at any given time. Press "0" (check your controls if it doesn't work) to enable usage then with an empty main-hand right click any compatible block to terraform or bonemeal the area. This is mainly works with dirt and sand related blocks. With an empty main-hand, you will also be able to break any plant block as if you had shears or silk touch. During a fight, right click an entity with either an empty main hand, a wooden sword, or any swords with the "lefonti imbuement" enchantment to suffocate them in blocks of logs or cactus depending of the present biome and ground condition. For admins, you can use "/dragonight_lefonti" to instantly become a dragonight.
- added lefonti player abilities
- added right click block to use ability
- added left click block to use ability
- added right click entity to use ability
- added admin dragonight lefonti command
- added lefonti dragonight advancement
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:1pnKrFfp:vvUvvjIf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1pnKrFfp:vvUvvjIf"
}

