Event Messaging Systems
Event messaging systems are core parts of Open 3D Engine (O3DE) that allow cross-system communication. When you develop systems that need to communicate with other parts of O3DE, you need to use the event messaging systems that O3DE has in place.
Section topics
| Topic | Description |
|---|---|
| Overview | An overview of the event messaging systems in O3DE and how they compare to each other. |
| EBus | An overview of the Event Bus (EBus) system. EBus is a single global bus that all systems can use to invoke requests and dispatch messages, respectively known as request and notification buses. |
| EBuses in Depth | A closer look at the technical design of EBuses and how to use them. |
| AZ::Interface | A simpler alternative to EBus, AZ::Interface creates global request buses for invoking requests across systems. |
| AZ::Event | A simpler alternative to EBus, AZ::Event publishes single-value messages, which other components can subscribe to and process using the event’s handler. |
Overview
Use event buses (EBus), AZ::Interface, and AZ::Event to dispatch messages between systems in Open 3D Engine (O3DE).
EBus
Use event buses and the eventing system to dispatch messages between systems in Open 3D Engine.
EBus In Depth
Learn detailed information about EBuses in Open 3D Engine.
AZ::Interface
Use the AZ::Interface
AZ::Event
Use the AZ::Event template class to subscribe to and publish messages across game components.