Links
Tags
Creators
Details
2.1.0
Compatibility
Changes
GeyserPlus v2.1.0
GeyserPlus is a community continuation of GeyserExtras (archived by its author on 2026-06-19). This is the first independent release, ported to Geyser 2.11.1 / Minecraft 26.x (Bedrock 26.0–26.40).
The plugin/extension id stays geyserextras (command /geyserextras, config folder, extension id), so existing GeyserExtras configs keep working.
Requirements
- Geyser 2.11.1 (older builds are not supported; use the previous upstream releases for those)
- Java 21+ to run the plugin (MC 26.x servers themselves require Java 25)
- Velocity users: Velocity 4.0.0+ required (3.5.x fails with Geyser 2.11.1)
Changes since upstream v2.0.0-BETA-11
Geyser 2.11.1 port
org.geysermc.geyser:coreunified to2.11.1-SNAPSHOTin all modules; Java toolchain 17 → 21;extension.ymlapi →2.11.0VideoSection: adapted tocooldownType()and the newCooldownTypeenum (CROSSHAIR/HOTBAR)BedrockEmoteListInjector: rewritten — upstream translator was removed in 2.11Action: MCPLClientCommand.STATS→REQUEST_STATS- blockdisplay workaround: adapted to the 2.11 entity system refactor (
EntityTypeBase/VanillaEntityType,EntitySpawnContext,GeyserEntityDataManager,Block.asItem()) Entity.getGeyserId()→geyserId();SkinSaver:BedrockClientDatanow returnsbyte[];DebugSection:session.playFabId();getScale()→getDisplayScale()
Rename
- Display names and jar names are now GeyserPlus; repository moved to leemwood/GeyserPlus
Verified
- Builds for all modules (core / extension / spigot / velocity / bungee)
- Startup-tested with Geyser 2.11.1-b1210 on Standalone (extension), Paper 26.2, Velocity 4.0.0 and BungeeCord
- In-game tested on Paper 26.2 + Floodgate 2.2.5-b138 (
auth-type: floodgate) with a real Bedrock client
Downloads
| File | Platform |
|---|---|
GeyserPlus-Spigot.jar |
Spigot / Paper / Purpur |
GeyserPlus-Velocity.jar |
Velocity |
GeyserPlus-BungeeCord.jar |
BungeeCord / Waterfall |
GeyserPlus-Extension.jar |
Geyser Standalone extensions/ folder |
GeyserPlus.jar |
Core jar (for developers) |
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:MMHzAVoW:UdILF3vE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MMHzAVoW:UdILF3vE"
}
