Tags
Creators
Details
All versions
0.9.0
Release
v0.9.0 - Fix'n'Type'Help(?)3 years ago 64
Compatibility
Minecraft: Java Edition
1.20.2–1.20.4
Platform
Data Pack
Changes
- Added a setting to choose new presets for the entities the beacons will buff, instead of being limited to peaceful mobs unless you modify the datapack. (normal/peaceful, breedable, tameable, peaceful + player, player, hostiles, and blank custom)
:
- Compatibility with 23w31a+ incase anyone wants to use it on those two snapshots without it complaining
- Slightly optimized general detections by caching levels much less frequently, instead of checking it every tick, also with a micro optimization to the settings check(s).
- General improvements to "Quick-Find"
- Fixed it not stopping, added a more visible particle at the end so the maximum range is more visible, reduced the overall duration, and made the particles only visible to the player its casting from.
- Renamed the "particles" setting to actually match the true/false values, it will automatically convert.
- Added
/function blue_b:check_settings; it will simply tell you which settings have a improper value, which can be the cause of the entire beacon not working. - Added
/function blue_b:beacons_help, made to be a much easier to access and use help method, and replaces the text inblue_b:firstload- Also added
/function blue_b:default_valuesto display what values would be default in vanilla, excluding the particles. - And
/function blue_b:set_defaultto.. set all values to their defaults
- Also added
- Hey, guess what? Added another function,
/function blue_b:remove_peaceful_beacons; I don't see how anyone would need to remove it since disabling the repeating function disables 90-99.9% of the average lag but there you go
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:DK3sl3Rz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:upNMhnTq:DK3sl3Rz"
}

