Tags
Creators
Details
3.2
Compatibility
Required content
Changes
๐ Safra 3.2 Update
๐ Safra has abandoned its custom internet transfer system in favor of a modular one. It has switched to the QUIC system, which supports the latest HTTPS/3 protocol.
โ ๏ธ Note
Connection parameters are calibrated based on internet speed during the initial handshake (static, not dynamic).
โก Optimizations
- ๐ Eliminated rubberbanding and stuttering.
- โฑ๏ธ Reduced load times for faster world entry.
- ๐ฅถ Resolved the sudden freezing issue that occurred when sharing the game.
- ๐งต Optimized to use fewer threads.
- ๐ฆ Implemented safeguards against data loss during transfer.
- ๐ค Established a P2P connection infrastructure where both parties exchange messages to overcome NAT issues.
๐บ๏ธ Mod Compatibility
- ๐ Fixed the JourneyMap reset issue.
- ๐ When changing an in-game rule, it now overwrites only the specific rule that was modified. - You can now use mods for game rules
- ๐งฉ Fixes implemented for Fabric/ModMenu
๐ ๏ธ Resolved Issues
- ๐ Interrupting the connection while loading now redirects you to the server list instead of the main menu
- ๐ฃ๏ธ Added text-to-speech support for the code-sharing system (a feature no one will likely use :D)
- ๐น Added support for video links to assist anyone encountering issues later (the video isn't ready yet :D)
- โณ Fixed the issue where the code would become invalid after a certain period
- ๐ If you are streaming and don't want the code to appear in the chat, you can set
dontSayCodetotruein the config file
๐งน Code Cleanup
- ๐ Line count reduced by half: optimized by cutting it from 9.3k lines to approximately 5.4k lines
๐ Security & Servers
- ๐ Added encrypted connection capability between you and your friend
- ๐ Expanded audit logs
- ๐ก๏ธ Strengthened security architecture for Bedrock servers
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:XtEbzMqr:aSjnz8S9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XtEbzMqr:aSjnz8S9"
}

