Defines the contract between vanilla “base” biomes and Latitude “out” biomes. Prevents incorrect assumptions about F3 biome, temperature/precip flags, and feature placement. Provides the required debugging interpretation for LAT_PICK logs.
This skill prevents a common error:
“F3 says biome = jungle, therefore cold/snow features cannot trigger.”
That is false when:
base=... in [LAT_PICK].out=... and typically what F3 shows.out while generation decisions still reference .base[LAT_PICK] logsGiven a log line like:
zone=EQUATOR base=minecraft:snowy_taiga out=minecraft:jungleInterpretation:
snowy_taiga.jungle.This is expected in the presence of base leakage and does not mean Latitude selection failed.
[LAT_PICK] template[LAT_PICK]
x=<x> z=<z> absZ=<absZ> radius=<radius> t=<t>
zone=<EQUATOR|TROPICS|ARID|TEMPERATE|SUBPOLAR|POLAR>
base=<minecraft:...>
out=<minecraft:...>
beachOverride=<true|false>
rareOverride=<true|false>
mangroveDecision=<...> cont=<...> ero=<...> weird=<...>
How to read it:
out is warm but base is cold, vanilla temperature-driven features may still attempt cold placements unless guarded (e.g., FreezeTopLayer).When a “contradiction” occurs (warm biome but cold artifacts):
[LAT_PICK] entries:
zone and compare base vs out.FreezeTopLayerFeature)Do not propose band-table changes based only on F3.
Observed:
minecraft:jungleCommon cause:
[LAT_PICK] base=snowy_plains out=jungleFreezeTopLayerFeature consults base biome climate → attempts snow.The assistant must provide: