All versions
1.3.3
Release
The Unseen Entity 1.3.33 weeks ago 235
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
The Unseen v1.3.3 - Endless Fields & Cyber Wormhole Update
Endless Wheat Fields (Recovery Sector)
- Reworked the Recovery Sector dimension with infinite golden wheat fields stretching to the horizon.
- Added detailed procedural structures on a spaced grid: 3-Story Windmill, Historic Wooden Chapel with Bell Tower, Sunflower Apiary, Ancient Stone Well, Grain Silo & Barn, Scarecrows, and Telegraph Poles along the highway.
- Completely removed vanilla villages and vanilla structures from the flat dimension.
- Added dedicated teleport commands: /unseen_goto_fields, /unseen_tarlalar, and updated /unseen_tp fields.
- Added custom ambient music "Where The Grass Bends" with smooth 17-second loop pauses.
- Added new collectible Music Disc: "The Unseen - Where The Grass Bends" available in the Creative Tab and hidden world loot chests.
Cyber Wormhole Extraction
- Replaced the static block portal at the end of the Wireframe Void bridge with a dynamic, rotating 3D Cyber Wormhole.
- Added magnetic gravitational pull mechanics that lift and draw the player into the singularity to initiate the sanctuary transition.
Gameplay & Quality of Life Fixes
- Added Death Location Respawn: Players now respawn at their exact death position in their respective dimension instead of being sent to the Overworld.
- Added Void Fall Protection: Falling off the wireframe bridge during the escape sequence instantly teleports the player safely back onto the bridge.
- Fixed structure clipping and protected the main highway corridor from overlapping obstacles.
- Optimized client-side rendering and particle performance.
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:LZKrTql3:2wgXhqmj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LZKrTql3:2wgXhqmj"
}

