Tags
Creators
Details
1.5
Compatibility
Changes
TheMob v1.5 – Combat Engine & Advanced Spawn Control
This update is a system-expansion release that introduces a new player stat foundation and a fully reworked, command-driven spawn control layer.
v1.5 builds on the stability of v1.4 and expands TheMob from a fixed arena system into a dynamic, controllable world-spawn framework.
It turns spawning from “static and location-bound” into “intentional, player-aware and state-driven.”
Goal
Create a unified system where:
Combat is fully stat-driven
Spawning is intentional and controlled
Player movement influences gameplay
All systems remain predictable and exploit-safe
At the same time:
Maintain v1.4 stability guarantees
Prevent spawn abuse and duplication
Keep performance constant under load
Core Improvements Advanced Spawn Control via /mob set
A new command-driven spawn control system was introduced.
Spawns can now be created, modified and managed at runtime without editing YAML files.
/mob set autospawn – Fixed Point Spawning
Creates a fixed-location auto-spawn bound to the execution point.
Features:
Interval-based spawning
Maximum active spawn limit
Hot / cold lifecycle support
Automatic cleanup on cold state
➡️ This is the core, arena-style spawn system, now fully command-controlled.
/mob set followplayer – Player-Bound Spawning
Creates a spawn rule that follows a specific player.
Features:
Player-bound spawn anchor
One-time or endless spawn modes
Minimum and maximum distance control
Spawn wave limits
Optional player notification messages
Use cases:
Hunter-style encounters
Dynamic ambush events
Story-driven pursuit mechanics
➡️ Spawning now reacts to player movement, not static locations.
/mob set randomradius – Radius-Based Spawning
Creates random spawns around a fixed point.
Features:
Configurable minimum and maximum radius
Interval-based spawning
Max active spawn control
Lifecycle-bound cleanup
Use cases:
Open-world events
Dynamic encounter zones
Non-static farming areas
➡️ Prevents predictable farming patterns.
/mob set randomworld – Global World Events
Creates a world-wide random spawn event.
Features:
Random position selection across the world
One-time or repeating spawn modes
Periodic location hint messages
Auto-stop on mob death
Full lifecycle cleanup
Use cases:
World bosses
Global hunt events
Server-wide announcements
➡️ Enables true world events without custom scripting.
/mob list all – Spawn Overview
Lists all active spawn rules:
Spawn type
Target mob
State (hot / cold)
Active mob count
➡️ Administrators always know what is running and why.
Spawn Lifecycle & Safety Improvements
All new spawn types inherit the v1.4 lifecycle guarantees:
State-driven hot / cold logic
Delayed cleanup timers
UUID-based spawn tracking
Boss lock integration
Reload-safe handling
This ensures:
✔ No duplicate spawns ✔ No orphaned mobs ✔ No lingering world events
Combat System Foundation
(unchanged from previous section, summarized here)
Centralized player stat cache
Attribute-based stat application
Config-driven RPG stats menu
Tier-based progression system
Item stat and lore pipeline
Combat validated under high mob density
➡️ Combat and spawning now operate on the same lifecycle philosophy.
Internal Architecture Improvements
Unified spawn abstraction across all spawn modes
Reduced command-to-system coupling
Defensive handling for partial failures
Prepared hooks for:
Spawn conditions (time, weather, biome)
Event-based modifiers
Difficulty scaling
⚠️ Notes & Compatibility
✅ Fully compatible with v1.4 ✅ Safe update for existing arenas and worlds ✅ No migration required ✅ All previous auto-spawns continue to work
❌ No spawn rebalance yet ❌ No permission overhaul (planned for v1.6)
Summary
v1.5 is where TheMob becomes dynamic.
Combat is stat-driven. Spawning is intentional. Players influence the world.
This release transforms TheMob from an arena system into a living PvE framework.
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:KGtVR6hD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8hhaeY0e:KGtVR6hD"
}

