Interacting with Cloud Events

Creating an Event Listener
For us to be notified when our event service receives an event from the cloud we must provide it with an event listener for it to relay to. The SDKs provide an interface that we will use to implement a listener the service will use. An example of how we may implement the IEventListener interface can be seen below:
Java
C# | Unity
C++
Unreal
import com.enjin.sdk.events.IEventListener;
import com.enjin.sdk.models.NotificationEvent;
​
class Listener implements IEventListener {
    @Override
    public void notificationReceived(NotificationEvent event) {
        // Place code here
    }
}
using Enjin.SDK.Events;
using Enjin.SDK.Models;
​
class Listener : IEventListener {
    public void NotificationReceived(NotificationEvent notificationEvent) {
        // Place code here
    }
}
#include "enjinsdk/IEventListener.hpp"
#include "enjinsdk/models/NotificationEvent.hpp"
​
using namespace enjin::sdk::events;
using namespace enjin::sdk::models;
​
class Listener : public IEventListener {
public:
    void notification_received(const NotificationEvent& event) override {
        // Place code here
    }
};
#include "IEventListener.h"
#include "Model/NotificationEvent.h"
​
using namespace Enjin::Sdk::Event;
using namespace Enjin::Sdk::Model;
​
class FEventListener : public IEventListener
{
public:
    void NotificationReceived(const FNotificationEvent& Event) override
    {
        // Place code here
    }
};
The NotificationEvent argument in the notification received method models an event that the event service has received and parsed. This argument will contain information telling us the type of the event that was received, the channel the event was broadcasted on, and the JSON message that is the data associated with the event, such as the asset ID for asset events or the wallet address for wallet events.
Listener Registration
Registering a Listener
Once we have defined an event listener we may register it with our event service. The event service has multiple registration methods with different functionality, but for now, we will use the most basic of these methods. The basic registration method will register our listener and for any event the service receives and processes from the cloud, our listener will receive the parsed event data. When registering our listener we will also receive the listener registration object containing data about our registration.
Java
C# | Unity
C++
Unreal
import com.enjin.sdk.events.EventListenerRegistration;
​
Listener listener = new Listener();
​
EventListenerRegistration reg = service.registerListener(listener);
using Enjin.SDK.Events;
​
Listener listener = new Listener();
​
EventListenerRegistration reg = service.RegisterListener(listener);
#include "enjinsdk/EventListenerRegistration.hpp"
#include <memory>
​
using namespace enjin::sdk::events;
​
std::shared_ptr<Listener> listener = std::make_shared<Listener>();
​
EventListenerRegistration reg = service->register_listener(listener);
#include "EventListenerRegistration.h"
​
using namespace Enjin::Sdk::Event;
​
FEventListenerRef Listener =
    MakeShared<FEventListener, ESPMode::ThreadSafe>();
​
FEventListenerRegistrationRef Reg =
    EventService->RegisterListener(Listener);
Unregistering a Listener
If we wish to do so we may also unregister our listener from the service. To do so we pass our listener as an argument to the service's unregister method. In the event that we did not create a variable for our listener before registering it, we may use the reference that is stored in the registration that we received upon registration as shown below:
Java
C# | Unity
C++
Unreal
// Using a listener registration
service.unregisterListener(reg.getListener());
// Using a listener registration
service.UnregisterListener(reg.Listener);
// Using a listener registration
service->unregister_listener(reg.get_listener());
// Using a listener registration
Service->UnregisterListener(Reg->GetListener().Get());
Event Channel Subscription
Subscribing to a Channel
To subscribe to one of the four-event channels used by the cloud we must provide the identifier for it. See the code block below for what these identifiers are:
Java
C# | Unity
C++
Unreal
service.subscribeToProject("<the-project's-uuid>");
​
service.subscribeToPlayer("<the-project's-uuid>", "<the-player's-id>");
​
service.subscribeToAsset("<the-asset's-id>");
​
service.subscribeToWallet("<the-wallet's-address>");
service.SubscribeToProject("<the-project's-uuid>");
​
service.SubscribeToPlayer("<the-project's-uuid>", "<the-player's-id>");
​
service.SubscribeToAsset("<the-asset's-id>");
​
service.SubscribeToWallet("<the-wallet's-address>");
service->subscribe_to_project("<the-project's-uuid>");
​
service->subscribe_to_player("<the-project's-uuid>", "<the-player's-id>");
​
service->subscribe_to_asset("<the-asset's-id>");
​
service->subscribe_to_wallet("<the-wallet's-address>");
Service->SubscribeToProject(TEXT("<the-project's-uuid>"));
​
Service->SubscribeToPlayer(TEXT("<the-project's-uuid>"), TEXT("<the-player's-id>"));
​
Service->SubscribeToAsset(TEXT("<the-asset's-id>"));
​
Service->SubscribeToWallet(TEXT("<the-wallet's-address>"));
After subscribing to a channel our event service will now receive events that are broadcasted on the specified event channel.
When using the PusherEventService, subscribed channels may only be subscribed to after starting the service for the first time.
We may also check to see if our service is already subscribed to a particular event channel by using the appropriate method and passing the identifiers as shown below:
Java
C# | Unity
C++
Unreal
service.isSubscribedToProject("<the-project's-uuid>");
​
service.isSubscribedToPlayer("<the-project's-uuid>", "<the-player's-id>");
​
service.isSubscribedToAsset("<the-asset's-id>");
​
service.isSubscribedToWallet("<the-wallet's-address>");
service.IsSubscribedToProject("<the-project's-uuid>");
​
service.IsSubscribedToPlayer("<the-project's-uuid>", "<the-player's-id>");
​
service.IsSubscribedToAsset("<the-asset's-id>");
​
service.IsSubscribedToWallet("<the-wallet's-address>");
service->is_subscribed_to_project("<the-project's-uuid>");
​
service->is_subscribed_to_player("<the-project's-uuid>", "<the-player's-id>");
​
service->is_subscribed_to_asset("<the-asset's-id>");
​
service->is_subscribed_to_wallet("<the-wallet's-address>");
Service->IsSubscribedToProject(TEXT("<the-project's-uuid>"));
​
Service->IsSubscribedToPlayer(TEXT("<the-project's-uuid>"), TEXT("<the-player's-id>"));
​
Service->IsSubscribedToAsset(TEXT("<the-asset's-id>"));
​
Service->IsSubscribedToWallet(TEXT("<the-wallet's-address>"));
Channel subscriptions on the PusherEventService persist after shutting down and restarting the service.
Unsubscribing from a Channel
To unsubscribe our service from a channel we will need to recall the information we provided when we first subscribed and provide it to the service's unsubscribe method as well. After doing so our service will no longer receive events from the cloud for the specified channel.
Java
C# | Unity
C++
Unreal
service.unsubscribeToProject("<the-project's-uuid>");
​
service.unsubscribeToPlayer("<the-project's-uuid>", "<the-player's-id>");
​
service.unsubscribeToAsset("<the-asset's-id>");
​
service.unsubscribeToWallet("<the-wallet's-address>");
service.UnsubscribeToProject("<the-project's-uuid>");
​
service.UnsubscribeToPlayer("<the-project's-uuid>", "<the-player's-id>");
​
service.UnsubscribeToAsset("<the-asset's-id>");
​
service.UnsubscribeToWallet("<the-wallet's-address>");
service->unsubscribe_to_project("<the-project's-uuid>");
​
service->unsubscribe_to_player("<the-project's-uuid>", "<the-player's-id>");
​
service->unsubscribe_to_asset("<the-asset's-id>");
​
service->unsubscribe_to_wallet("<the-wallet's-address>");
Service->UnsubscribeToProject(TEXT("<the-project's-uuid>"));
​
Service->UnsubscribeToPlayer(TEXT("<the-project's-uuid>"), TEXT("<the-player's-id>"));
​
Service->UnsubscribeToAsset(TEXT("<the-asset's-id>"));
​
Service->UnsubscribeToWallet(TEXT("<the-wallet's-address>"));
Matching Listeners for Events
In the case where we would like to register a more specialized event listener that only receives particular event types, we may use various means to specify which events we want to receive to offload the responsibility of filtering events from our listener to the event service instead.
Functional Matcher
For registering our listener in the service to process events under tailored conditions we specify, we may use the service's method for registering with a paired matcher for our listener. If the matcher returns true, then the service will pass the NotificationEvent to our listener for processing, whereas if the matcher returns false, then our listener will not receive the event. As with standard registration, this method returns a listener registration object.
Java
C# | Unity
C++
Unreal
service.registerListenerWithMatcher(listener, notificationEvent -> {
    // Place code here
​
    return true;
}); // Returns listener registration
service.RegisterListenerWithMatcher(listener, eventType => {
    // Place code here
​
    return true;
}); // Returns listener registration
#include "enjinsdk/models/EventType.hpp"
​
using namespace enjin::sdk::models;
​
service->register_listener_with_matcher(listener, [](EventType type) {
    // Place code here
​
    return true;
}); // Returns listener registration
#include "Model/EventType.h"
​
using namespace Enjin::Sdk::Model;
​
Service->RegisterListenerWithMatcher(Listener, [](const EEventType Type)
{
    // Place code here
​
    return true;
}); // Returns listener registration
Including Events
For registering our listener in the service to process only a select set of events, we may use the service's method for registering with including event types. As with standard registration, this method returns a listener registration object.
Java
C# | Unity
C++
Unreal
import com.enjin.sdk.models.EventType;
​
service.registerListenerIncludingTypes(listener,
    EventType.ASSET_MELTED,
    EventType.ASSET_MINTED,
    EventType.ASSET_TRANSFERRED
); // Returns listener registration
using Enjin.SDK.Events;
​
service.RegisterListenerIncludingTypes(listener,
    EventType.ASSET_MELTED,
    EventType.ASSET_MINTED,
    EventType.ASSET_TRANSFERRED
); // Returns listener registration
#include "enjinsdk/models/EventType.hpp"
​
using namespace enjin::sdk::models;
​
service->register_listener_including_types(listener, {
    EventType::AssetMelted,
    EventType::AssetMinted,
    EventType::AssetTransferred
}); // Returns listener registration
#include "Model/EventType.h"
​
using namespace Enjin::Sdk::Model;
​
Service->RegisterListenerIncludingTypes(Listener,
{
    EEventType::AssetMelted,
    EEventType::AssetMinted,
    EEventType::AssetTransferred
}); // Returns listener registration
Excluding Events
For registering our listener in the service to not process a select set of events, we may use the service's method for registering with excluding event types. As with standard registration, this method returns a listener registration object.
Java
C# | Unity
C++
Unreal
import com.enjin.sdk.models.EventType;
​
service.registerListenerExcludingTypes(listener,
    EventType.ASSET_MELTED,
    EventType.ASSET_MINTED,
    EventType.ASSET_TRANSFERRED
); // Returns listener registration
using Enjin.SDK.Events;
​
service.RegisterListenerExcludingTypes(listener,
    EventType.ASSET_MELTED,
    EventType.ASSET_MINTED,
    EventType.ASSET_TRANSFERRED
); // Returns listener registration
#include "enjinsdk/models/EventType.hpp"
​
using namespace enjin::sdk::models;
​
service->register_listener_excluding_types(listener, {
    EventType::AssetMelted,
    EventType::AssetMinted,
    EventType::AssetTransferred
}); // Returns listener registration
#include "Model/EventType.h"
​
using namespace Enjin::Sdk::Model;
​
Service->RegisterListenerExcludingTypes(Listener,
{
    EEventType::AssetMelted,
    EEventType::AssetMinted,
    EEventType::AssetTransferred
}); // Returns listener registration
Filtered Listener
We may also attach attributes/annotations on listener classes to indicate to the event service which events we want our listener to receive or not receive. Generally, we can set which events we want them to filter for and also indicate if we want the filter to allow or disallow said events. Examples of what this may look like in the SDKs which support this feature can be seen below:
Java
C# | Unity
import com.enjin.sdk.events.EventFilter;
import com.enjin.sdk.events.IEventListener;
import com.enjin.sdk.models.EventType;
​
@EventFilter(allow = true, value = {EventType.ASSET_MELTED /* more events */})
class Listener implements IEventListener { /* ... */ }
using Enjin.SDK.Events;
using Enjin.SDK.Models;
​
[EventFilter(allowed: true, EventType.ASSET_MELTED /* more events */)]
class Listener : IEventListener { /* ... */ }
Setting up an Event Service
Message Logging
Last modified 6mo ago