Links
Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 4 days ago
All versions
4.4.0-1.21.1
Release
Dark Doppelganger 4.4.0-1.21.1last week 53
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
4.4.0 — Intro Cutscene
The Dark Doppelganger now makes a proper entrance. Thanks to thrasos-dev for this contribution!
Intro cutscene
- When the boss is summoned, players within 48 blocks who can see where it appears watch it arrive. The view zooms in, the portal opens and the boss rises out of it, laughing. Then the camera swings out to a side-on shot of you and the boss facing each other before handing control back.
- It lasts 9.5 seconds, with letterbox bars and no HUD. You're held in place and can't be hurt while it plays, and neither can the boss. The boss music starts when the fight does.
- Multiplayer: everyone watches from their own position. Players who arrive later aren't pulled in, and the fight starts early if every watcher leaves, dies or changes dimension.
- Server owners can turn it off with the new
introCutsceneoption in the common config.
Spawn spot
- The boss now appears about 10 blocks past the altar, on the far side from the summoner, so everyone gathered at the altar sees it in front of them.
/darkd summon_doppelgangernow brings the boss in ahead of where you're looking instead of just behind you.- If there isn't room that far out, it tries closer spots.
Less on-screen text
- Removed the "DARK DOPPELGANGER" title card on summon and the "SHATTERED" title card on death.
- Removed the Summon Scroll's "No room for the Dark Doppelganger here." message.
Bug fixes
- Spawn animation: the boss no longer shows for a moment before its spawn animation starts, and the summon smoke no longer appears before the portal opens.
The fight is now covered by 17 automated in-game tests.
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:2vzHL83v:KhYY5c59"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2vzHL83v:KhYY5c59"
}

