Tags
Creators
Details
1.7.10
Compatibility
Required content
Changes
[1.7.10] - 2026-07-31
变更 / Changes
-
ScalableLux 不兼容声明绕过 / ScalableLux incompatibility declaration bypass: 使用 NeoForge 官方的
fml.toml依赖覆盖([dependencyOverrides])机制,绕过 Sable 的neoforge.mods.toml中对 ScalableLux 的type = "incompatible"声明,避免 NeoForge ModSorter 在启动阶段直接拒绝加载。/ Uses NeoForge's officialfml.tomldependency override ([dependencyOverrides]) mechanism to bypass Sable'stype = "incompatible"declaration against ScalableLux inneoforge.mods.toml, preventing NeoForge ModSorter from aborting startup.- fs 启动时自动检查并写入
fml.toml,无需用户手动配置。/ fs automatically checks and writesfml.tomlon startup, no manual configuration required. - 替代了 v1.7.9 中复杂且易出问题的 CoreMod 方案。/ Replaces the complex and error-prone CoreMod approach from v1.7.9.
- fs 启动时自动检查并写入
-
ScalableLux 兼容性 mixin 注入修复 / ScalableLux compat mixin injection fix: 修复
ScalableLuxCompatMixin的@At("NEW")target 格式不正确导致 mixin 扫描 0 个目标,simulated mod 加载时崩溃(Scanned 0 target(s))。/ FixedScalableLuxCompatMixin@At("NEW")target format causing mixin to scan 0 targets and crash when simulated mod loads (Scanned 0 target(s)).- 将 target 从
new <类名>(<描述符>)V改为纯类名net/minecraft/world/level/lighting/LevelLightEngine。/ Changed target fromnew <class>(<descriptor>)Vto plain class namenet/minecraft/world/level/lighting/LevelLightEngine.
- 将 target 从
-
控制台刷屏修复 / Console log spam fix: 修复无物理结构时
Attempted to teleport invalid/removed body (id=0), skipping警告每 tick 刷屏的问题。/ FixedAttempted to teleport invalid/removed body (id=0), skippingwarning spamming console every tick when no physics structures exist.- 警告改为 60 秒节流窗口,窗口内只输出一次。/ Warning now throttled to once per 60s window.
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:YS1hdEUp:AzaiOYcY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YS1hdEUp:AzaiOYcY"
}

