1.1.0
Compatibility
Required content
Changes
Changelog
This may be the final content update for the mod. Future updates will focus on fixes and adjustments.
Additions
New Entities
Three new Illager-type servants have been added to the mod:
Firecaller Servant: A geomancer Illager servant that hurls magma bolts at enemies. Its magma bolts explode on impact, scorching the ground and knocking nearby creatures back without breaking terrain or damaging the owner and allies. Bound Firecaller: The soul-bound form of the Firecaller Servant. It floats above the ground, unaffected by gravity, and inherits the Firecaller's magma bolt and area damage spells. Bound Sorcerer: The soul-bound form of the Sorcerer Servant. It wields purple magical flames, teleports to reposition.
New Focus
Fire Call Focus: Casts a magma bolt that travels in the direction the player is looking. The bolt bursts upon impact, creating a non-terrain-breaking explosion that scorches the ground and flings nearby enemies aside. Compatible with Potency and Burning enchantments. When cast with a Geo Staff, two additional bolts are loosed. Configuration
Comprehensive Servant and Spell Configuration
The mod now ships with a fully featured configuration system under config/goety_invasion/:
servants.toml provides per-entity tuning for every servant in the mod, covering health, armor, follow range, movement speed, casting cooldowns, damage values, effect durations, and skill radii. All values can be adjusted without recompiling. spells.toml provides per-spell tuning for every focus in the mod, covering soul cost, cast duration, cooldown, damage, and radius. All values can be adjusted without recompiling.
Configuration files are generated automatically on first launch and reloaded on server start.
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:MnJ7CuCq:plFPenFA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MnJ7CuCq:plFPenFA"
}

