# ShakeDown API added to the fort\_down\_but\_not\_out\_component

**URL:** <https://forums.unrealengine.com/t/shakedown-api-added-to-the-fort-down-but-not-out-component/2854496>\
**Category:** Feedback & Requests (UEFN)\
**Tags:** unreal-editor-for-fortnite, fortnite-creative, fortnite\
**Created:** [November 12, 2026, 10:49am UTC](https://forums.unrealengine.com/t/shakedown-api-added-to-the-fort-down-but-not-out-component/2854496 "2026-11-12T10:49:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![DionPowder](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/dionpowder/32/1221509_2.png) [@DionPowder](https://forums.unrealengine.com/u/DionPowder)\
**Post date:** [November 12, 2026, 10:49am UTC](https://forums.unrealengine.com/t/shakedown-api-added-to-the-fort-down-but-not-out-component/2854496/1 "2026-11-12T10:49:42Z")

</div>

### Select a topic

Verse API

### Tell us your feedback. What is working, what is not, and what would you change?

43.10 added a bunch of components related to the fort\_character, one of them being the down but not out. I haven’t tried them yet, but these components are amazing and super useful from the looks of it. So thank you so much for adding this! (even if it is in experimental)

I would like to see 3 more API’s added to the down but not out component, these being:

- SetShakeDownsAllowed(NewShakeDownsAllowed:logic):void
- ShakeDownEvent:listenable(entity) = external {}, Sends the agressor
- ShakenDownEvent:listenable(entity) = external {}, Sends the victim

This would allow us to control/track when shakedowns happen more precisely 🙂

### Please provide any supporting material that you think will help describe your feedback. (.jpg, .png, .gif)

 ![Screenshot 2026-10-30 145733.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/f/0/6f0f48991a2f6162285fd256f909b5ad117544c2.png)

 ![Screenshot 2026-11-12 115511](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/c/c/6cc72404cc2623e6f5c97ef509bbecbc59566f1e.png)

---

<div class="post-metadata">

**Author:** ![FragileNucleusGames](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/fragilenucleusgames/32/1103901_2.png) [@FragileNucleusGames](https://forums.unrealengine.com/u/FragileNucleusGames)\
**Post date:** [November 12, 2026, 2:25pm UTC](https://forums.unrealengine.com/t/shakedown-api-added-to-the-fort-down-but-not-out-component/2854496/2 "2026-11-12T14:25:00Z")

</div>

> [@DionPowder](#):
>
> - ShakeDownEvent:listenable(entity) = external {}, Sends the agressor
> - ShakenDownEvent:listenable(entity) = external {}, Sends the victim

It could be one event that returns the two entities.

```auto
# Returns a tuple of the aggressor and victim
ShakeDownEvent:listenable(tuple(entity, entity)) = external {}

```

---

<div class="post-metadata">

**Author:** ![DionPowder](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/dionpowder/32/1221509_2.png) [@DionPowder](https://forums.unrealengine.com/u/DionPowder)\
**Post date:** [November 12, 2026, 2:39pm UTC](https://forums.unrealengine.com/t/shakedown-api-added-to-the-fort-down-but-not-out-component/2854496/3 "2026-11-12T14:39:57Z")

</div>

Yup, I just copied the setup from the DBNO device, but that could work too

or an event that returns a new struct like the elimination result

![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/f/b/1/fb11b48d8027ba4910d97c1e58247b87ef4420af.png)

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/e/5/0/e5030f2c066c97ea5d3f115c572dd8ba15c133a5.png)
