Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 months ago
All versions
1.0.1
Release
Villainous Horde Manager 1.0.12 months ago 45
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
- Adds the minimumSpawnRange and maximumSpawnRange fields to the wave data
- If these fields are not present, they'll default to the original values of 21 and 35
- These numbers are recommended unless you're going for something specific, as they reduce the odds of pathfinding issues, as well as reduce the risk of low render/simulation distance causing problems.
- Adds the "auto" setting when starting json hordes through the command.
- Auto will pick the player with the most other players around them to be the anchor point of the horde
- If the highest player is tied with another for number of players around them when the command is run, it'll randomly pick between the top contenders.
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:pXwCfB4o:gyplR0b7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pXwCfB4o:gyplR0b7"
}

