Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 23 hours ago
All versions
- Added a server-side playerTickWorkInterval config option to reduce expensive per-player hazard calculations.
- Hazard apply intervals are now tracked per player and hazard type, so skipped worker ticks do not break exposure timing.
- Cleared cached player hazard tick state on logout.
- Improved point hazard line-of-sight handling, including block sources that should not block themselves.
- Absorption-based point hazards now use absorption tracing instead of treating solid blocks as all-or-nothing line-of-sight blockers.
- Avoided loading chunks while checking hazard block sources and blockers; unloaded chunks now use conservative defaults.
- Updated datapack documentation for playerTickWorkInterval and point hazard blocking/absorption behavior.
1.20-0.0.2
Beta
Hazardous - 1.20-0.0.24 months ago 23
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Changes
Hazardous 1.20-0.0.2
- Added a server-side playerTickWorkInterval config option to reduce expensive per-player hazard calculations.
- Hazard apply intervals are now tracked per player and hazard type, so skipped worker ticks do not break exposure timing.
- Cleared cached player hazard tick state on logout.
- Improved point hazard line-of-sight handling, including block sources that should not block themselves.
- Absorption-based point hazards now use absorption tracing instead of treating solid blocks as all-or-nothing line-of-sight blockers.
- Avoided loading chunks while checking hazard block sources and blockers; unloaded chunks now use conservative defaults.
- Updated datapack documentation for playerTickWorkInterval and point hazard blocking/absorption behavior.
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:z0ksB2DN:dAarI0qI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z0ksB2DN:dAarI0qI"
}


