1.2.5
Compatibility
Required content
Changes
LUMINOUS:BEASTS V1.2.5 Changelog
NEW FEATURES:
-Added the Witchdoctor, a new Legendary Beast found in the Spare Jungle!
-Added the Woodland Witchdoctor, a new Rare Legendary Beast found in the Taiga Forest!
-Added 2 new trophies for the Witchdoctor and Woodland Witchdoctor
-Added 2 new Ultimate Bestiary Journal Entries for the WitchDoctor and Woodland WitchDoctor
-Added 2 new config variables for determining if Witch Doctor and Woodland Witch Doctor will spawn
-Added 2 new config variables for the Jungle Pendant, Pendant_timer, and Pendant_Reistance
BUG FIXES:
-Fixed an issue where crafting the beast pit would yield a beast pit in he wrong blockstate
-Fixed a bug where the Red Mummy would not have the correct texture when it changed attack states
-Fixed an issue where the Mummy and Red mummy were missing an agro animation
-Fixed a bug where the Sea Viper Fang would only work when the player had a certain slot selected in the inventory
-Fixed a bug where the Yeti Horn would only work when the player had a certain slot selected in the inventory
RETEXTURES / MODEL CHANGES:
-None this time
TECHNICAL CHANGES:
-Added an extra block to the "When Item in hand tick" procedure for the sea viper fang, so it only works when a player is in survival
-Added an extra block to the "When Item in hand tick" procedure for the Yeti Horn, so it only works when a player is in survival
-Reduced the Duration of the resistance granted by the Sea Viper fang from 12s > 5s
-Added another check for if the player is below full health in the procedure for the Yeti Horn, so the NBT data is not constantly updating
-Reduced the base value of the Viper fang timer configuration variable from 10 to 8
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:fGCP5k6m:i7mFpZFw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fGCP5k6m:i7mFpZFw"
}

