# Novice blueprint logic problems

**URL:** <https://forums.unrealengine.com/t/novice-blueprint-logic-problems/1167124>\
**Category:** Game Development\
**Tags:** unreal-engine, question\
**Created:** [May 16, 2023, 3:00am UTC](https://forums.unrealengine.com/t/novice-blueprint-logic-problems/1167124 "2023-05-16T03:00:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ClockworkOcean](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/clockworkocean/32/1169999_2.png) [@ClockworkOcean](https://forums.unrealengine.com/u/ClockworkOcean)\
**Post date:** [May 16, 2023, 12:23pm UTC](https://forums.unrealengine.com/t/novice-blueprint-logic-problems/1167124/3 "2023-05-16T12:23:56Z")

</div>

And now… ( drum roll ) the correct answer 🙂

Very similar, in fact. When you make the widget, give it an actor reference variable, and expose it on spawn, like this

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/8/f/a8faf3b501c5aea5aa17535d69c103a67e73d6ec.png)

When you create the widget ( from wherever ), you say

![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/9/3/d/93d397c326ea351d6d4765727dd24d4fd675238d.png)

The widget responds to the actor with a blueprint interface

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/d/f/5/df5333fcae6dd546aac538ed85d6f789ff0ec6f6.png)

That call gets caught in the blueprint

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/5/a/4/5a454c187eddc09f0b28cb5c833f2ae758ead133.png)

The interface definition

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/f/2/af28d7421629593527cf6a589398bff0d7fbc75f.png)

---

_[View the full topic](https://forums.unrealengine.com/t/novice-blueprint-logic-problems/1167124)._
