Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 3 months ago
All versions
2.6.5-neoforge+mc1.21.1
Release
2.6.5-neoforge+mc1.21.13 months ago 475.6K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
YSM 2.6.5 Changelog
Performance & Stability
- Fixed an issue where the game would freeze after long runtime on Linux and Android;
- Improved renderer scheduling for slight performance gains, reducing load and power consumption on Android;
- Optimized rendering of opaque models; improved model memory management;
- Note: Once a model uses semi-transparent textures, rendering efficiency will drop significantly. It is recommended to minimize the use of transparency;
Compatibility
- Added support for Minecraft 26.1.2 NeoForge;
- Automatically disables linked mod features when the linked mod version is too low (instead of crashing with an error);
Features
- Added configuration options to disable certain high-risk linked mod features;
- For example, mods like Sophisticated Backpacks and Parkour that frequently change their core code;
- Improved stability of the radial menu configuration UI;
- Added support for lance animations; the animation category name is
lance;
Bug Fixes
- Fixed an issue where some Molang events were not firing correctly;
- Fixed incorrect pitch rotation not being applied to custom minecart models;
- Fixed rotation anomalies in preview models and paper doll rendering in certain situations;
- Fixed katana group positioning and TaCZ pistol animation issues for some models;
- Fixed the issue where maids using YSM models would clip through entertainment blocks;
Model Updates
- Updated models: Mini Wine Fox, Holy Wine Fox, Elf Wine Fox, Survivor Wine Fox, K Snail;
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:86xjpqqS:HZWaR0LY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:86xjpqqS:HZWaR0LY"
}

