Tags
Creators
Details
1.3.11
Compatibility
Changes
Horde Nights v1.3.11
Notes
This version is primarily developed for 1.21/1.21.1, and changes are ported upwards. This means despite estensive playtesting, there is still a higher chance of bugs in 1.21.2+. Please report any you find! Horde Nights is not actively recieving new content at this time. Fixes and Ports will be pushed as needed. Otherwise, see you for v2.0.0 in 2026!
Updates
- Updated to support 1.21.9/10
Additions
- Added two new enchantments:
- Knowledge of The Horde - Gain additional EXP from slaying Horde Mobs.
- [Curse] Bunk Knowledge of The Horde - Gain less EXP from slaying Horde Mobs.
- These enchantments are obtained through the enchanting table, villagers, and loot drops, unlike the Horde Damage enchantments.
- The curse is meant to be insanely common. This is not a bug. This is intended to draw out progression of Horde Nights mastery.
Changes
- Bunk Horde Damage Enchantments no longer function in the offhand, only the mainhand.
- Rebalanced EXP gain from Horde Mobs slightly. Some mobs now gain drastically more in some cases by default.
- See the two new enchantments above.
Fixes
- Fixed skeleton & zombie horses not being able to be ridden.
- Fixed skeleton & zombie horde size.
- Fixed zombie horses not being implimented into bunk blood moons properly.
- Fixed zombie horses not being implimented into super moons properly.
- Fixed implimented zombie & skeleton horses not spawning at all.
Known Issues
- Skeletons on Skeleton Horses do not spawn with a weapon.
- Skeletons do not seem to get enchanted bows in 1.21.9/10.
- Skeletons do not seem to get infested effect in 1.21.9/10.
- Spiders do not seem to get weaving effect in 1.21.9/10.
Datapack Conventions Compliance
This pack complies with the following Datapack Conventions:
Optional dependencies
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:jGO2ac1X:qzVyAjmr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jGO2ac1X:qzVyAjmr"
}

