All versions
2.1.1
Release
BetterBeacons-NeoForge-1.21.1-2.1.1last year 19K
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[2.1.1] - 2025-02-16
Fixed
- Fixed crash of beaconMixin being null
[2.1.0] - 2025-01-29
Added
- Add zh_cn translation (Thanks crazyfl-exe)
Changed
- Update to 1.21
- Base blocks can now be mixed and keep a higher amplifier
- Update ru_ru translation (Thanks mpustovoi)
[2.0.0] - 2024-01-28
Added
- Compatibility with CerbonsAPI 1.1.0
- Support for Fabric and NeoForge
- Compatibility with Just Enough Effect Descriptions mod
- Config to change the payment items in the UI and theirs positions
- ru_ru translation (Not complete because of the update to multi loader)
Changed
- Move project to multi loader
- Configs are now handled with cloth config
- Config names
- ++ and -- from the UI are now translatable using a lang file
- Patrol Nullifier effect rename to Patrol Bane
- Improve compatibility with Quark beta
- Minor code improvements
Removed
- Waterlogging and conduct redstone configs
- Lock beacon feature
[1.1.1] - 2024-01-18
Fixed
- Fix crash if using mod alongside Quark beta
[1.1.0] - 2023-12-31
Changed
- Make mod dependent on CerbonsApi
[1.0.2] - 2023-11-02
Fixed
- Fix mod crashing when used on servers
[1.0.1] - 2023-10-31
Changed
- All copper variants can now be used to build the beacon
[1.0.0] - 2023-10-12
- Initial release
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:gSeQTNSE:acPk7j8a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gSeQTNSE:acPk7j8a"
}

