Heroes, Villains & Renegades
A persistent comic-book universe

The World of HVR

See how solo advancement, player rivalry, cooperation, identity, and recurring world events occupy the same persistent setting.

HVR is a shared comic-book setting built from two kinds of continuity. The game supplies locations, factions, missions, bosses, raids, events, and rules. Players supply the named characters, visual identities, Leagues, rivalries, victories, defeats, and community memory that keep those systems from feeling like an empty menu.

Heroes, Villains, and Renegades

The title describes the range of identities that inhabit the same world. Heroes can act from duty or compassion. Villains can pursue power, revenge, ideology, or spectacle. Renegades occupy the unstable space between them, answering to a personal code rather than a simple public label.

Alignment is most useful as a source of character decisions and relationships. It can explain why two players become rivals, why unlikely characters cooperate against a world threat, or why a member’s methods create tension inside a League. It does not require every Hero to use the same equipment or every Villain to approach combat in the same way.

How the world is experienced

Solo and story

Missions and Careers

Structured challenges and career paths give an individual character direction and mark new stages of progression.

Exploration

Patrol locations

Locations hold encounters, choices, bosses, rewards, Gyms, and discoveries that connect ordinary play with larger threats.

Rivalry

Battles and Arenas

Other player builds become opponents to read and solve, while divisions and special battlefields change the competitive context.

Cooperation

Raids and Leagues

Shared enemies and team infrastructure ask players to coordinate rather than treating every resource and result as private.

Live continuity

Events and seasonal towns

Limited rules, currencies, shops, locations, and world-scale encounters change what the community is doing together.

Player history

Profiles and community memory

Names, appearances, records, descriptions, League membership, and long-term relationships give a persistent character context.

Factions and Leagues are different layers

Factions connect a character to broader sides and conflicts in the setting. Leagues are player-organized super-teams with their own membership, communication, Headquarters, cooperative goals, and competitions. A faction supplies world context; a League supplies a day-to-day group of people.

That distinction creates room for interesting relationships. Players can share a broad allegiance without sharing a League, or work with unexpected allies when a raid or world event threatens everyone.

Where player stories come from

The most durable player stories do not need a scripted cutscene. A narrow raid victory, an Arena promotion, a League rebuilding after a loss, a Gym rivalry, a strange seasonal item, or a character’s evolving costume can all become part of the identity players remember.

HVR also contains an experimental automated Battle Stories feature that converts selected battle data into narrative text. Those generated scenes are a separate feature, not a substitute for the human-written rules, guides, profiles, conversations, and player decisions that explain the game.

Participating in a shared world

  • Give other players enough context when asking for raid or event help.
  • Treat character profiles and public communication as part of a community with real people behind it.
  • Separate playful rivalry from harassment or account-level conflict.
  • Credit useful strategy and correct outdated information when the game changes.
  • Use the developer contact route for bugs, account issues, data requests, and conduct that needs intervention.

Choose an entry point

New players can begin with Getting Started in HVR. Players who want to understand the collection can browse the live Power Catalog and Equipment Catalog. If you are evaluating the game itself, About HVR and Cat Castle Games explains who maintains it and how to reach the developer.