Revelationary Mod (26.2, 1.20.1) – Rewarding Game Progression

Revelationary Mod makes it so that certain aspects of the game will be unlocked or revealed only if you meet a certain criteria or reach a certain point of game progression. The mod by itself does not make any changes to the vanilla game. It is meant to be used by designers of progression based mods or modpacks. With this mod, you will be able to use datapacks or the Revelationary API to reveal certain blocks only when the player reaches a certain point of progression in the game. As the developer states, a plain filled with stone will be filled with lush and greenery as the player defeats a boss mob. The possibilities are endless.

Features:

• Data-pack revelations: Declare revelations in resources/data/<mod_id>/revelations. Map disguised block_states and items to their real representations. Each revelation links to an advancement that controls visibility.
• Per-player visibility: Each player’s view of the world is independent – a block can be revealed for one player and still disguised for another.
• Disguise behavior: Disguised blocks keep the original block’s properties (hitbox, light transparency, behavior). Only visuals and drops change unless you modify behavior via the API.
• Advancement-driven: Use existing Minecraft advancements as unlocking conditions (any advancement can trigger a revelation).
• API for modders: Register Revelation-aware items/blocks, provide cloak mappings, react to cloak/uncloak events, and register global callbacks when revelations happen.
• Performance: Designed to be lightweight and performant (reveals are resolved client-side per player; worldgen not modified).

Limitations & considerations:

• Only visuals and drops change by default. Disguised blocks keep original physical properties. Choose disguises that match (e.g., stone/deepslate for ores).
• If you need different hitboxes or interactions while disguised, use the API to change behavior dynamically.
• Design carefully to avoid confusing players (use sensible disguises and clear advancement triggers).

Quick examples (concise):

• Data pack JSON – place under data/<mod_id>/revelations/<name>.json:

  {
  "advancement": "spectrum:milestones/reveal_quitoxic_reeds",
  "block_states": {
  "minecraft:grass": "minecraft:beacon",
  "minecraft:tall_grass": "minecraft:obsidian"
  },
  "items": {
  "minecraft:nether_star": "minecraft:gunpowder"
  }
  }

• Registering a revelation-aware item (Java) – implement RevelationAware and provide cloak identifiers and mappings. Keep methods: getCloakAdvancementIdentifier(), getItemCloak(), onCloak(), onUncloak().
• Global callback – use RevelationHolder.registerRevelationCallback(...) to run code when players uncloak blocks/items (e.g., show UI prompts or trigger sounds).

Where to look in the repo (wiki pages):

• Accessibility Settings
• Advancement API
• Advancement Criteria
• Revelation API
• Revelations via Data Pack

Best practices for designers:

• Pick disguises that match physical properties (hitbox, light). Stone/deepslate work well for ores.
• Gate new resources with meaningful milestones (bosses, milestones) to avoid overwhelming players.
• Use small, clear advancement descriptions so players understand why something became visible.

Screenshots:

Revelationary Mod Download Links