Description
Discord 💬 | Documentation 📑 | Videos 📷
Hyper Event Manager v4
The Hyper Event Manager v4 is the nervous system of your game logic. It allows for the decoupling of systems by using Gameplay Tags to trigger global or local events. Triggers like ‘PlaySequence’, ‘SpawnLevelInstance’, or ‘AddItem’ can be broadcast to any listener without hard references. It simplifies complex interactions, such as quest progression or world state changes, enabling you to build ‘in-flight’ game logic dynamically.
Key Features
- Decoupled architecture using Gameplay Tags
- Global and Local Event Listeners
- Payload support (Variables, Structs, Objects)
- Integrates Quests, Dialogue, and Spawning Logic
- Debug tools for tracking event flow
- Extremely lightweight and performance-friendly
Why Hyper?
- The strongest public modular Unreal Engine framework available at this scale
Most studios keep tools like this internal. Hyper makes a serious technical foundation available to solo developers, indies, and teams. - Built from 75,000+ hours of Unreal Engine work
System design, Blueprint architecture, multiplayer patterns, documentation, testing, examples, iteration, and real production problem-solving. - Systems designed to work together
Inventory, crafting, equipment, interaction, UI, combat, attributes, multiplayer, AI, quests, dialogue, maps, progression, survival systems, environment tools, performance helpers, and more can all live inside one larger ecosystem. - Not a content dump
Hyper gives you working examples, modular structure, documentation, and patterns you can extend into your own game. - Made for serious projects, not just demos
Hyper is built around scalable architecture: gameplay tags, structured data, child Blueprints, clean overrides, reusable components, and clear project boundaries. - Start fast, grow cleanly
Use the included examples, replace visuals, adjust data, create child Blueprints, connect systems, and build toward your own game without rebuilding the same foundation from scratch.
Want to learn more about the Hyper ecosystem, architecture philosophy, workflows, and developer behind it? Read more here and get started.
3 reviews for Event Manager
You must be logged in to post a review.
- Future-proof design with ongoing updates
- Clear, well-documented Blueprints with clear naming
- Scalable system for hobby to AAA-scale productions
- Cross-genre ready (Open-World, Survival, RPG, FPS, etc.)
- Fully network-replicated for multiplayer support
- Cross-platform ready (Windows tested)
- Modular, component-based (drag-and-drop integration)
- Data-driven setups using DataTables where applicable
- Blueprint-first where sensible
- Trusted by developers across indie to large productions
Support, Community, and Documentation
- Public Documentation, YouTube, and Discord are available.
- Verified buyers can use the support forums for bug reports, data models, and peer help.
- Blueprint comments explain both how the system works and why key choices were made.
Plugins
- Common UI
WHYPHY710 –
Review from FabIt’s simple straight forward logic that can manage your quests and so much more!
Dalcon4 –
Review from FabThe Hyper Event Manager v4 is a centralized event dispatching and scheduling framework that coordinates gameplay events across all systems and actors. It provides a unified event bus that decouples game systems, enabling complex event chains, timed triggers, conditional responses, and cross-system communication without direct dependencies between modules. The Event Manager is architecturally robust. It supports immediate and deferred event dispatch, timed and recurring event schedules, conditional event filtering, event priority ordering, event chaining for sequential workflows, listener registration and unregistration, and comprehensive event logging for debugging. The system handles high-throughput event scenarios without performance degradation. Using the Event Manager is intuitive. Register listeners for specific event types, dispatch events from any system, and the manager routes them to all registered handlers. Events are defined through a flexible typing system that supports custom data payloads. Adding new event types requires no modification to the core system. The Blueprint interface is clean and well-documented. Event dispatching is near-instant with negligible overhead. The routing system efficiently matches events to listeners without unnecessary iteration. Timed events fire with frame-accurate precision, and the priority system ensures critical events are processed before lower-priority ones. The debugging tools make it easy to trace event flows through complex system interactions.