Skip to content

docs(legacy-events): add yt video about migrating from events to triggers #516

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lancesnider merged 3 commits into from
Mar 5, 2026
Merged

docs(legacy-events): add yt video about migrating from events to triggers #516

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
35041fe
Add Events to Triggers TY video
jeffatrive Feb 25, 2026
6d0dce2
Update overview.mdx
jeffatrive Feb 25, 2026
6df9641
Update rive-events.mdx
jeffatrive Feb 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions editor/events/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,19 @@
---
title: 'Events Overview'
sidebarTitle: 'Overview'
description: ''
description: "⚠️ DEPRECATED: Use Data Binding instead of Events"
---
import { YouTube } from "/snippets/youtube.mdx";

<Info>
If you're using [Data Binding](/editor/data-binding), you can listen for triggers or value changes from your code without needing Events.
</Info>
<Warning>
**DEPRECATION NOTICE:** This entire page documents the legacy Events system.
**For new projects:** Use [Data Binding](/runtimes/data-binding) instead.
**For existing projects:** Plan to migrate from Events to Data Binding as soon
as possible. **This content is provided for legacy support only.**
</Warning>


<YouTube id="M5DIDVtYI_Y" />

Events are a way to send signals to your runtime code to execute a block of code at the right moment. They enhance the communication between designers and developers by passing along useful information. With them, we can do things like go to a URL, play a sound, have some HTML appear, or do anything else we may want to accomplish via code.

Expand Down
2 changes: 2 additions & 0 deletions game-runtimes/unity/rive-events.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,11 @@ noindex: true

import LegacyDataBindingNotice from '/snippets/unity/legacy-databinding-notice.mdx';
import LegacyApiNotice from '/snippets/unity/legacy-api-notice.mdx';
import { YouTube } from "/snippets/youtube.mdx";

<LegacyDataBindingNotice subject="Events" />

<YouTube id="M5DIDVtYI_Y" />
For more information on Rive Events see the respective runtime and editor documentation.

<CardGroup col="2">
Expand Down
2 changes: 2 additions & 0 deletions runtimes/rive-events.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ import { YouTube } from "/snippets/youtube.mdx";
as possible. **This content is provided for legacy support only.**
</Warning>

<YouTube id="M5DIDVtYI_Y" />

With Rive events, you have the ability to subscribe to meaningful signals that get reported from animations, state machines, and Rive listeners, all created at design time from the Rive editor. These signals can be subscribed to at runtime and have a specific name, type, and various custom metadata that may accompany the event to help inform the context surrounding its meaning.

For more on the Events feature in general, check out the [Events](/editor/events/overview) page in the editor section of the docs. The Event system has also been expanded to support [Audio Events ](/editor/events/audio-events)to trigger audio to play in the editor and at runtime.
Expand Down