1.1.0
Compatibility
Required content
Changes
Added Blockworks, infrastructure for automated casting:
- Produce Mana with the Mana Forge
- Transport Mana with the Mana Link
- Store Mana with the Mana Battery
- Interface with devices using the Mana Frame
- Store information in the Locus
- Added the Casting Frame, triggered by redstone
- All additions discussed in detail in the in-game guidebook
Added new Blockworks glyphs, able to trigger Casting Frames, fork spells, store and retreive information and detect redstone power
Transmitters can be linked to casting frames and placed over batteries, allowing the frame to draw Mana from the Battery during casting.
Added the Infused Loupe, allowing networks to be observed and visualised.
Reworked casting logic to enable block-based and non-player casters.
Added Spatial Strike spell, able to interrupt casting in progress.
Added Collect and Store Item spells, able to store items in Entity and BlockEntity inventories.
Added lang file support for Spanish and Russian.
Added commands for unlocking glyphs and setting mana level and First Threshold status.
Added config control for Mana Forge production rates, mana reservoir storage, player mana max, player mana regen, casting frame cooldown, decoction max mana boost, etc.
Added compatibility with Botania:
- Explosions from Lingua Mundi work with the Entropinnyum
- Exoflames can now head Mana Forges
Added compatibility with Valkyrien Skies
Added compatibility with Iron's Spells and Ars Nouveau, with config-control managing potential merging between Lingua Mundi's player mana and one of the aforementioned mods' own system.
Made basic spells into cantrips, unlocked by default.
Fixed several null pointer errors caused by list species.
Optional dependencies
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:2uCEiJ7z:5NbHJGZR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2uCEiJ7z:5NbHJGZR"
}






