0.5.0-beta.2-hotfix.2
Compatibility
Changes
Echo Protocol 0.5.0-beta.2 — Hotfix 2
This update focuses on fixes discovered during extended external survival testing on Minecraft 1.21.11.
Fixed
- Improved Echo visibility while keeping the target player's real Minecraft skin clearly recognizable.
- Reduced excessive transparency so Echoes are much easier to notice during normal gameplay.
- Echoes now use only very light transparency while remaining visually distinct from normal players.
- Fixed Memory Echoes frequently selecting idle, AFK, crafting, or mining segments instead of meaningful movement.
- Memory-based Echoes now prioritize continuous movement recordings when appropriate.
- Fixed Echoes repeatedly standing still and staring at the ground.
- Improved initial pitch/orientation for independent Echo types.
- Fixed Mimic movement issues caused by recorded absolute coordinates.
- Fixed Echo grounding on slabs and uneven terrain.
- Fixed Corrupted Memory progression being granted before a properly observable manifestation.
- Improved observation checks for several Echo-related advancements.
- Fixed rejected and unobserved events consuming excessively long cooldowns.
- Fixed failed/discontinuous events potentially leaving the Event Director locked.
- Added faster bounded retries after failed or unobserved manifestations.
- Improved Echo appearance sound readability.
- Improved cleanup and lifecycle handling for natural Echo events.
- Preserved collision-aware movement and blocked-route safety.
- Preserved real player skins and classic/slim model support.
Testing
- 61/61 automated regression tests passing.
- Tested on Minecraft 1.21.11 with Fabric.
- Final build tested through Prism Launcher.
- Tested using natural survival gameplay and the real Event Director rather than relying only on spawn/debug commands.
- Dedicated Fabric server startup and shutdown verified.
Compatibility
- Minecraft 1.21.11
- Fabric
- Java 21
- Fabric API required
Note
This is a bug-fix and polish update for 0.5.0-beta.2.
Larger gameplay additions and new horror behaviors are planned for a future beta.
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:yky5pji4:ht2PeQoG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yky5pji4:ht2PeQoG"
}

