Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last year
All versions
1.2.11-1.20.1-RELEASE
Release
Midrian WIMP - 1.2.11-1.20.1-BF2 years ago 49
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
1.20.1-midrian-wimp-release-1.2.11 - Bug Fixes
- Bug fixes:
- When attacking a bedrock and breaking it with a golden_bedsteel_pickaxe, the stone is restored.
- The way to use the golden_bedsteel_pickaxe has been changed. Now, to weaken the bedrock, you need to right-click.
- On the server:
- When crossing the bedrock and jumping into the void towards the nether, or using the End Star to enter the End, the server limits the player's fall speed, causing them to die from falling, or even removing the player from the server for "flying".
- The fall distance has been reduced in both the nether and the end to avoid these problems.
- When jumping into the void after killing the dragon, the player can still die from falling into the void.
- The teleport distance in the void of the End has been changed.
- When crossing the bedrock and jumping into the void towards the nether, or using the End Star to enter the End, the server limits the player's fall speed, causing them to die from falling, or even removing the player from the server for "flying".
- When attacking a bedrock and breaking it with a golden_bedsteel_pickaxe, the stone is restored.
NOTE:
- There is a bug in this version that causes the player's XP to disappear after teleporting. This is a synchronization bug that can be resolved by reopening the map or changing the gamemode. I'm working on fixing it.
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:U09S0PiD:hZEocAi6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:U09S0PiD:hZEocAi6"
}

