Links
Tags
Creators
Details
All versions
1.0.2
Release
journeymaptfcintegration 1.0.2last month 41
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
English
[1.0.2] — 2026-07-13
Fixed
- Cache loss (Critical):
loadOnce()was previously triggered by client requests. External mods (e.g. SimpleBackups) could fireLevelEvent.Saveimmediately after server init, when memory only contained incomplete spawn chunk data, causingsave()to irreversibly overwrite the full historical disk cache.loadOnce()moved toJMTFCServerPlugin.initialize()— loads at server startup, no longer depends on client.save()now guarded byloadedFromDiskflag — refuses to overwrite disk beforeloadOnce()completes.loadOnce()merge with existing in-memory data fromChunkEvent.Load, disk takes priority, with merge count logging.
Added
/jmtfc clearcachecommand: OP level 2, clears all TFC cache (memory + disk file).- Full-chain diagnostic logging: covers loadOnce / save / warmup / buildPayload / handleRequestCache / handleCacheData / onCacheDataReceived / toggleOverlay / renderOverlay; INFO level reserved for lifecycle events only.
Changed
- Log downgrade: per-request logs (warmup, buildPayload, toggleOverlay, etc.) lowered to DEBUG to reduce noise.
- Fixed fully-qualified
ChunkAccessreference inTFCDataAccess.
中文
[1.0.2] — 2026-07-13
Fixed
- 缓存丢失(Critical):
loadOnce()原本依赖客户端请求触发,外部模组(如 SimpleBackups)可在服务端初始化后立即触发LevelEvent.Save,此时内存中仅有 spawn chunks 的不完整数据,save()直接覆盖磁盘上完整的历史缓存文件,造成不可逆的数据丢失。loadOnce()移至JMTFCServerPlugin.initialize()中执行——服务端就绪即加载,不再依赖客户端。save()新增loadedFromDisk守卫——loadOnce()未完成前拒绝覆盖磁盘。loadOnce()加载时与内存已有ChunkEvent.Load数据合并,磁盘优先,追加合并计数日志。
Added
/jmtfc clearcache命令:OP 权限(level 2),清除全部 TFC 缓存(内存 + 磁盘文件)。- 全链路诊断日志:覆盖 loadOnce / save / warmup / buildPayload / handleRequestCache / handleCacheData / onCacheDataReceived / toggleOverlay / renderOverlay 各环节,INFO 仅保留关键生命周期事件。
Changed
- 日志降级:per-request 日志(warmup、buildPayload、toggleOverlay 等)降至 DEBUG,减少正常使用时的日志噪音。
- 修复
TFCDataAccess中ChunkAccess全限定名引用。
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:lYsRkKJg:gfC4F6aT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lYsRkKJg:gfC4F6aT"
}



