Tags
Creators
Details
1.8
Compatibility
Changes
🔧 TheMob v1.8 – Combat, Config & Control
This release expands TheMob’s core systems with advanced combat configuration, admin-only feedback controls and full global config transparency, building directly on top of the v1.7 automation & scaling foundation.
No gameplay rebalance.
No forced behavior.
Only more control, safety and clarity for server owners.
⚔️ Advanced Combat Configuration (NEW)
Combat behavior is now globally configurable and admin-controlled.
combat:
damage-indicator:
enabled: false
show-to:
- op
- admin
✔ Floating damage indicators are now fully optional
✔ Visible only to admins / operators by default
✔ No PvP clutter, no immersion break for players
➡️ Ideal for debugging, balancing and boss tuning
➡️ Zero gameplay impact for normal players
🧠 Automation Feedback Control (NEW)
Spawn protection feedback is now configurable.
automation:
feedback:
show-to-players: false
✔ TPS warnings
✔ Budget blocks
✔ Cooldown blocks
➡️ Shown only to admins by default
➡️ Players never see internal system messages
This keeps gameplay clean while admins stay fully informed.
📖 Full Global Config Documentation (LIVE)
The entire config.yml is now fully documented on GitBook.
✔ Every section explained
✔ Safe defaults clarified
✔ Performance & scaling behavior documented
✔ Network-ready explanations
🛠 Internal Stability Improvements
Several under-the-hood improvements were included:
✔ Safer phase combat modifier handling
✔ Improved lifecycle cleanup for bosses & minions
✔ Defensive checks against invalid stat keys
✔ No forced despawns – ever
These changes improve long-session stability and reduce edge-case risks.
✔ Safe for live servers
✔ No performance regressions
✔ Fully backward compatible
✔ No required config migration
⚠️ Some systems are intentionally admin-only for now
→ Player-facing options will unlock later in v1.9 / v2.0
📌 Notes
Protection systems only block spawns, never delete mobs
All config values are optional – missing sections fall back safely
Designed for long-running servers & large networks
Thanks to everyone testing, reporting and pushing TheMob forward ❤️
More combat and UI polish coming next.
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:8hhaeY0e:F6jPKdhF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8hhaeY0e:F6jPKdhF"
}

