# Behavior tree still running after player controller possesses actor

**URL:** <https://forums.unrealengine.com/t/behavior-tree-still-running-after-player-controller-possesses-actor/2844723>\
**Category:** Blueprint\
**Tags:** unreal-engine, question\
**Created:** [October 24, 2026, 4:53pm UTC](https://forums.unrealengine.com/t/behavior-tree-still-running-after-player-controller-possesses-actor/2844723 "2026-10-24T16:53:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pastelfable](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/pastelfable/32/1138306_2.png) [@pastelfable](https://forums.unrealengine.com/u/pastelfable)\
**Post date:** [October 24, 2026, 4:53pm UTC](https://forums.unrealengine.com/t/behavior-tree-still-running-after-player-controller-possesses-actor/2844723/1 "2026-10-24T16:53:53Z")

</div>

In my project the player can switch between characters, and when they switch off a character an AI controller possesses it and runs a behavior tree, which is currently just a move to and an attack task. When switching back to that character though the behavior tree still runs the move to task even though the AI controller has unpossessed the actor. Does anyone know why this might be happening?

My current blueprints in the AI controller:

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/e/4/c/e4c495647c44a56e84e1d2219506bea2e1a0f795.png)

---

<div class="post-metadata">

**Author:** ![pastelfable](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/pastelfable/32/1138306_2.png) [@pastelfable](https://forums.unrealengine.com/u/pastelfable)\
**Post date:** [October 24, 2026, 7:30pm UTC](https://forums.unrealengine.com/t/behavior-tree-still-running-after-player-controller-possesses-actor/2844723/2 "2026-10-24T19:30:01Z")

</div>

I figured it out! originally i just had event unpossessed connected to spawn default controller in my actor blueprint, but event unpossessed gets called every time something unpossesses an actor, so it was also being called when the ai controller was unpossessing the actor and was getting itself stuck in a loop

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/0/4/20464bf5fbfaf37712ed229d2b0b1f99af651a44.png)