Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 2 weeks ago
All versions
0.9.3
Beta
1.20.1 - 0.9.35 months ago 73K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
New Content
Spells
- Added "Mystic Shield": A reassuring defensive spell when facing spectral sharks.
Items
- Added "Scrollcaster Gauntlet" and "Spell Calibration Bench": A magical tool inspired by old-style spellbooks, along with a device used to calibrate it.
- Added "Multicast Echo Staff": If sound can echo, then surely magic can echo too.
- Added "Mithril Freecast Staff": A Swingcast Staff designed to be used freely while away from home.
- Added "Creative Spell Dispenser": For world creators and server administrators.
Changes / Tweaks
- Remodeled Pastel Staff.
- Removed the recipe-disabling config option to avoid conflicts with recipe-changing mods.
- Please use KubeJS or similar tools to disable recipes from now on.
- Removed the config option for adding Isekai Travel Guidebook to bonus chests.
- Please remove it directly from loot tables with a datapack or similar method from now on.
- Added many server config options for modpacks and multiplayer servers.
- Made Errand Mage trades data-driven.
- Removed a setting that made Scarlet Thirst too easy to obtain from catacombs.
Bug Fixes
- Fixed a bug where Smashcast Scepter swung too slowly when Better Combat was installed. (1.20.1 only)
- Fixed a bug where many Iron's Spells 'n Spellbooks spells could not deal damage when cast from a Spell Dispenser.
- Fixed a bug where breath-type spells, such as Fire Breath, could not deal damage when cast from a Spell Dispenser.
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:MYxjEv5n:Q5A4GPk6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MYxjEv5n:Q5A4GPk6"
}

