Tags
Creators
Details
1.0.1+mod
Compatibility
Changes
1.0.1 Changelogs
-
Reworked the ranges to match a beacon's actual range, going up 500 blocks alongside no longer being circular.
-
Made the quick-find's "beacon-found" particles only visible to the user
-
Renamed some of the namespaces to be shorter and match next datapack, next version won't have the transfer lines.
-
Slightly optimized the check for if a beacon should give two effects or not on 1.20.3+ (when level 4)
-
Added smaller indications to some of the manual commands
-
Compatibility for some earlier snapshots and 1.20.5 (?)
-
Significantly reduced the size of the datapack's icon
-
Stopped effects from being given through full snow blocks
-
Fixed effects not being given through short grass (1.20.4), moss carpet, composters, floor-piglin head, decorated pot, soul lantern & campfire, sculk sensor(s), sculk shrieker, and bedrock.
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:upNMhnTq:PBZ2rTg4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:upNMhnTq:PBZ2rTg4"
}

