Tags
Creators
Details
2.0.9
Compatibility
Changes
BedrockGUI v2.0.9
This release adds a third official addon ā Homestead ā and a new actions-only mode across all addons.
š New: Homestead Addon
Native Bedrock forms for the Homestead land-claiming plugin ā all 27 of its GUIs, built for you and served automatically to Bedrock players:
- Regions ā list, per-region hub, info, top-regions leaderboard, welcome-sign teleports.
- Players ā members, invites, bans; invite / ban / kick / unban / revoke from forms.
- Flags ā world, global, and per-member player & control flags as toggle sheets.
- Sub-areas ā manage, rename, delete, members and flags.
- Chunks ā claimed-chunk list (teleport / unclaim) plus map colour & icon pickers.
- Progression & settings ā levels, rewards, logs, rating, region settings and a weather/time cycler.
Bedrock players who run any Homestead command get the form automatically; Java players keep the native GUIs. Requires Homestead installed.
š New: actions-only mode for every addon
All three addons now have integrated-gui and register-actions toggles. Set
integrated-gui: false to stop the built-in forms and command interception while still registering
the addon's actions ā so you can build your own BedrockGUI menus and drive the plugin through them.
š¦ Distribution
Addons are distributed with the main plugin ā grab the JARs from the release:
BedrockGUI-HomesteadAddon.jar(new)BedrockGUI-EssentialsAddon.jarBedrockGUI-BedwarsAddon.jar
Installation: drop the addon JAR(s) into plugins/ alongside BedrockGUI v2.0.8+ and Floodgate.
The Homestead addon also needs the Homestead plugin. See each addon's page for setup details.
Requires Paper/Spigot 1.20.1+ and Java 21.
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:T4qAiwvL:zEsfp8ug"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:T4qAiwvL:zEsfp8ug"
}

