Creators
Details
1.1.0
Compatibility
Required content
Changes
π BPREFIX v1.1.0 β The Big Bedrock & Cross-Platform Update!
We are excited to release the biggest update for BPREFIX yet! The focus of this update is entirely on the seamless integration of Bedrock players via Geyser and Floodgate, alongside a high-performance Paper-Native architecture.
β¨ New Features & Highlights
- π± Native Bedrock UI (Geyser Cumulus Integration):
- Bedrock players (mobile, consoles, Windows 10/11 edition) now receive a modern, native form UI instead of cumbersome chest inventories.
- Automatic client type detection: Entering the command on Bedrock instantly opens the sleek form interface.
- π Perfect Cross-Platform UUID Synchronization:
- Full integration of the Floodgate API (getJavaUniqueId()).
- Prevents any data desyncs: Bedrock players are now flawlessly mapped in the data.yml and retain their chosen prefixes permanently.
- β‘ Performance & Architecture:
- Fully optimized for the Paper-Native API and the Brigadier Command API standard.
- Implementation of ConcurrentHashMap for thread safety in modern server environments (perfect for Folia and high-performance networks).
- π¨ MiniMessage & Adventure API Support:
- Modern text formatting and color tags are now smoothly processed and safely stripped for clean Bedrock displays.
π οΈ Bugfixes & Improvements
- π Permission Handling: LuckPerms permission checks now work with equal precision for both Java and Bedrock accounts.
- π Reset Function: Resetting prefixes (both via chat/Bedrock form and GUI) has been optimized to directly target the corrected player profiles.
- π§Ή Various minor code cleanups and stability improvements for a lag-free player experience.
Optional dependencies
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:QtkrFRVG:J1zRIoeN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QtkrFRVG:J1zRIoeN"
}

