Links
Tags
Creators
Details
1.2.0
Compatibility
Changes
๐ชช BedrockPassport 1.2.0
BedrockPassport 1.2.0 adds Folia support and moves BedrockPassport onto the Paper/Folia scheduler model instead of relying on the legacy Bukkit main-thread scheduler.
โก Folia support
- Added
folia-supported: true. - Player-bound deferred work now uses the owning entity scheduler.
- Command-block responses use the owning region scheduler.
- Plugin-wide reload work uses the global-region scheduler.
- Existing online players are resynchronized safely after
/bp reload. - Session protection fails closed while reload resynchronization is in progress.
- Deferred command responses preserve the original sender execution context instead of rediscovering region-owned state from an async callback.
๐งช Build-time compatibility checks
The build now:
- compiles normally against the Paper API;
- performs an additional source compilation against the Folia 26.2 API;
- rejects legacy
Bukkit.getScheduler(),Server#getScheduler()andBukkitRunnableusage in BedrockPassport sources; - verifies that the Folia support marker remains present.
โ Runtime verification
The LOCAL provider was runtime-tested on Folia 26.2 with Geyser, Floodgate and SkinsRestorer.
Verified behavior includes:
- BedrockPassport loading successfully on Folia;
- Folia scheduler detection;
- Bedrock/Floodgate backend join;
- disconnect and reconnect;
- switching between saved LOCAL identities.
๐ Existing account flows preserved
This release keeps the existing:
LOCALprovider;JAVA_ACCOUNTprovider;- Microsoft device-code verification;
- saved Java-account reconnect flow;
- targeted
/bp reset-login <javaName>; - global
/bp reset-login --all confirm; - same-Java-UUID re-verification protection;
- Floodgate coexistence handling;
- encrypted saved Java authentication state.
โน๏ธ Compatibility note
BedrockPassport can be Folia-compatible only within its own code and integrations. Geyser, Floodgate, authentication plugins, skin plugins and other server plugins used alongside it must also support Folia themselves.
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:xlbqOfvO:8duaD8lU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xlbqOfvO:8duaD8lU"
}

