The Temple of Time is the beginning of the sword progression. Its template contains the special sword-bearing shrine that gives you the first Goddess Sword, and the structure is also tied to Navi.
Where can it generate?
| Biome ID or tag | Requirement |
|---|---|
#minecraft:is_forest | Vanilla ID or built-in tag |
#c:is_plains | Optional compatibility tag (requires matching data) |
#c:is_rare | Optional compatibility tag (requires matching data) |
Biome membership is an eligibility rule, not a guarantee. Optional #c: tags only broaden placement if populated in this world or modpack.
Confirmed structure-specific behavior
Its structure definition includes an ambient Navi spawn override (weight 1, one at a time). Navi’s own spawn rules also restrict wild spawning to the Temple of Time area. The local structure audit confirms the template itself contains exactly one mastersword:sword_shrine_sword block, so the first Goddess Sword shrine is physically part of the Temple of Time template.
See Navi and companion fairies and the Sword Shrine guide.
Inside the structure: decoded template
The temple_of_time.nbt template is 102 × 82 × 56 blocks with 468,384 explicit block records. The counts refer to the saved template, not a guarantee that every server places the same structure.
- The locally decoded template contains exactly one mastersword:sword_shrine_sword block, confirming the first Goddess Sword shrine is physically part of the Temple template.
- It also contains one Farore Fire, one Din Fire, one Nayru Fire and one Temple music block; no chest block entities or saved entities were reported by the audit.
- The audit captured the music block at local (56, 23, 27); its selected-coordinate report did not record the shrine block position, so its exact local shrine coordinate is left unspecified.
Notable local template coordinates
| Feature | Local (x, y, z) |
|---|---|
| Temple music block | (56, 23, 27) |
Locations are coordinates inside the saved saved structure template. Generated structures can be shifted and rotated; use these as relative exploration clues, not /tp commands.
Compare all ten structure interiors → · Custom chest loot tables →
Finding it
- Search eligible biomes in newly generated terrain. Config changes do not alter old chunks.
- On a cheats-enabled world, try
/locate structure mastersword:temple_of_time, provided the built-in pack is enabled. - Keep in mind that the shared generator requires relatively flat land and excludes village-adjacent candidates.
World-generation rules
Structure generation is affected by enabled data packs, biome-tag population and server configuration. The default spacing is 40 chunks, minimum separation is 30 chunks, and a candidate is excluded within 10 chunks of village structure-set candidates. The custom land generator rejects starts at a sampled center height of 250 or above and layouts whose sampled surface varies by more than four blocks.
Generation notes
These biome rules come from the structure’s built-in biome tag and worldgen definition. Server configs or datapacks can change what appears in a world. Structure definition: src/main/resources/packs/temple_of_time/data/mastersword/worldgen/structure/temple_of_time.json.
This page documents saved block/entity records and any linked loot-table JSON. It does not claim to solve a dungeon puzzle, guarantee every random reward, or verify an actual in-game screenshot.
← Back to all structures · Loot and acquisition
What is actually inside the Temple
The complete Temple template measures 102 × 82 × 56 and contains 468,384 explicit block records. The locally decoded palette contains exactly one each of mastersword:sword_shrine_sword, mastersword:farore_fire, mastersword:din_fire, mastersword:nayru_fire, and mastersword:music_block, plus twelve Gold Blocks.
The audit did not report any chest block entities or saved entities in the Temple NBT. The Temple music block is recorded at local template coordinate (56, 23, 27). The current audit’s selected-coordinate list did not capture the special shrine block’s exact coordinate, so the guide confirms the shrine is present without assigning it an unsupported XYZ.
The source code already established what the sword-bearing shrine does. The local structure audit now establishes that one such block is actually embedded in the Temple of Time template.