Documentation category

Exploration and Narrative

This is where Hyper starts feeling less like a collection of systems and more like a world that can remember, guide, surprise, reward, and tell stories. Exploration and narrative can be as small as one NPC with one quest marker, or as large as a layered RPG structure with regions, quest chains, dialogue, codex entries, inspections, map markers, memories, level instances, and scripted sequences all working together.

Narratives Can Be Big

A simple narrative might ask the player to talk to an actor, inspect an object, follow a marker, complete an objective, and receive a reward. A larger narrative can touch almost every layer of the game: quests, dialogue, world map markers, guide prompts, regions, memory state, teleporting, databank unlocks, visual novel scenes, event triggers, level streaming, reputation, unlocks, inventory items, AI targets, and combat encounters.

That is the point of this category. It is not only about writing dialogue. It is about giving designers and developers the infrastructure to build playable story logic without hardcoding every beat into one-off Blueprints.

What You Can Build

  • Quest lines with objective updates, world markers, dialogue steps, rewards, and progression state.
  • Exploration loops where the player finds places, inspects objects, unlocks codex entries, and slowly understands the world.
  • Guided onboarding, tutorials, region-based discoveries, teleport points, scripted moments, and map-driven navigation.
  • Story-heavy systems such as visual novel scenes, sequence-driven events, memory tracking, and databank progression.

Working Advice

  • Start tiny: one actor, one objective, one marker, one completion path.
  • Once the loop works, expand into dialogue branches, map elements, codex entries, events, regions, and rewards.
  • Keep IDs, tags, data rows, and save state consistent. Narrative systems become powerful when many systems can safely refer to the same state.