Tags
Creators
Details
2.3.0
Compatibility
Changes
This release updates DoorsReloaded for Minecraft 26.1.x and prepares both platform builds for the latest Paper and Fabric toolchains.
✨ New Features & Changes
- ✅ Minecraft 26.1.x Support - DoorsReloaded now supports Minecraft
26.1,26.1.1, and26.1.2. - ✅ Updated Fabric/Quilt Build - Migrated the Fabric mod to the Fabric 26.1 toolchain and official Mojang mappings.
- ✅ Updated Paper/Purpur/Folia Build - Updated the plugin build to the Paper 26.1.2 stable API line.
- ✅ Java 25 Support - Both platform builds now target Java 25.
- ✅ Updated Platform Metadata - Modrinth, Fabric, and Paper metadata now advertise the correct 26.1.x compatibility range.
Downloads
| Platform | File | Minecraft Version |
|---|---|---|
| Paper/Purpur/Folia | DoorsReloaded-2.3.0-Paper.jar |
26.1.x |
| Fabric/Quilt | DoorsReloaded-2.3.0-Fabric.jar |
26.1.x |
Technical Changes
- Updated Fabric Loom to
1.16.2 - Updated Fabric Loader to
0.19.2 - Updated Fabric API to
0.150.0+26.1.2 - Updated Paper API target to
26.1.2.build.66-stable - Split Paper API versioning from the Fabric Minecraft version property
- Updated release docs, README, changelog, and platform metadata
Compatibility Summary
- ✅ Paper 26.1.x
- ✅ Purpur 26.1.x
- ✅ Folia 26.1.x (region-threading aware)
- ✅ Fabric 26.1.x
- ✅ Quilt 26.1.x
- ❌ Spigot / CraftBukkit (not supported)
Migration
From v2.2.0 on Paper/Purpur/Folia:
- Remove old
DoorsReloaded-2.2.0-Paper.jarfromplugins/ - Drop in
DoorsReloaded-2.3.0-Paper.jar - Restart the server
From v2.2.0 on Fabric/Quilt:
- Make sure you are running Java 25
- Install a compatible Fabric Loader and Fabric API for Minecraft 26.1.x
- Replace
DoorsReloaded-2.2.0-Fabric.jarwithDoorsReloaded-2.3.0-Fabric.jar - Launch the game
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:4sXMh9tV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rx5M5rp4:4sXMh9tV"
}

