Tags
Creators
Details
1.8
Compatibility
Changes
MANY small things were changed in this update to increase performance a little and it's always possible bugs are introduced as a result! Please let me know if you find anything.
The following files were updated, but it's not a big deal to not reset.
- languages/en-us.json (alchemy perk disclosure)
- recipes/brewing_recipes.json (some recipes not giving exp when they realistically should)
- skills/enchanting_progression.yml (sweeping edge not giving exp)
ADDED Permanent effect cooldowns property to player stat profile (you can now give players permanent effects that have a cooldown on activation)
FIXED Player stats applying in incorrect scenarios, such as the player being affected by their own immunity reduction obtained via rapiers
FIXED ItemsAdder and CraftEngine blocks and items not being recognized
FIXED Bow damage being different depending if shot from main hand or off hand
FIXED The configuration button being absent in the "add permanent potion effect" modifiers
FIXED NullPointerException with JustLootIt
FIXED Repaired items being given ValhallaMMO durability when combining two vanilla tools in a crafting grid
FIXED Non-ValhallaMMO attribute stats not being recognized (for example when using custom armors from other plugins. Also included ValhallaTrinkets)
ValhallaTrinkets should also be updated if you have it
FIXED A certain alchemy perk not disclosing it also increased the quality of one's potions
FIXED The splash- and lingering potion recipes not rewarding alchemy exp
FIXED "crafting speed" stat not functioning on immersive recipes
FIXED Party rename command actually changing the description of the party instead of renaming
TWEAK Many small performance increases
TWEAK Improved recipe output preview system to display the output more accurately. This mainly just affects recipe book icons and immersive recipe buttons.
TWEAK The "charged shot" ammo animation no longer plays if the player is invisible
TWEAK Improved performance on block placement status data
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:rxrgsoud:fQUgyj48"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rxrgsoud:fQUgyj48"
}

