# Unpossess firing on begin play **URL:** \ **Category:** Blueprint\ **Tags:** possessing-pawns, unreal-engine, bug-report, UE4, Blueprint, question\ **Created:** [June 21, 2017, 1:19pm UTC](https://forums.unrealengine.com/t/unpossess-firing-on-begin-play/396443 "2017-06-21T13:19:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Supreme.net](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Supreme.net](https://forums.unrealengine.com/u/Supreme.net)\ **Post date:** [June 21, 2017, 1:19pm UTC](https://forums.unrealengine.com/t/unpossess-firing-on-begin-play/396443/1 "2017-06-21T13:19:31Z")
Hello! I just noticed that when, i try to possess pawn alpready placed in level automatically fires unpossess event. Actualy there takes place following behaviour: player controller possess pawn, then unposseess and then posseess again. We have three fired event . Steps for replication: Create project based on thirdperson blueprint template. In the game mode set `player pawn` to `none`. Then place character to level and set `autopossess` option to `player 0`. In `ThirdPersonCharacter` blueprint add `Event Posses`s, and `Event Unposesss` with `print string` node connected. See result. Here link to video: [- YouTube](https://youtu.be/V1H4Cla9qtU) ![190980-gamemode.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/b/4/6b47087b5a9dfb54becf9c6201d757f109793987.png) ![190981-bp.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/e/8/2/e82293a849df31a50bfc7945dcb9884bf2c9c41f.png) ![190982-pawnsettings.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/1/2/a1294e501465af8cfc2fb09abbb71e1516085af4.png) ---
**Author:** ![anonymous\_user\_e729f54e](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_e729f54e](https://forums.unrealengine.com/u/anonymous_user_e729f54e)\ **Post date:** [July 31, 2017, 6:52pm UTC](https://forums.unrealengine.com/t/unpossess-firing-on-begin-play/396443/2 "2017-07-31T18:52:22Z")
Hello Supreme, I was able to reproduce this issue on our end. I have written up a report and I have submitted it to the developers for further consideration. I have provided a link to the public tracker. Please feel free to use the link provided for future updates. Link: [Unreal Engine Issues and Bug Tracker (UE-47883)](https://issues.unrealengine.com/issue/UE-47883) Make it a great day ---
**Author:** ![anonymous\_user\_a075c5d9](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_a075c5d9](https://forums.unrealengine.com/u/anonymous_user_a075c5d9)\ **Post date:** [March 19, 2018, 6:48pm UTC](https://forums.unrealengine.com/t/unpossess-firing-on-begin-play/396443/3 "2018-03-19T18:48:33Z")
Yup, having the same problem. The player controller possessed the pawn then ejected and repossessed. So it called twice. Not sure why this is happening unless that is Epic intention. ---
**Author:** ![Alizia](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Alizia](https://forums.unrealengine.com/u/Alizia)\ **Post date:** [January 1, 2023, 5:37pm UTC](https://forums.unrealengine.com/t/unpossess-firing-on-begin-play/396443/4 "2023-01-01T17:37:04Z")
The bug is still present in 5.0.3. Really annoying. It happen also if you possess the character with Possess(). A solution we find was to use the event on the player controller, this one is only called once. ---
**Author:** ![Metalvenomuk](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/metalvenomuk/32/925664_2.png) [@Metalvenomuk](https://forums.unrealengine.com/u/Metalvenomuk)\ **Post date:** [July 17, 2023, 9:16am UTC](https://forums.unrealengine.com/t/unpossess-firing-on-begin-play/396443/5 "2023-07-17T09:16:49Z")
+1 still in 5.2 ---
**Author:** ![Maciek\_Leto](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/maciek_leto/32/1194559_2.png) [@Maciek\_Leto](https://forums.unrealengine.com/u/Maciek_Leto)\ **Post date:** [October 14, 2023, 8:49pm UTC](https://forums.unrealengine.com/t/unpossess-firing-on-begin-play/396443/6 "2023-10-14T20:49:59Z")
Still in UE5.3. BTW Epic reported they won’t fix. My workaround is to check the game mode for a valid value it sets after the player has clicked the UI. ---
**Author:** ![Animbeast1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Animbeast1](https://forums.unrealengine.com/u/Animbeast1)\ **Post date:** [November 29, 2024, 1:17pm UTC](https://forums.unrealengine.com/t/unpossess-firing-on-begin-play/396443/8 "2024-11-29T13:17:09Z")
In Your Pawn BP , "auto posses ai "is not set to disabled. That why at begin play the pawn gets possed by AIController and Event Possed Fires.