# Stop/Play/Open in Studio buttons on serialized event references

**URL:** <https://qa.fmod.com/t/stop-play-open-in-studio-buttons-on-serialized-event-references/20045>\
**Category:** Unity\
**Created:** [March 31, 2023, 10:21am UTC](https://qa.fmod.com/t/stop-play-open-in-studio-buttons-on-serialized-event-references/20045 "2023-03-31T10:21:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaitekinafune](https://avatars.discourse-cdn.com/v4/letter/k/a183cd/32.png) [@kaitekinafune](https://qa.fmod.com/u/kaitekinafune)\
**Post date:** [March 31, 2023, 10:21am UTC](https://qa.fmod.com/t/stop-play-open-in-studio-buttons-on-serialized-event-references/20045/1 "2023-03-31T10:21:14Z")

</div>

Hello,

A colleague of mine recently asked me to add those buttons to serialized FMOD events. I did, but our team is against modifying the source code of the plugin, so we decided to offer this feature on the forum.

![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/7/7278e98bdf67050f2a0c7779bde2a6939e3ed7d1.png)  
(I simply copied the existing code from the FMOD Event Browser with slight modifications)

---

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [April 4, 2023, 6:34am UTC](https://qa.fmod.com/t/stop-play-open-in-studio-buttons-on-serialized-event-references/20045/2 "2023-04-04T06:34:04Z")

</div>

Hi,

Just to clarify, by “offer this feature” do you mean that you’re requesting this feature?

---

<div class="post-metadata">

**Author:** ![kaitekinafune](https://avatars.discourse-cdn.com/v4/letter/k/a183cd/32.png) [@kaitekinafune](https://qa.fmod.com/u/kaitekinafune)\
**Post date:** [April 4, 2023, 7:05am UTC](https://qa.fmod.com/t/stop-play-open-in-studio-buttons-on-serialized-event-references/20045/3 "2023-04-04T07:05:19Z")

</div>

Hi,

Yes 🙂

(I tried to edit the post but couldn’t find the button to do so)

---

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [April 4, 2023, 11:08pm UTC](https://qa.fmod.com/t/stop-play-open-in-studio-buttons-on-serialized-event-references/20045/4 "2023-04-04T23:08:06Z")

</div>

Alright, I’ve added your feature request to our internal improvement tracker.

For posterity, the edit button is the pencil icon towards the bottom right corner of your post.  
 ![editbutton](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/3/3b4feed1e0981fb4e81dff1ac31069eb67ef7091.png)

---

<div class="post-metadata">

**Author:** ![kaitekinafune](https://avatars.discourse-cdn.com/v4/letter/k/a183cd/32.png) [@kaitekinafune](https://qa.fmod.com/u/kaitekinafune)\
**Post date:** [April 5, 2023, 5:56am UTC](https://qa.fmod.com/t/stop-play-open-in-studio-buttons-on-serialized-event-references/20045/5 "2023-04-05T05:56:38Z")

</div>

Thank you!

I forgot to mention that it would be great if you could add parameters to this event. For example, like it’s done in StudioEventEmitter. We mostly use FMOD with serialized fields (on ScriptableObjects) because we have many entities with similar events. But maybe I’m asking too much haha  
(Or, for example, a new class. Something like “ParametrizedEventReference” 🤔)

* * *

![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/1/14930e567429644abe8facf100ee7c8c674d4492.png)  
I guess I can’t edit it twice?

---

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [April 5, 2023, 6:32am UTC](https://qa.fmod.com/t/stop-play-open-in-studio-buttons-on-serialized-event-references/20045/6 "2023-04-05T06:32:31Z")

</div>

> [@kaitekinafune](#):
>
> I forgot to mention that it would be great if you could add parameters to this event. For example, like it’s done in StudioEventEmitter. We mostly use FMOD with serialized fields (on ScriptableObjects) because we have many entities with similar events. But maybe I’m asking too much haha  
> (Or, for example, a new class. Something like “ParametrizedEventReference” 🤔)

Given that the functionality does exist in StudioEventEmitter, I can see it being more convenient than either creating a custom UI script, or having to manage your own script that interacts with a Studio Event Emitter - I’ve also added it to our internal improvement tracker.

As for only being able to edit once, I’m not sure whether that’s intentional, but I’ll look into it.
