# Feature request: event instances as blueprint data type (variable)

**URL:** <https://qa.fmod.com/t/feature-request-event-instances-as-blueprint-data-type-variable/12244>\
**Category:** Unreal Engine\
**Created:** [January 14, 2016, 4:09pm UTC](https://qa.fmod.com/t/feature-request-event-instances-as-blueprint-data-type-variable/12244 "2016-01-14T16:09:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zelotos](https://avatars.discourse-cdn.com/v4/letter/z/5f9b8f/32.png) [@Zelotos](https://qa.fmod.com/u/Zelotos)\
**Post date:** [January 14, 2016, 4:09pm UTC](https://qa.fmod.com/t/feature-request-event-instances-as-blueprint-data-type-variable/12244/1 "2016-01-14T16:09:48Z")

</div>

My team is using a game instance in UE4, which needs to stop all currently playing FMOD events at a given time, for example when the player dies or when a new level is opened. As such, we’re looking for a way to efficiently collect all currently playing FMOD event instances and command them all to stop playing. Is there a way to save FMOD event instances as variables (blueprint data type)? Or do you know of another way to collect all currently active event instances?

([https://wiki.unrealengine.com/Game\_Instance,\_Custom\_Game\_Instance\_For\_Inter-Level\_Persistent\_Data\_Storage](https://wiki.unrealengine.com/Game_Instance,_Custom_Game_Instance_For_Inter-Level_Persistent_Data_Storage "info"))

---

<div class="post-metadata">

**Author:** ![geoff](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@geoff](https://qa.fmod.com/u/geoff)\
**Post date:** [January 20, 2016, 11:20pm UTC](https://qa.fmod.com/t/feature-request-event-instances-as-blueprint-data-type-variable/12244/2 "2016-01-20T23:20:37Z")

</div>

This is a great idea and I can see why it would be very useful. I’m not sure exactly how feasible that is at the moment. I’ll add it to our list, but I don’t have an ETA on when we’ll get around to having a look at it.

---

<div class="post-metadata">

**Author:** ![geoff](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@geoff](https://qa.fmod.com/u/geoff)\
**Post date:** [May 10, 2016, 1:48am UTC](https://qa.fmod.com/t/feature-request-event-instances-as-blueprint-data-type-variable/12244/3 "2016-05-10T01:48:31Z")

</div>

> [@](#):
>
> This is a great idea and I can see why it would be very useful. I’m not sure exactly how feasible that is at the moment. I’ll add it to our list, but I don’t have an ETA on when we’ll get around to having a look at it.

It looks like it is simply a matter of changing the USTRUCT macro to USTRUCT(BlueprintType). I’ll update it for next release.

---

<div class="post-metadata">

**Author:** ![reveracorp](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@reveracorp](https://qa.fmod.com/u/reveracorp)\
**Post date:** [June 28, 2016, 2:11am UTC](https://qa.fmod.com/t/feature-request-event-instances-as-blueprint-data-type-variable/12244/4 "2016-06-28T02:11:27Z")

</div>

This would be very useful if possible in the next release. Was just looking into this myself.

Thanks,