Creators
Details
2.0.11
Compatibility
Changes
If you want a server setup for the Big Beautiful Buttons mod with zero effort, get a server with BisectHosting and receive 25% off your first month as a new customer using the code kreezxil
Changes
• Every button now remembers the player who placed it. Buttons placed by commands or structures, and buttons placed before this version, have no placer and are never restricted.
• New option placerOnly (off by default): when on, only the placer can press a button, by hand, with arrows they shot, or with wind charges they threw. Other players, mobs, dispensers and ownerless projectiles are ignored, and operators are not exempt.
• New option placerOnlyShowMessage (on by default): shows "This button belongs to another player." on the action bar.
• New options pressDurationTicks (default 20) and woodTypePressDurationTicks (default 30) set how long buttons stay pressed.
• New options glowstoneLightLevel (default 15) and magmaLightLevel (default 3) set the light given off by glowstone and magma buttons.
• New command /big_beautiful_buttons <option> [value] shows or changes the options. It needs operator level 2 by default (the server console can always use it), rejects out-of-range values, saves to the config file and takes effect immediately. commandPermissionLevel can only be changed in the file or the config screen.
• Added a config screen in the Mods menu and an example config file, bigbeautifulbuttons.example.cf, which the mod never reads. Do not rename it to bigbeautifulbuttons-common.toml.
• The config file bigbeautifulbuttons-common.toml is created the first time 2.0.11 starts. Earlier versions had no config.
• Added English and Russian text for the config options and the message.
• Added game tests for the placer rules, press duration and light options, the command and the config files (20 tests in total).
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:lUPRlJLb:mS5Zu4wO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lUPRlJLb:mS5Zu4wO"
}


