Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 5 years ago
Updated 2 months ago
All versions
1.6.5-alpha.1-1.21.1
Beta
1.6.5-alpha.1-1.21.12 months ago 91
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
- Fixed the issue that the mod is incompatible with Forge/NeoForge and Sinytra Connector in 1.20.1 and 1.21.1.
- In 1.21.1, in the
methodmethod in the mixin annotation, no matter the specified value is a single method namefindCrosshairTarget(Yarn mapping), or a full method signature, the intermediary name remapped by Yarn only contains method namemethod_56153, and then when remapped by Sinytra Connector into official mapping, the method name ispick. In Yarn mapping, in theGameRendererclass, the method namedfindCrosshairTargetis only one, but in the official mapping, in theGameRendererclass, the methods namedpickare more than one (corresponding tofindCrosshairTargetandupdateCrosshairTargetin the Yarn mapping), so the target cannot be correctly located, causing the mixin to encounter errors. To solve this issue, I addedtarget = @Desc(...)into the code to help the game correctly find the method to apply mixin. - In 1.20.1, the
BeaconBlockEntityclass has only one method namedtickin both Yarn and official mappings, and Yarn correctly remaps it tomethod_16896. However, in the mod remapped by Sinytra Connector, the method name is stillmethod_16896, which is abnormal in Forge. To solve this issue, the relevant mixins have been set to be silently ignored, so exceptions will not be thrown when they are found, and the relevant mixins will not be applied in this case. This also means that, in 1.20.1, when using Forge/NeoForge and Sinytra Connector to run Mishang Urban Construction, custom-colored glass blocks and other blocks cannot tint beacon beams. If Sinytra Connector is updated in the future, this issue may be resolved.
- In 1.21.1, in the
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:rItLmRo4:NAygnnFq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rItLmRo4:NAygnnFq"
}
