Links
Tags
Creators
Details
All versions
1.0.3
Release
Thaumic All Aspect 1.0.35 months ago 464
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Changes
v1.0.3 (Changelog)
- Fixed the “0 aspects / fake aspects” issue: if an
AspectListhassize > 0but total amount is0(total == 0), it could be mistakenly treated as “already has aspects”, causing the mod to skip re-derivation (leading to HUD/machine readings showing=0, and potentially crashes). Now such lists are treated as “no aspects”, so the correct derive/backup logic runs. - Enforced cache/registration safety: before writing to Thaumcraft,
aspect-cache.cfg, or logs, the code guarantees each aspect amount is at least1to prevent persisting0-value aspects. - Hardened recipe-first pipeline behavior: derivation checks are driven by “positive total aspect amount” rather than only
size > 0, preventing early termination by fake-aspect states and improving multi-step chains (e.g.,A=BthenA+B=C). - UI visibility enhancement for small-piece items: for keyword hits like
nugget/粒/dust/shard, a post-scan adjustment upgrades all-1 aspect sets to2(same aspect types) to make them easier to read. - Configuration-driven tuning:
maxRecipeDepthandrecipeFirstMaxRoundsare read from config (default pipeline rounds remain6) for better control in large modpacks. - NEI integration is additive: NEI recipes are merged/added with vanilla indices to avoid losing recipes when NEI coverage is incomplete.
- Cache seed + incremental scan: when
aspect-cache.cfgexists, it is used as an initial seed; the derive pipeline still runs to fill only targets that are still missing aspects, then the updated cache is written back.
v1.0.3(更新日志)
- 修复“0 要素/假要素”问题:当
AspectList满足size > 0但要素总量total == 0时,可能会被误判为“已拥有要素”,从而跳过重推导(导致 HUD/机器读数显示=0,并可能增加崩溃风险)。现在把这种情况视为“无要素”,确保推导/兜底逻辑正常执行。 - 强化写入安全性:向 Thaumcraft 注册、写入
aspect-cache.cfg以及日志输出前,确保每个要素数量至少为1,避免出现0值要素被持久化。 - 加固配方优先(Recipe-first)流程:衍生判定改为依据“要素总量是否为正”,而不是仅看
size > 0,避免假要素状态导致过早终止,并提升链式配方覆盖(如A=B再到A+B=C)。 - 小件命中词 UI 可见性增强:对包含
nugget/粒/dust/shard等关键词的命中项,扫描后若所有要素都恰好为1,会自动提升为2(要素类型不变),使显示更清晰。 - 配置化调优:
maxRecipeDepth与recipeFirstMaxRounds从配置读取(默认配方优先轮数保持6),便于大整合包做性能/覆盖平衡。 - NEI 配方为“追加合并”:NEI 配方会与原版索引进行合并追加,避免 NEI 覆盖不完整时丢配方。
- 缓存种子 + 增量扫描:当存在
aspect-cache.cfg时先作为初始种子加载;随后仍会走推导管线,但只补全仍缺少要素的目标,最后重写更新后的缓存。
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:iQg9bRZN:H8vkWg0w"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iQg9bRZN:H8vkWg0w"
}

