Links
Tags
Creators
Details
1.0.0
Compatibility
Changes
SimplyManhunt
SimplyManhunt is a high-performance, enterprise-grade Minecraft Speedrunner vs. Hunter plugin built specifically for modern server environments (Minecraft 1.20 and above). Engineered with a robust internal state machine and strict initialization verification, this plugin eliminates the traditional configuration errors commonly found in community mini-games, delivering a flawless competitive experience.
🚀 Key Architectural Features
- Strict Setup Verification Engine: Prevents matches from starting prematurely. The plugin cross-checks role assignments, boundary metrics, and game modes before enabling initialization hooks.
- Dynamic Multi-Language Support (I18n): Features fully localized real-time messaging, allowing seamless switching between English, Turkish, French, and German.
- Synchronized Multi-Dimension World Border Control: Modifies global boundary logic synchronously across the Overworld, Nether, and The End with 0-second instant compression vectors.
- Intelligent Cross-Dimension Portal Tracking: Dynamically recalibrates hunter compasses to target a Runner's last known Nether/End portal location when dimensions mismatch.
- Advanced Economy & Sabotage Subsystems: Integrates dynamic bartering probability tables for Piglins and a live event-driven scoring matrix for Hunters to deploy tactical sabotages.
🛠️ Global Administration & Management Commands
All administrative actions require the manhunthelper.admin permission nodes.
Core Game Loop Control
/mh help- Description: Dynamically renders the interactive command documentation directly to the executor based on the active language configuration.
/mh status- Description: Audits the current memory state of the plugin. Outputs active registries, configured probability multipliers, cross-dimension tracker flags, and boundary readiness status.
/mh start- Description: Triggers the strict setup validation routine. If all criteria are satisfied, it executes a synchronized title-frame countdown, establishes a 30-second localized freeze period (Slowness CCLIV) for Hunters, and unlocks the Runner sequence.
/mh stop- Description: Forces immediate game termination. Purges volatile memory pools, clears tracking BossBars, resets state registers, and calculates session variables.
Match Configuration & Setup
/mh runner [player_name]- Description: Registers or deregisters a target network entity into the
Runnervolatile array list. Automatically balances teams by stripping conflicting player roles.
- Description: Registers or deregisters a target network entity into the
/mh hunter [player_name]- Description: Invokes target insertion into the
Hunterregistry. Instantiates tracking maps for player deaths and hooks into the automated Sabotage Point accumulation loop.
- Description: Invokes target insertion into the
/mh border [size_in_blocks]- Description: Forces an immediate, synchronous update to the
WorldBorderAPI across all active dimensions. Restricts the playable volume instantly with zero travel latency.
- Description: Forces an immediate, synchronous update to the
/mh chance [0-100]- Description: Overrides the internal drop-table weight for Piglin bartering mechanics. Directly manipulates the mathematical probability of spawning an Ender Pearl when interacting with gold ingots.
/mh lang [en/tr/fr/de]- Description: Alters the global language state machine on-the-fly. Instantly switches all system broads, title payloads, and localized error strings to the selected language.
Dynamic Modifier Toggles
/mh toggle nether [true/false]- Description: Explicitly configures the cross-dimension portal localization sub-routine. When set to
true, Hunter compasses point to the Runner's exact dimensional migration point.
- Description: Explicitly configures the cross-dimension portal localization sub-routine. When set to
/mh toggle sabotage [true/false]- Description: Governs the generation of automated Hunter assets. Enabling this allow Hunters to gain periodic points used to disrupt the Runner's progress.
/mh toggle diamondtracker [true/false]- Description: Validates or invalidates the Runner's protective intelligence system. Enables or completely restricts the ability for Runners to purchase proxy warnings.
🎮 Competitor & Player Commands
Available to all active participants in the match.
/hunt- For Hunters: Dynamically recalculates the precise coordinate vectors of the nearest alive Runner and forces a physical synchronisation to the player's Tracking Compass inventory slot.
- For Runners: Acts as an interface to the Diamond Tracker economy. Deducts 5 Diamonds from the inventory ledger to enable a real-time, micro-updating Actionbar display indicating the absolute distance of the nearest threat for 3 minutes.
/hunt sabotage- Exclusive to Hunters: Queries the player's current Sabotage score. If the balance meets the 10-point threshold, it deducts the assets and triggers an event-driven lightning strike directly onto the vector of the nearest alive Runner.
📋 Comprehensive Pre-Flight Setup Checklist
To guarantee successful match initialization via /mh start, the network administrator must execute the initialization matrix in the following mandatory sequence:
- Assign Teams: Populate registries using
/mh runner [Name]and/mh hunter [Name]. - Define Boundaries: Constrain the operational theater using
/mh border [Size]. - Calibrate Bartering: Inject balance variables using
/mh chance [Percentage]. - Confirm Global Toggles: Explicitly declare game parameters by running all three modifier vectors:
/mh toggle nether <true/false>/mh toggle sabotage <true/false>/mh toggle diamondtracker <true/false>
- Verify State: Run
/mh statusto confirm all validation fields are green. - Launch: Initialize the competitive runtime engine with
/mh 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:qFGHJPSV:dfycHmzX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qFGHJPSV:dfycHmzX"
}

