Lifecycle (Construct 3)

You do not wire lifecycle actions in Construct 3

Construct 3 already has its own suspend/resume pipeline — when the runtime loses focus or an overlay opens, it pauses ticking and audio automatically. The FRVR plugin defers to that. There is no “on ad started” / “on ad ended” pause action you need to wire on the event sheet.

Compared with the Web SDK lifecycle, where a plain JS game registers five callbacks explicitly, Construct 3 needs nothing:

• When an interstitial / rewarded ad opens, Construct’s runtime is suspended by the browser / host channel.
• Audio is suspended alongside (Construct uses the Web Audio API, which is already gated by the same visibility signals).
• Both resume automatically when the ad closes and focus returns.

What you do still care about

• The FRVR SDK object must exist in your project. That’s what the plugin hangs its lifecycle handling off. See Construct 3 quickstart § 2.
• Offline support must be OFF in the export dialog. See quickstart § 3. Offline mode traps the HTML shell and blocks FRVR’s pipeline from injecting the right channel bundle — it also interferes with ad lifecycle delivery.

If you want to react to pause/resume on the event sheet

Use Construct’s built‑in system conditions — they’ll fire whenever anything (including FRVR ads) suspends the runtime:

System → On suspended
  → Action: stop any background music loop
System → On resumed
  → Action: resume background music loop

There’s no FRVR‑specific “on ad started” trigger to add — the system conditions are already the right abstraction.