Player question · Missing villages

Matcha Flavored villages generate by their own pack rules

Village Beta buildings, the Abbey, Papal Outposts, biome-specific starts, wider placement spacing, archaeology, and chest pools explain why exploration can differ sharply from vanilla.

Guide covers: Pack 1.12 · Java 26.2
01
Answer first 01

Test Matcha Flavored villages in new terrain with world data active

The first check for missing Matcha Flavored villages is chunk age. A data pack cannot rebuild terrain that already generated before installation or before a world-generation change. Confirm that pack 1.12 is active in the world, then travel into genuinely unexplored chunks or create a disposable world on Minecraft 26.2. A matching resource pack changes appearance but cannot make a village generate.

Pack 1.12 replaces the village structure set with plains, desert, savanna, snowy, and taiga variants at equal structure weights. Its random-spread placement uses spacing 80 and separation 50. That makes the search pattern different from an assumed vanilla route and explains why one short trip through old or unsuitable terrain is not a valid generation test.

  • Plains villages allow plains and sunflower plains.
  • Desert villages use desert; savanna villages use savanna.
  • Snowy villages use snowy plains.
  • Taiga villages allow taiga plus old-growth pine and spruce taiga.
02
Templates 02

Matcha Flavored villages use buildings, roads, and a central well

Matcha Flavored villages start from the Village Beta town-center pool and its well, then use custom road and building pools. Pack 1.12 retains 16 Village Beta NBT templates: 9 active building layouts named small, medium, large, and extra-large; 4 road pieces; 1 well; and 2 Indev building templates present in the archive. The active building pool gives different relative weights to the 9 normal layouts.

Those weights affect which building piece the jigsaw pool selects; they do not promise that every village contains every house. The extra-large_2 layout has the largest individual building weight at 5, while several other layouts range from 1 to 4. Terrain fit, jigsaw assembly, placement rules, and the rest of the pool still shape the finished village.

03
New structures 03

Abbeys and Papal Outposts add two map-led exploration routes

Pack 1.10 added the overgrown Abbey as a late-mid to late-game dungeon and kept it in 1.12. The structure accepts forest and dark forest biomes, uses random-spread spacing 60 and separation 40, and excludes locations within 16 chunks of the village structure set. Its room pools include entrances, puzzles, checkpoints, vault and heart boons, hazards, and trial-spawner spaces; the current creator guidance recommends preparing with strong gear and food rather than treating it like a normal village.

An Archaeologist can sell an Abbey explorer map. For a controlled copied-world test, `/locate structure minecraft:abbey_overgrown` checks whether the current pack registers the structure without pretending that a map or one seed guarantees nearby generation. Version 1.12 also adds a craftable Ominous Trial Key and a 20% key-item drop route as a workaround for unreliable ominous spawner ejection inside the Abbey.

Papal Outposts reuse the `minecraft:pillager_outpost` structure identity, so maps and commands can label them as Pillager Outposts even though their pack content is different. The creator describes them as a more common, earlier source of a small number of Divine Fragments and Crystal Hearts plus potatoes and carrots. Test both structures only in new chunks after updating.

  • Abbey biome tag: forest and dark forest.
  • Abbey placement: spacing 60, separation 40, with a village exclusion zone.
  • Archaeologist maps can point to Abbeys and Papal Outposts.
  • Papal Outposts register under the Pillager Outpost structure identity.
04
World rules 04

Biome and dimension overrides provide environmental context

Each of the 5 village starts points to the Village Beta town center but keeps an explicit biome list. Plains and sunflower plains share one start; taiga includes both old-growth pine and old-growth spruce variants; desert, savanna, and snowy plains have their matching starts. Searching a visually similar but unsupported biome wastes time even when the pack is installed correctly.

Dimension and biome definitions can also change environmental context while familiar names remain on screen. For a clean test, record the biome from the debug screen, confirm that the chunk is new, and compare more than one seed. If the same valid biome repeatedly produces vanilla-only villages in new worlds, verify the data-pack copy and conflicts with other world-generation packs.

05
Rewards 05

Chest and archaeology tables answer what a location can yield

A Matcha Flavored villages reward claim belongs to the applicable chest or archaeology pool, not to the building filename. Chests can use weighted entries, conditions, functions, or nested pools, while suspicious blocks use their own selection context. Finding the right building therefore does not guarantee one specific item.

Weights remain relative inside an active pool. A listed item is not guaranteed in every generated structure, and a nested table can add another selection step. When reporting a missing reward, capture the structure or context, expected item, pack version, seed if relevant, and whether the chest or suspicious block was generated before the pack update. Existing chunks can preserve older world results.

  • Use the supported biome list to choose where to explore.
  • Use new chunks to test whether the village can generate.
  • Treat chest and archaeology contents as possible rewards, not guarantees.
  • Use a fresh matching-version world when testing generation changes.
06
Troubleshooting 06

Separate shipped rules from one seed's observed result

Pack analysis proves the 5 village starts, their biome lists, the spacing and separation values, the Village Beta template pools, and the Abbey and Papal Outpost registrations shipped in 1.12. It does not prove that every eligible seed produces a structure near spawn or that every room and reward appears. Minecraft placement randomness, terrain fit, version state, and already-generated chunks still require controlled gameplay tests.

For a useful missing-village report, include the seed, coordinates, biome, whether the chunk was new, Minecraft and pack versions, and every other world-generation data pack. That evidence can distinguish ordinary spacing from an inactive pack, an old chunk, an unsupported biome, or a conflict.

The official project name uses the Matcha Flavoured spelling. Search phrasing never overrides the shipped placement rules, matching-version world tests, or the behavior players can reproduce.

Quick answers

Questions players ask on the way

How many Village Beta templates are in pack 1.12?

The archive contains 16 NBT templates under the Village Beta structure family, covering buildings, roads, and a town-center well. The Abbey and Papal Outpost add separate template families.

Which biomes can generate Matcha Flavoured villages?

Pack 1.12 defines plains and sunflower plains, desert, savanna, snowy plains, taiga, old-growth pine taiga, and old-growth spruce taiga across its 5 village variants.

Where can the Abbey generate?

Pack 1.12 places the overgrown Abbey in forest and dark forest biomes, away from the village structure set; an Archaeologist map can help locate one.

Are all structure rewards guaranteed?

No. Chest and archaeology results can depend on pools, weights, conditions, functions, nested tables, and when the chunk was generated.

Why do I still see old or vanilla villages?

Existing chunks keep earlier generation. Test genuinely new terrain with pack 1.12 active, and check for another data pack overriding village structure sets or template pools.