Перейти к содержимому
Mineforgian

Create ReAutomated: Traces

A NeoForge 1.21.1 add-on for Create ReAutomated that scatters small ore outcrops on the surface above buried Ore Nodes

Загрузки
801
Подписчики
3
Обновлён
2 июля 2026 г.
Лицензия
All-Rights-Reserved

Опубликован 10 мая 2026 г.

Исходный код

A NeoForge 1.21.1 add-on for Create ReAutomated that scatters small ore outcrops on the surface above buried Ore Nodes. The point is simple: give you something to spot at world level, a hint that there's a Node worth digging for underneath, the way real ore deposits leave traces on the ground.

What it does

Whenever a chunk generates with an Ore Node in it, the mod looks for a flat patch of ground above the Node and stamps a small surface outcrop, a "trace". The trace is built from the Node's host stone (matching the deepslate, stone, or whatever the Node is buried in) studded with a configurable accent block on top. Cobblestone and cobbled deepslate are smoothed back to their natural variants, so traces look like exposed deposits rather than a pile of mining drops.

Works with custom Nodes (KubeJS, datapacks, sibling mods)

The mod doesn't care who registered a Node. As long as:

  1. The block extends createreautomated:ore_node (with its baseStone(...) set so the host material is correct).
  2. The block carries the createreautomated:ore_nodes tag.
  3. There's an entry in the createreautomatedtraces:trace_block_for_node data map mapping the Node block id to the surface accent block.

Biome coverage

By default traces are added to #minecraft:is_overworld and #minecraft:is_nether via the createreautomatedtraces:has_traces biome tag. To extend coverage to modded biomes (e.g. custom dimensions), add the biome or its parent tag to data/createreautomatedtraces/tags/worldgen/biome/has_traces.json in a datapack.

Notes

Detection runs only on freshly generated chunks. Existing worlds won't be retrofitted, and Nodes placed by hand or commands after worldgen won't trigger trace placement either.

⚠️Using this mod with the default Create ReAutomated Node generation settings could result in a lot of traces. We recommend reducing the tries per chunk; you can do so by downloading this datapack (or use the 0.5x version to halve the number of nodes generated). Here is an example: alt text

Ченджлог

0.3.0Релиз1.21.1 · 2 июля 2026 г.

Changelog

[0.3.0]

Added

  • Added size-based Trace templates, deterministic profiles, exact support masks, placement diagnostics, and a 2x2 steep-terrain fallback.
  • Added Trace Finder render tuning options for beam render radius and visible beam caps.

Changed

  • Reworked Trace placement to choose the largest fitting template, run at fluid_springs, and apply fixed safe cut/fill limits.
  • Placement now handles liquid spaces more deliberately, rejects logs/stems and protected blocks, and ignores non-blocking structures such as Strongholds, Trial Chambers, and Trail Ruins.
  • Trace Finder indexing no longer backfills existing chunks; it records only newly placed Traces or API-provided node records.
  • Trace Finder lookup and beam rendering are lighter, with non-blocking chunk reads, safer stale-record handling, and batched client-side beams.
  • Runtime Trace worldgen suppressions are now consumed when the matching Node position is seen.
0.2.0Релиз1.21.1 · 25 мая 2026 г.

Changelog

[0.2.0]

Added

  • Trace Finder discoveries are now dimension-aware, so traces at the same coordinates in different dimensions no longer conflict.
  • Trace index scan versioning now forces a one-time conservative rescan of older indexed chunks.

Changed

  • Trace generation now supports underwater and lava-covered terrain by anchoring traces on the solid bed below the fluid.
  • Ice-covered water now behaves like underwater terrain, so traces spawn on the water body's bed instead of on top of sea ice or iceberg ice.
  • New traces are indexed at the actual mapped trace block inside the generated template instead of an estimated center/top position.
  • Create is now declared as a required dependency because bundled recipes and default zinc trace mappings reference create:* resources.
  • Network payload protocol bumped to version 3.

Fixed

  • Fixed stale Trace Finder beams and compass targets after changing dimension.
  • Fixed valid traces being removed from the index when the saved position did not exactly match the visible trace block.
  • Fixed Trace Finder accepting arbitrary client-sent node ids.
  • Fixed generated features reporting success even when no trace was actually placed.
  • Fixed trace placement rejecting fluid-covered terrain entirely.
  • Fixed traces clearing logs while looking for or preparing an anchor.

Комментарии

Загружаем…