# Events The Events system defines lifecycle flow and communication between OMS and features. OMS uses events to notify components about runtime stages and to process explicit action requests. *** ### Overview OMS events are divided into two categories: * **Lifecycle Events** - describe runtime stages of OMS and the server * **Action Events** - represent explicit requests for OMS to perform an operation *** ### Lifecycle Events Lifecycle events describe the current state of the OMS runtime. They are used to: * register addons * notify features about startup * drive ticking logic * notify features about shutdown See [Lifecycle Events](/oms-wiki/developer-guide/core-architecture/events/lifecycle-events.md) *** ### Action Events Action events represent operations requested by features or internal OMS components. They are used to trigger controlled behavior such as: * server stop See [Action Events](/oms-wiki/developer-guide/core-architecture/events/action-events.md) *** ### Notes * Lifecycle events describe state * Action events request behavior * Features react to events through the OMS runtime * OMS processes action events and executes the corresponding flow --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://conboi.gitbook.io/oms-wiki/developer-guide/core-architecture/events.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.