1.0
Compatibility
Required content
Changes
BBS Extended Server Sync – 1.0 Sigma Update
The 1.0 Sigma release of BBS Extended Server Sync is here! With this update, all BBS assets are automatically downloaded to the client as soon as you join a server — no extra commands required. Everything is synced seamlessly, making joining a server smoother than ever.
New Features
Skin Management
-
/getskin name <playerName> – Instantly downloads and applies the selected player’s skin to everyone on the server.
-
/getskin url "https://www.example.com/skin.png" filename – Fetches a skin directly from a URL and distributes it to all players.
Model Synchronization
-
All server models are now automatically distributed to clients the moment they join.
-
If new models are added after joining, they can be synced with /bbs model reload.
-
Clients can request to upload a model to the server with /bbs model upload. This sends a request to the server owner.
-
The server owner can approve uploads with /bbs model accept <playerName>.
-
For full control, clients can overwrite existing models or resend everything from scratch with /bbs model upload --force.
Performance & Stability
-
Asynchronous system: Skin and model transfers now run on a fully asynchronous pipeline, providing better speed, reliability, and overall stability compared to the old system.
-
Large files may still cause timeouts depending on internet speed, but uploads are tracked and recover gracefully.
-
Built on the foundation of the previous release, with major improvements developed by byd3n1z and bay4lly.
Compatibility
- Fully tested and stable on Minecraft 1.20.1.
- Minecraft 1.20.4 support is unverified — stability cannot be guaranteed.
- To run on Forge, you must use the Sinytra Connector. Support
If you encounter issues or unexpected behavior, don’t hesitate to reach out via Discord (byd3n1z).
Summary
With 1.0 Sigma, BBS Extended Server Sync becomes more automatic, reliable, and user-friendly than ever. Assets now sync without extra commands, model and skin handling is smoother, and the new async system ensures better stability for everyone.
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:yWwOsHyX:IvbeVBCJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yWwOsHyX:IvbeVBCJ"
}

