Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last year
All versions
6.0.6
Release
Primal Magick 6.0.6last year 1,445
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
v6.0.6
- Added Pixie Houses, to give your flighty friends a home to defend
- Added Spelltomes, to expand the repertoire of spells you can use at once
- Added Mana Orbs, to supplement your supply of mana on the go
- Added a new enchantment for Mana Orbs, Pondering, to increase the rate of paired wands' passive regeneration
- Allowed magickal saplings to be placed in flower pots
- Allowed the Desalinator to fill itself with water if placed in an infinite water source
- Increased mana throughput for all tiers of mana relays and injectors
- Increased the required mana siphon amount for the Link Saturation advancement
- Made the Mana Efficiency enchantment applicable to magickal robes and offhand items as well
- Made the Spell Power enchantment applicable to spelltomes as well
- Fixed a bug where consecration fields would cast shadows
- Fixed a bug where the hitbox of the Celestial Harp didn't always line up with it visually
- Fixed an item duplication bug with the Runic Grindstone
- Fixed a bug where the Runic Grindstone wouldn't give hints in some circumstances
- Fixed a bug that could allow Enderman teleportation to ignore an Enderward in some circumstances
- Restored the Treasure enchantment to full functionality
- Made several blocks waterloggable (Thanks, eehunter!)
- Removed outdated references to mana cost penalties from some Grimoire entries
- Fixed a tooltip bug for wands that were showing incorrect mana costs for spells
- Fixed base mana cost modifiers for multiple spell components
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:VlgDBPBy:UsFmjjO8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VlgDBPBy:UsFmjjO8"
}

