Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 2 months ago
All versions
2.0.5-RELEASE
Release
BedrockGUI 2.0.5-RELEASE9 months ago 170
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
BedrockGUI Changelog
Added
- Visual Form Designer - New web-based interface at designer.pintux.org for interactive visual design and export of both Bedrock and Java menus
- Java Edition menu support - Full GUI support for Java Edition players
- Player head support in simple menus - Display custom heads using multiple image sources:
- Direct texture URLs from Minecraft texture servers
- Player usernames (both static and placeholder-based)
- Base64-encoded texture data
- External image URLs (e.g., Google logos, custom images)
- Per-form file structure - Forms are now stored in individual files for better organization
- Form validator - Automatically validates button configurations to catch missing required fields
/bgui openforcommand - Open forms for other players directly
Fixed
- Command actions - Commands triggered by button clicks now execute properly
- Velocity proxy messages - Removed hard-coded messages in Velocity build
- Conditional button checks - Simple form conditional logic now properly recognizes complex commands
- Delay action - Action delays now function correctly
- Config options - Cleaned up and fixed configuration handling
Changed
- Velocity build improvements - Commands now execute properly in proxy environments
- Code cleanup - Removed legacy conditional button code for Bedrock Edition
- Documentation updates - Wiki and plugin page now include setup instructions for servers without Floodgate or with Geyser on the same instance
Migration
- Important: Run
/bgui convertafter updating to migrate forms to the new per-file structure
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:XujTOyJM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:T4qAiwvL:XujTOyJM"
}

