Tags
Creators
Details
4.0.0
Compatibility
Changes
ExtendedHorizons V4
ExtendedHorizons V4 is a complete rewrite of V3, focused on simpler internals, efficient chunk delivery, lower transport overhead, and reliable synchronization of distant terrain and players.
Chunk Streaming and Performance
- Rebuilt the chunk reading, preparation, and delivery pipeline.
- Reads pregenerated terrain directly from disk without keeping distant chunks loaded for simulation.
- Shares chunk reads and compressed packet data between players viewing identical terrain.
- Reduces redundant chunk transmissions through packet reuse and duplicate suppression.
- Prioritizes terrain in the player's direction of travel and fills surrounding terrain while stationary.
- Improves chunk delivery during fast movement and elytra flight.
- Adds configurable per-player and global bandwidth budgets, worker counts, and in-flight limits.
- Reduces allocations, cache churn, and contention in shared data structures.
- Consolidates TCP flushes to reduce transport overhead and improve responsiveness under load.
Distant Players
- Reworked player visibility beyond the server's native tracking distance.
- Synchronizes movement, equipment, supported actions, and skin layers.
- Improves transitions between distant-player rendering and native server tracking.
- Fixes player-info and TAB-related visibility issues.
- Provides configurable tracking limits, update intervals, equipment, and action synchronization.
Live Terrain Updates
- Updates distant terrain when blocks are modified.
- Supports block placement, breaking, and supported natural block changes.
- Adds optional WorldEdit and FastAsyncWorldEdit integration.
- Invalidates edited snapshots and refreshes affected chunks.
Anti-Xray
- Adds optional block masking specifically for extended chunks.
- Supports a customizable hidden-block list.
- Preserves intentionally empty optional configuration entries.
Compatibility and Configuration
- Supports Minecraft 1.21.11, 26.1, 26.2, and 26.3.
- Uses Paper/Folia scheduling APIs for EH's scheduled work.
- Supports custom world heights.
- Includes fixes for Geyser chunk flickering.
- Adds runtime delivery, cache, and failure statistics.
- Integrates FastStats through MapacheeeLib.
- Adds missing required configuration entries during startup and reload while preserving existing values.
Upgrading from V3
- Update both ExtendedHorizons and MapacheeeLib.
- Back up your V3 configuration and generate a fresh V4 configuration: the schema has changed.
- Keep the server's native view distance below EH's extended distance.
- Use pregenerated terrain. V4 streams available chunks and does not generate missing terrain.
- Far-player tracking, live chunk updates, WorldEdit integration, and Anti-Xray are optional and must be enabled as needed.
Performance depends on player distribution, hardware, terrain, enabled features, and network capacity. See the README in github for benchmark results and methodology.
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:RTpACLoD:FdYrHtDF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RTpACLoD:FdYrHtDF"
}

