Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 2 months ago
All versions
1.3.5
Release
[v1.3.5] Exp Rewards Overhaul + Fixeslast year 394
Uploaded by
Compatibility
Minecraft: Java Edition
25w19a
1.21–1.21.5
Platform
Data Pack
Changes
Horde Nights v1.3.5
Experimental Features
Experimental Features DO NOT:
- Receive support
- Guarantee support for Integrations
- Guarantee proper function
Additions
- Added two new advancements.
Changes
- Exp Rewards for killing mobs have been changed:
- There is no additional exp reward for killing a mob during a festive moon now.
- There is now an additional EXP reward for killing a mob during a bunk blood moon.
- Increased the EXP reward for killing a mob during a super moon.
- Nerfed the additional exp reward from zombie villagers(this is in prep for their upcoming content, making it less worth killing them).
- Buffed the additional exp reward from killing cave spiders, spiders, bogged, & stray.
- You can no longer earn statistic kills during festive moon events.
- Advancement Tweaks
- Ritual advancements are now placed behind the minecraft "obtain diamonds" advancement.
- Ritual advancements no longer announce to chat.
- Design tweaks
- Primed Diamond crafting recipe is now shapeless.
Fixes
- Fixed Festive Moon "Gifting" mechanic not working at all.
- Fix bad predicate checks preventing creation of bunk diamonds.
Known Issues
- Every horde mob except slimes do not drop items.
Datapack Conventions Compliance
This pack complies with the following Datapack Conventions:
Optional dependencies
Unavailable version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:RBNANRtd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jGO2ac1X:RBNANRtd"
}

