NotificationRecipient

MMO\client\events · 1 symbol · generated 27 Oct 2026

class

NotificationRecipient

Who is asking for their notifications (Notifications): mmo.client knows no user, mmo.oauth answers with the logged in user's uid. Nobody answering: there is no notification centre for this request.

class MMO\client\events\NotificationRecipient extends MMO\core\events\Signal

Namespace: MMO\client\events
Extends: Signal

NotificationRecipient::AddListener(fn(NotificationRecipient $e) => $e->setReturn(\MMO\oauth\user()?->uid()));

Inherited members (17)

	Properties	Declared by	Description
	`Listeners`	Event
	`origin`	Event
	`returnValue`	Signal

Methods	Declared by	Description
`AddListener($handler, $order)`	Event	Register a listener directly (as opposed to `ConnectListeners`'s attribute-based discovery).
`ConnectListeners($obj)`	Event	Scan $obj's methods for #[Listen(EventClass::class)] attributes and register each one as a listener on the matching event class.
`DisconnectListeners($obj)`	Event	Undo a previous `ConnectListeners`: removes every listener that `connect` had registered for $obj on this event class.
`dispatch()`	Event	Invoke every `GetListeners` listener with $this.
`GetListeners()`	Event	Collect every listener for this class, including those registered on its parent classes (so a subclass event is also caught by listeners of its parent event), sorted by ascending $order (ties keep …
`getOrigin()`	Event
`getReturn()`	Signal
`HasListener($handler)`	Event
`hasReturn()`	Signal
`RemoveListener($handler)`	Event	Remove the last added handler from the listeners.
`Send($args)`	Event	Construct a new instance of this class with $args, then `dispatch` it to every listener.
`SetListenerOrder($handler, $order)`	Event	Change the order of an already-registered listener, whether added directly via `AddListener` or indirectly via `ConnectListeners` (which also stores its `[$obj, $methodName]` callables here).
`setReturn($value, $stop)`	Signal
`__construct($origin)`	Event