-
Notifications
You must be signed in to change notification settings - Fork 0
Event Handler
PlatanoGames edited this page Aug 8, 2026
·
3 revisions
The event-handler subsystem resolves a Gameplay Tag to a handler class derived from the Core handler base.
- Ephemeral: create for one execution.
- Cached: reuse an instance while it remains cached.
- Singleton: maintain one shared instance for the configured scope.
Handlers can be registered and inspected through Core contracts. They are a behavior-dispatch mechanism, distinct from broadcasting a typed message to multiple listeners.
Use handlers when a tag selects an implementation. Use messages when a publisher announces data to optional receivers.
- Development Preview
- Getting Started
- Release branch catalog
- Public Plugin Matrix
- Early Preview Plugins
- Known Issues
- Architecture Overview
- Plugin Topology
- Module Reference
- Configuration and Registry
- Data-Driven Design
- Profiles and Budgets
- Gameplay Tag Architecture
- Initialization Pipeline
- Cross-Plugin Communication
- Message System
- Event Handlers
- Logging and Trace
- Runtime Flows
- Blueprint API Design
- Editor Integration
- Editor Visual System