What's New

• New EventSubscriber Block  Introduced a reusable block that simplifies event subscription. Just drop it into your UI and configure the EventId and OnEvent—no need to manually call SubscribeToEvent.

• Automatic Unsubscription  The EventSubscriber block now handles cleanup automatically via OnDestroy, preventing memory leaks and reducing boilerplate code.

• Improved Documentation & Developer Experience  Updated descriptions, usage examples, and Forge listing to reflect the new block-based architecture. Easier onboarding for new developers.

Enhancements

• Refactored internal logic for better performance and maintainability.

• Improved naming conventions and input validation for EventId and Payload.

• Added comments and structure to client actions for easier customization.

Breaking Changes

• If you previously used only the SubscribeToEvent client action, consider migrating to the new EventSubscriber block for better lifecycle management.

• Deprecated manual unsubscription patterns—these are now handled automatically.

Security Reminder

Events are transmitted entirely on the client side. Do not send sensitive data through the Payload. Always validate permissions and roles server-side before executing any critical logic.