Hyper game templates are pre-configured Unreal Engine project foundations built from multiple Hyper systems. They are intended for developers who want a working genre setup first, then want to customize the content, UI, data, and gameplay on top of it.

For shared setup guidance, see the Migration Guide and Integration Guide. Use the System Atlas to look up functions, variables, events, components, and ownership references. Use this page for template-specific decisions, bundle options, and integration expectations.

Most Hyper modules are genre-agnostic. Templates combine those systems into a practical starting point for RPG, survival, shooter, open-world, co-op, multiplayer, top-down, first-person, third-person, side-scroller, RTS, platformer, and other project styles depending on how you configure and extend the systems.

Template Tiers and Upgrades

Some templates are available in several tiers. Each tier includes a different set of systems and example content. You can upgrade your template anytime, so you can start with a smaller tier and move up later if the template fits your project.

• Play

• Play

• Play

• Play

What Templates Are

A template is a ready-to-use collection of multiple Hyper systems configured and integrated for a specific game genre. It is a technical foundation, not a finished game.

Templates usually include:

• Multiple systems working together out of the box.
• Genre-specific configuration for RPG, survival, shooter, or similar projects.
• Pre-configured data tables with example content.
• Example maps that demonstrate technical implementation and integration.
• Genre-specific UI widgets and HUD elements.
• Core folder content, including shared abstract classes, structures, enums, and interfaces.
• Resource Pack assets such as icons, UI elements, placeholder meshes, particle effects, and sounds.

Templates do not provide:

• Complete game content.
• Final art assets.
• Full game design.
• Polished gameplay.
• Story, narrative, or finished levels.

Template vs. Individual Systems

Buying an individual system gives you the system itself, its core dependencies, basic UI, and general setup. You still decide how it connects to the rest of your project.

Buy Inventory System separately:
├── Inventory System blueprints
├── Interaction System blueprints
├── Core folder (abstract classes, structures)
├── UI widgets
└── Resource Pack assets

• Inventory functionality.
• Basic integration support.
• Generic setup.
• You configure it for your genre.
• Lower initial cost.

Buying a template gives you several systems that are already configured for the genre and connected to each other.

Buy Survival Template:
├── Inventory System
├── Equipment System
├── Crafting System
├── Building System
├── Attribute System (Health, Hunger, Thirst, Temperature)
├── Interaction System
├── ... (10+ systems total)
├── Pre-configured data tables (survival items, recipes, resources)
├── Example maps (survival mechanics demonstration)
├── Genre-specific UI
└── All systems integrated for survival gameplay

• 10+ systems working together.
• Survival-specific configuration.
• Hunger, thirst, and temperature systems.
• Survival items, recipes, and building pieces.
• Lower total cost than buying comparable systems individually.
• A ready foundation for a survival game.

Available Template Types

RPG Template

The RPG template is configured around character progression, quests, inventory, equipment, dialogue, choices, and RPG-style UI.

• Character stats such as Strength, Intelligence, and Dexterity.
• Level progression and class-based equipment restrictions.
• Quest journal and quest tracking.
• Dialogue and NPC interaction flows.
• Inventory with weight limits.
• Skill tree style progression where included.

Use this direction for games in the style of Skyrim, Hogwarts Legacy, or other RPG-style projects.

Survival Template

The survival template is configured around resource pressure, crafting, building, and survival attributes.

• Hunger, thirst, temperature, stamina, and related state effects.
• Resource gathering and survival item data.
• Crafting recipes and building pieces.
• Environmental pressure and shelter-related systems.
• Solo or co-op survival workflows.

Use this direction for games in the style of The Forest, Rust, ARK, or other solo/co-op survival projects.

Shooter Template

The shooter template is configured around combat, weapons, loadouts, attachments, ammo management, tactical equipment, teams, and multiplayer support.

• Rifles, pistols, attachments, and weapon-related data.
• Loadout customization and ammo management.
• Weapon mods and tactical equipment.
• Team systems and multiplayer setup where included.

Use this direction for tactical or arcade shooter projects in the style of Escape from Tarkov, Call of Duty, or Battlefield.

Why Use a Template?

Genre-Specific Setup

A template saves the initial work of deciding how the systems should connect for a common genre. Data tables, example maps, and UI are already aligned around that genre, so you can inspect a working baseline before replacing content with your own.

Pre-Configured Integration

With individual systems, you set up each component, configure its data, connect it to related systems, test the data flow, and fix integration issues. With a template, those connections already exist in the supplied example project.

Example survival flow:

1. The player gathers wood from a resource.
2. The gathering system adds the wood to inventory.
3. The inventory updates weight and UI.
4. The crafting system checks the inventory for ingredients.
5. Crafting consumes the ingredients and creates the item.
6. The equipment system lets the player equip the crafted item.
7. The attribute system can affect the flow through stamina, hunger, temperature, or related state effects.

Cost Efficiency

Templates are intended to cost less than buying the same systems individually, while also saving setup and integration time. The exact value depends on your project: if you need most of the included systems, a template is usually the better starting point. If you only need a few systems, individual systems or the Bundle Configurator may fit better.

Example Maps, Data, and UI

Templates include more example content than individual systems. The goal is to show how the systems work together, not to provide final production content.

• Data tables: example items, equipment, recipes, quests, attributes, and other system data depending on the template.
• Example maps: technical maps that demonstrate integration and give you a reference for implementation.
• UI widgets: genre-specific inventory, equipment, crafting, HUD, and menu widgets where relevant.
• Core folder: shared abstract classes, structures, enums, and interfaces used across systems.
• Resource Pack: supporting icons, UI elements, placeholder meshes, effects, and sounds.

Use the examples as a reference, then replace the content, art, data, and design with your own project-specific implementation.

Bundle Configurator

The Bundle Configurator is used when a predefined template is close but not exact, or when your project needs a custom set of systems.

Example custom bundle:

• Inventory System
• Equipment System
• Crafting System
• Quest System
• Building System
• Attribute System
• Weather System
• Vehicle System

Pricing is based on the selected systems and any bundle discount or optional Integration Service. For example, a custom bundle might include several individually priced systems, a bundle discount, and an added Integration Service cost. Compare that result against the closest template tier before choosing.

Integration Service

The Integration Service is an optional add-on where Games by Hyper integrates the selected systems into one cohesive project.

Without Integration Service, you receive the selected systems and integrate them yourself. This includes connecting data flow between systems, configuring UI, testing integration points, and resolving conflicts.

With Integration Service, you receive a single integrated project with systems connected, data tables configured, UI hooked up, and example content tested together.

The service is most useful when your selected systems need to communicate heavily, such as Inventory ↔ Equipment, Inventory ↔ Crafting, Inventory ↔ Quest, or Equipment ↔ Attribute.

Choosing the Right Option

Also consider budget, required features, team size, project scope, timeline, and whether you want to do integration work yourself.

What You Receive

A template or bundle is delivered as Hyper project content with the relevant core files, systems, UI, resources, and example content.

Template Purchase:
Hyper/
├── Core/ (all system core files)
├── Templates/[TemplateName]/ (template-specific files)
├── [System1]/ (first system)
├── [System2]/ (second system)
├── ... (all systems in template)
├── UI/ (all UI widgets)
└── ResourcePack/ (all assets)

Bundle Configurator Purchase (Without Integration):
Hyper/
├── Core/ (core files for selected systems)
├── [System1]/ (your selected systems)
├── [System2]/
├── ... (all selected systems)
├── UI/ (UI for selected systems)
└── ResourcePack/ (assets for selected systems)

Bundle Configurator + Integration Service:
Hyper/
├── Core/ (all system core files)
├── Templates/CustomBundle/ (integrated project files)
├── [System1]/ (fully integrated)
├── [System2]/ (fully integrated)
├── ... (all selected systems, integrated)
├── UI/ (all UI widgets, connected)
└── ResourcePack/ (all assets)
+ Pre-filled data tables
+ Example map showing integration
+ All systems connected and tested

Documentation and support may include:

• Individual system documentation.
• Template-specific setup guidance.
• Integration examples.
• Data table references.
• Access to support channels, updates, bug fixes, and new features depending on the support plan.

Recommended First Steps

1. Open the example map. Test the included systems and inspect how they work together.
2. Review the data tables. Look at entries such as DT_Items, DT_Crafting, and other template-specific tables.
3. Read the relevant system documentation. Use the individual docs to understand each component, data structure, and extension point.
4. Customize the content. Replace sample items, recipes, quests, art, UI styling, and other example content with your project-specific data.
5. Build on top of the foundation. Add your levels, story, mechanics, progression, and production content.

If you purchased Integration Service, skip manual integration and start from the supplied integrated project.

Summary

Hyper templates, custom bundles, and Integration Service are different ways to start from working Unreal Engine systems instead of wiring everything from scratch.

• Templates are best when a predefined genre package fits your project.
• Bundle Configurator is best when you need a custom system mix.
• Bundle Configurator + Integration Service is best when you want custom systems delivered as a working integrated project.

Choose the option that matches your game genre, budget, timeline, and willingness to handle integration work yourself.