About Montinuity
A persistent multiverse RPG for shard campaigns, portable characters, and shared history.
Montinuity is built around the idea that a campaign shard should accumulate meaning. Characters grow, worlds remember, and an account becomes a continuity graph instead of a queue of disposable runs.
The product combines classic RPG structure, a persistent hex realm, authoritative gameplay systems, and a multiverse continuity model so returning to the same world or moving into a new shard still feels coherent.
What the game is optimizing for
- Shard campaigns instead of disposable sessions
- Character identity that survives many runs and restores
- A world model that remembers consequences across branches
- Algorithmic support that serves structure instead of replacing it
Why this world exists
Most digital dungeon runs are built to be replayed, but not remembered. Montinuity takes the opposite approach: the goal is to build shard worlds worth returning to because your earlier choices still matter.
That means campaigns persist, locations become familiar, and a character can complete an arc without the whole account losing continuity. Retirement, restoration, and forked variants are part of the design, not failure states.
- Campaigns should feel authored by play, not erased by the next queue.
- Character progression should create identity, not just higher numbers.
- World systems should support planning, travel, continuity, and consequence across sessions.
For long-form RPG players
This is aimed at players who miss campaigns that lasted months or years and want digital systems that respect long arcs and persistent consequences.
For roster builders
Characters are meant to define playstyles, relationships, and account history instead of being consumed and discarded after a single run.
For multiverse tinkerers
The setting matters as much as the character sheet: travel, location state, branching continuity, and eventual cross-setting migration are part of advancement.
The pillars behind the experience
These are the product-level promises that shape how content, systems, and progression are designed across every shard the platform can host.
Shard Campaigns
Campaigns are treated as real universe shards with their own local history, pressures, and consequences rather than disposable save slots.
Continuity Anchors
Save, restore, and replay are part of the fiction. A stored state is a continuity anchor that can be resumed, studied, or branched without pretending nothing happened.
Forked Characters
Characters are modeled as persistent agents who can evolve, diverge, retire, return, and carry identity across timelines or future setting shifts.
Cross-Setting Portability
A character can move from classic fantasy into cyberpunk, planar, or stranger shards as part of the world model instead of as an out-of-band import trick.
Living Service
The platform is meant to grow over time, with new shards, new rules families, and new interfaces added without breaking the continuity already earned.
The campaign loop
The game is designed to create momentum across sessions, restores, and future shard jumps, not just inside one isolated run.
Instantiate a roster
Create characters meant to persist, specialize, retire, restore, and eventually be replaced by successors or forked variants inside the same account history.
Push a shard forward
Campaigns explore new territory, uncover threats, earn equipment, and create a living record of what your group changed inside that universe branch.
Return, branch, or migrate
The next session can continue from the same world, restore from an earlier anchor, or carry the character into a different shard without losing the larger continuity story.
The technology and service model
The stack exists to support a living multiverse RPG service with clear systems, durable data, and room for algorithmic content expansion.
Game systems
- Persistent shard campaigns and character rosters
- Hex-realm travel layered above dungeon expeditions
- Authoritative encounter, chat, and continuity state
- Equipment, quests, and world history designed for long arcs
Platform stack
- Drupal CMS for structured content, routing, and operations
- Modern web UI with room to extend into mobile experiences
- H3-style geospatial thinking for region-scale world navigation
- Generated-image and algorithmic generation services integrated into gameplay systems
Operating model
- Algorithmic generation expands content breadth without replacing game structure
- Systems are tuned for reliability, readability, and reuse
- The product is designed as a living multiverse service, not a static one-off campaign
- Every layer is meant to support continuity, clarity, portability, and replay value
The team and product posture
Montinuity is being built as a living-world RPG service, which means the work is not just about generating more content. It is about making every shard legible, durable, and worth investing time into.
The team is focused on aligning generation systems, game rules, and world structure so the product feels like a coherent multiverse platform instead of a bag of disconnected features.
Product principles
- Persistence over disposability
- Readable systems over novelty for its own sake
- Player continuity over isolated single runs
- Operational reliability over flashy but brittle features
Ready to start a character that can actually travel with its history?
Create a roster, launch a shard, and start shaping a world you can return to, restore, or carry forward instead of resetting from scratch.