CWES Field Journal Entry Standard

Purpose

Members of the Cubed Worlds Explorers Society are trained observers. Their field journals should read like in-world exploration records, but they should also preserve practical Minecraft information so a location can be found, revisited, verified, rebuilt, or adapted later.

Every CWES field journal entry should include the required fields below.

Required Header Fields

Use this header format for all CWES field journal entries:

Cubed Worlds Explorers Society
Field Journal of Explorer [Explorer Name]
World Name: [World Name]
Minecraft Edition and Version: [Bedrock or Java] [Version Number]
Seed Number: [Seed Number]
Primary Coordinates: [X, Y, Z]
Secondary Coordinates: [Optional additional points of interest]
Nearest Known Landmark: [Landmark, settlement, river, road, or archive reference]
Survey Region: [Plain-language location description]
Subject: [Primary discovery or investigation subject]
Discovery Date: [In-world date or real recording date]
Weather and Light Conditions: [Conditions at time of survey]
Status: [Preliminary, Confirmed, Mapped, Recovered, Restricted, Lost, or Archived]

Required Location Data

Every field journal must include:

• World name.
• Minecraft edition.
• Minecraft version number.
• Seed number.
• Coordinates of the main discovery.
• Any useful secondary coordinates.
• Nearest known landmark.
• Survey region.

Coordinates should be specific enough that another explorer can find the place without guessing.

Required Discovery Data

Every field journal should include:

• Name of the reporting Explorer.
• Subject of the discovery.
• Discovery date.
• Weather or light conditions if relevant.
• Current record status.
• Summary of what was found.
• Notes on visible materials, structures, artifacts, or environmental clues.
• Recommendations for follow-up survey work.

Recommended Body Structure

Use this structure for most public-facing CWES field journals:

1. Header metadata.
2. First approach or discovery moment.
3. Site description.
4. Artifact or structure notes.
5. Interpretation.
6. Uncertainties or competing explanations.
7. Recommended follow-up actions.
8. Builder adaptation notes if the record is part of a tutorial or lore guide.

Tone Guidelines

CWES entries should sound observant, practical, and curious.

The Explorer may speculate, but speculation should be clearly signaled. A trained Explorer records what is known, what is inferred, and what remains uncertain.

Good phrasing:

• The site appears to...
• This suggests...
• I estimate...
• No direct evidence was found for...
• Further mapping is recommended before...

Avoid making every mystery certain. The best field journals leave room for later discoveries.

Public Archive Note

When a CWES journal is published as part of Andy's Archives or a tutorial pack, include links to related pages when relevant:

• Matching world page.
• Matching archive category.
• Related location records.
• Related tutorial or build guide.
• Related video or stream.

For tutorial packs, the CWES record can act as a lore example, showing viewers how to turn a build into an archaeological discovery or exploration record.