I want to help you get the most out of your purchase and make your project a success.

Included with your purchase:

• Video tutorials & walkthroughs: Find extensive, regularly updated tutorials on YouTube, with new topics added based on community requests.
• Documentation: Always available at gamesbyhyper.com/docs.
• Bug reports & fixes: All bug reports are welcome. Fixes are prioritized by impact and provided as long as they fit our support guidelines.
• Community forums: Connect with other developers; team members participate when available.
• Specialized walkthroughs: Released as needed for complex topics.

If you need extra help, see our options for additional support below.

Standard support does not include:

• Custom integration or project-specific setup
• Fixes for issues caused by code changes in your project
• Personal chat or video calls for general advice
• Proactive participation of staff in community forums

For needs beyond standard support, see our upgrade options.

If you need more in-depth help, we offer several optional upgrades:

• Enhanced Support: Available only through subscription credits. Includes a short scheduled call with a Hyper team member for tailored guidance within Hyper products.
  Details: Enhanced Support Session
  Redeem credits: Subscriptions
• Full courses: Covering every core feature and advanced workflows. See our courses.
• Studio support: Dedicated support by the hour (minimum 4 hours): custom support.
• Professional agreements: For studios needing strip cards, in-house sessions, or custom development. We support many large studios (including AAA) under NDA. Contact us for details.

Refunds follow Epic’s guidelines and are only possible for technical issues that prevent the product from functioning as advertised in its core features.

Refunds are not offered for:

• Difficulty understanding the product
• Needing modifications to fit your project
• Price changes (including sales or increases)

Note: Minor visual imperfections, normal engine or network limitations, or subjective opinions about usability or appearance do not qualify for refunds. Only reproducible issues that break the main, advertised functionality will be considered for a refund. Unreal Engine products may show minor artifacts or network effects; these are to be expected.

If you believe you have found a genuine technical issue that prevents the product’s core features from working as described, please contact us with specific details.

No software of this size and complexity can ever be completely bug-free. The framework is stable and thoroughly tested, but it is always possible that some bugs may arise.

If you experience any issues, please report them. Bug fixes are a top priority and are addressed as quickly as possible, with the most critical issues fixed first.

Your feedback is valuable and helps us continue to improve the product.

Yes! Engine updates and fixes are included for at least 3 years after initial release or until a major Unreal Engine version change (e.g. UE6).

• Only the latest engine versions are officially supported and receive new updates.
• Older versions may receive updates if feasible, but this is rare.
• Changelogs may be brief.
• Newly released modules or updates are not guaranteed to work with previous Unreal Engine versions.

1. General Advice:

• If you’re actively programming, avoid updating.
• Engine or marketplace updates can break your custom changes.

2. No Code Changed?

• If you haven’t modified Hyper code, updates are easy.

3. Important:

• Always backup & use version control.
• I can’t help with updates or provide detailed changelogs.

4. How to Update:

• If no code changed, remove all Hyper files, migrate, then re-integrate.

5. Extra Tips:

• Document any code changes you make.
• Backup your data tables.
• Keep folder structure—moved files get overwritten.

6. Product Philosophy:

• Sold “as is”.
• Updates = bug fixes, not new features (even though I sometimes do, at my discretion).
• You bought it for its current state.

7. File Structure & Updates:

• Structure usually stays consistent for migration.
• If versions & folders match, you can overwrite—but it erases changes.
• After migration: re-add your changes, reimport data tables.
• Core folder now holds base architecture (datastructures, classes, interfaces). Implementations are outside.
• Overwriting old with new is not always simple now.

8. Cherry Picking:

• If you’ve changed a lot, selectively copy code you want.
• Advanced users: mix new with old for best results.

9. Conclusion:

• Updates are not always needed.
• If you update, follow these tips for smooth integration.

I do provide optional courses. Currently, I have a course for the absolute basics of UE5 and one in the making for learning how to create a multiplayer survival framework.

UE5 Basics:

Are you new to Unreal Engine and eager to grasp its fundamental principles? This course covers everything from understanding variables to unraveling the complexities of networking.

Multiplayer Survival Framework Course:

This course will guide you through the process of crafting the foundation of a multiplayer survival game with Unreal Engine 5. We will start with the essentials, such as thinking out the architecture and setting up a map. From there, we will dive into the technical aspects, exploring the world of Unreal Engine’s visual scripting through Blueprints. You will gain proficiency in functions, macros, interfaces, variables, networking, and a wealth of other crucial concepts.

The Survival Framework course helps to comprehend an extensive framework that also highlights why certain architectural choices are made, with the goal to provide you with foundational knowledge.

Is it easy to integrate system X with system Y?

Integration depends on:

• Your experience level
• How modular each system is
• How much effort you’re willing to invest

Why Hyper systems add value: When you buy a Hyper module (like mineable rocks), you get a complete system, not just one feature. For example, mineable rocks include inventory, interaction, replication, animation, pickup/equip, and damage handling.

This means:

• All-in-one solution: Everything works together out of the box.
• Blueprint for integration: If you want to use your own inventory, simply search for “get inventory” in the Blueprints to find logical connection points.

• See adapting modules (mineable rocks example)
• See migrating our own systems (level manager example)

• Flexible customization: Use the full template or just the parts you need.

Note: Custom integration—especially between different systems—is one of the most challenging parts of game development. If you’re new to Unreal Engine or Blueprints, you’ll usually have the best experience staying within the Hyper ecosystem, which is one of the most complete and robust available.

Support and resources:

• Detailed documentation, migration guides, and video tutorials are available to help you.
• While we can’t offer step-by-step support for every third-party asset, our resources and community support can help guide your process.

Nearly everything in my products is created by me and the team I’ve built over time. Together, we’ve dedicated well over 50,000 hours to development—covering gameplay systems, Blueprints, and documentation—with a deep passion for quality and completeness.

We also leverage some of the best content provided by Epic Games where it makes sense. For example, our advanced locomotion framework uses adapted Lyra animations as a foundation, ensuring industry-standard quality for your projects.

To keep the focus on gameplay depth and value, we sometimes use outstanding community assets under the CC0 license. Please support these great creators if you can:

• Poly Haven
• ambientCG
• OpenGameArt
• Blend Swap (be sure to filter for CC0 assets)

Our priority is always delivering robust, original systems. When we use open community resources, it’s to bring you the best quality possible and to support the vibrant Unreal and open-source communities.

I understand the price may seem high at first glance, but the value you receive is substantial. Here’s why:

• Over 50,000 hours of professional work have gone into these systems and templates, including design, programming, testing, and documentation.
• Industry value: Even at a modest rate of $50 per hour (many developers charge much more), that would total several million dollars in development value.
• Massive time savings: By purchasing a template or module, you save thousands of hours and get advanced, production-ready systems at just a tiny fraction of real development cost.
• Best value: Buying the full template is much more affordable than purchasing individual modules separately.
• Flexible payment: If you need more flexibility, pay-over-time options are available through my website.

If you have questions about features, value, or pricing, please feel free to reach out. My goal is to help you succeed with the best tools available.

In regard to expectation management of developers that want to build an MMO:

It is hard, and requires a lot of custom implementations. I made it as easy as possible but I do not support large-scale MMO by default since it most likely requires custom engine implementations and more.

Multiple people in our community are doing a successful approach and are working on custom implementations like segmental replication and more.

The most easy answer is: If you need to ask this question, the answer will probably be not for you.

If there are any other creators who say it is all possible and easy… They are most likely not telling the whole story!