Tags
Creators
Details
2.3.5
Compatibility
Required content
Changes
Gateway of Doom – 2.3.5
New Vanilla / Custom selection: When an operator first joins the world, a selection screen lets them choose the default portal set for the entire server. Selecting an option returns directly to the game.
New Vanilla presets: Crypt Gateway, Inferno Gateway and Abyss Gateway feature classic Minecraft enemies, fixed waves and Vanilla bosses.
Custom portal set: Runestone Gate, Necromancer Gate, Maelstrom Portal and Golden Rune Gate feature themed enemy waves and custom bosses: Runeroot, Reaper, Voidwing and Azure Ronin.
Switch portal sets at any time: Open /doom menu → Key Profiles → Vanilla / Custom to change the selection without restarting the server. New key drops and automatic default events follow the selected set. Custom profiles, edits to both sets and ongoing battles are preserved.
Reworked default rewards: All default encounters now award guaranteed materials, experience bottles and completion XP, alongside chances for enchanted books, equipment and rare trophies. Rewards scale with each encounter, including Netherite, Totems and Elytra in advanced encounters. Golden Rune Keys remain rare bonus rewards in the three main Custom portals.
Existing reward customizations preserved: Unmodified default rewards update automatically. Manually edited rewards and custom profiles retain their settings.
New enemy highlight defaults: Wave enemies, boss guards and bosses receive a glowing outline when they are at least 20 blocks from their portal. The outline disappears when they return closer. Existing profiles retain their saved settings.
Improved shader compatibility: Fixed custom portal rendering issues and Iris rendering crashes on Minecraft 26.3, including problems when reloading shaders and resources.
Fixed chunk loading: Gateways now use dedicated chunk tickets. Closing a gateway preserves chunk-loading requests from Vanilla and other mods.
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:Z7xAH01M:IwTyaZi3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Z7xAH01M:IwTyaZi3"
}

