Links
Tags
Creators
Details
1.80-beta
Compatibility
Changes
Changelog
This beta version focuses on stability and improvements to the random mode.
This is a bet because the tasks are not fully completed (i.e. they will be updated in the release), and I also do not have a team to check everything.
Patch note Hunter vs Speedrunner 1.80-betta:
đź”§ Fixes & Improvements
- Fixed multiple bugs and significantly improved overall game stability
- Random tasks system has been fully reworked
- Removed impossible-to-complete tasks
- Improved task distribution and completion checks
- Fixed an issue where tasks were not counted as completed if one of the speedrunners died
- Fixed localization issues related to random tasks
- Fixed a problem with spawn point reset
- Fixed an issue where task bossbars could disappear
- Task bossbars are now stable and no longer vanish during the game
- Fixed an issue where a notification about hunters leaving appeared if the game ended before their teleportation
Now this notification appears only if the game was not force-ended and the hunter release time was reached
- Fixed the gamerule locator so it is now automatically disabled on game start
Yes, this is because of that Mojang update. I hate it too.
Random Tasks
- If there are two speedrunners and one of them dies, their tasks are redistributed among the remaining players
You might get lucky and receive 0 tasks — it’s random after all
- Fixed an issue where tasks were not marked as completed if one of the speedrunners died
New Features
- Hunters can now see other players’ tasks while holding a compass
- If random mode is disabled, the main objective for speedrunners is to kill the Ender Dragon
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:pJ2R5qSJ:qwNTbDOp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pJ2R5qSJ:qwNTbDOp"
}

