Tags
Creators
Details
2.5.0
Compatibility
Changes
This release updates DoorsReloaded's mod and plugin to Minecraft 26.3, carrying forward the features, improvements, and fixes from 2.4.0.
✨ New Features & Changes
- ✅ Minecraft 26.3 Support - Updated both the Fabric/Quilt mod and Paper/Purpur/Folia plugin for Minecraft 26.3.
- ✅ Updated Platform Dependencies - Updated Fabric Loader, Fabric API, and the Paper API target for Minecraft 26.3.
- ✅ Updated Platform Metadata - Both platform jars now declare the correct Minecraft 26.3 compatibility requirements.
📦 Downloads
| Platform | File | Minecraft Version |
|---|---|---|
| Paper/Purpur/Folia | DoorsReloaded-2.5.0-Paper.jar |
26.3 |
| Fabric/Quilt | DoorsReloaded-2.5.0-Fabric.jar |
26.3 |
🔧 Technical Changes
- Updated Fabric Loader to
0.19.5. - Updated Fabric API to
0.161.0+26.3. - Updated the Paper API target to
26.3.build.177-stable. - Adapted Fabric gameplay permissions to the permission API included with Fabric API for Minecraft 26.3.
- Verified both platform builds and the existing regression tests against the Minecraft 26.3 targets.
📋 Compatibility Summary
- ✅ Paper 26.3
- ✅ Purpur 26.3
- ✅ Folia 26.3 (region-threading aware)
- ✅ Fabric 26.3
- ✅ Quilt 26.3
- ✅ Java 25 required
- ❌ Spigot / CraftBukkit (not supported)
📝 Migration
From v2.4.0 on Paper/Purpur/Folia:
- Back up your server and update it to Minecraft 26.3 using Java 25.
- Remove
DoorsReloaded-2.4.0-Paper.jarfromplugins/. - Add
DoorsReloaded-2.5.0-Paper.jar. - Restart the server.
From v2.4.0 on Fabric/Quilt:
- Back up your world and update to Minecraft 26.3 using Java 25.
- Install Fabric Loader
0.19.5or newer and Fabric API for Minecraft 26.3. - Replace
DoorsReloaded-2.4.0-Fabric.jarwithDoorsReloaded-2.5.0-Fabric.jarinmods/. - Launch the game or restart the server.
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:rx5M5rp4:5QKRFoYe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rx5M5rp4:5QKRFoYe"
}

