Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 2 months ago
All versions
1.3.3+mod
Release
[v1.3.3] QOL, 1.21.5, & Many Fixes!last year 687
Compatibility
Minecraft: Java Edition
1.21–1.21.5
Platforms
Forge
NeoForge
Supported environments
Changes
Horde Nights v1.3.3
Updates
- Updated to fully support 1.21.5
Changes
- Init v10
- Config Changes
- You can now configure Natural Bunk Events to be 50% chance, or guarenteed.
- Currently there is no 100% functionality in the TimeLib Integration, this may change.
- You can now configure Natural Bunk Events to be 50% chance, or guarenteed.
- Changed how Natural Bunk Events work
- If natural bunk events are enabled, they now only have a 50% chance relative to their non-bunk counterpart.
- For example, if your world is only currently eligible for Blood Moons, there will be a 50/50 chance of going bunk.
- However, if you are eligible for Festive or Super Moons, since these event's cannot yet go bunk, the chance is less than 50%
- The chance of a Bunk Blood Moon will be the same as the chance of a normal Blood Moon. 50% chance relative to non-bunk counterpart.
- However, you can choose to have the guarenteed functionality in the config.
Fixes
- Fixed #8 - Player can get Oozing Effect.
- Fixed #9 - Horde Mobs will delete player's items if they pick up and despawn.
- Fixed Natural Bunk Config Buttons doing nothing(oopps forgot code hehe).
- Potentially fixed a bug causing Festive Moons to never spawn if enabled.
- Fixed still being able to manually set difficulty to peaceful.
- Fixed Difficulty Config Page sometime being behind and not displaying correctly.
- Fixed Super Moon events not lasting 2x longer than regular nights.
- Fixed "Horde Rod" item being broken in 1.21.2+
- Fixed "Blood Pact" advancement in 1.21.4+
- Fixed NoSleep not working during super moons since bunk groundwork update.
Datapack Conventions Compliance
This pack complies with the following Datapack Conventions:
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Unavailable 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:NeqOE3IF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jGO2ac1X:NeqOE3IF"
}

