I found an issue when running TFC and Canary at the same time. When you enter a newly created chunk, TFC consider it to always be of "Temperate" climate with 10.0°C average temperature. When using the F3 screen, "Invalid Chunk Data" is displayed. If you save and quit, and reload the world, the chunk gets populated properly with climate data.

Looks like there does exist a system in 1.20 to ship a "default disabled features" file, but I can't be asked at the moment to figure it out. In any case, this is a user config, "disable part of canary that breaks TFC". as mentioned above.

This got fixed in Canary 0.2.9, btw.

This is quite likely something that Lithium breaks that we're relying on either as part of Forge or Minecraft functionality. If someone wants to look into this, there may be a specific optimization in Lithium that we can disable, or request to be disabled automatically, which can be tested via trying various things in the Lithium config.

Example screen short of F3 screen:

My guess is that it some Forge behavior that changes; Lithium tries hard not to break vanilla functionality so if that part is properly ported to Forge, the problem is more likely to lie in the Forge-specific parts of Canary.

Adding mixin.world.player_chunk_tick=false to canary.properties resolves this issue.

@DontStarve72 Thank you! I can indeed confirm that this helps.

Maybe this should be documented somewhere?