UEFN Template Abilities: How to Build and Publish Custom Powers

UEFN template abilities allow Fortnite creators to make custom powers using inputs, targeting and timed effects. Since Epic’s v42.40 update on October 15, 2026, Abilities and Fortnite Template Abilities have left Experimental. Islands using custom abilities can now be published, rather than being restricted to testing.

Epic’s Spicy Sprint example is a good first project: the player gets faster, but takes damage while the power is active. It teaches you how an ability, an item and a device fit together. Once that works, you can start changing the effects to suit your own island.

How UEFN template abilities work

Each template has an input action, a targeting query and a timeline. The input starts the power. The target determines who receives it, whether that’s the player using it, someone under the reticle or entities in an area. Timeline elements then control when animations, sound, Niagara effects and gameplay effects happen.

With UEFN template abilities, you can arrange timeline elements in the editor instead of coding every action from scratch. A point runs once at a specified time, while a span stays active between its start and end times. More involved powers still need Verse, but the timeline handles a lot of the timing.

How to make UEFN template abilities with Spicy Sprint

For a working example, follow Epic’s Spicy Sprint quickstart. The steps below explain its order; copy the complete Verse implementation from Epic rather than relying on an abbreviated sample.

1. In UEFN, open Verse > Verse Explorer. Right-click the project and choose Create Verse File. Call the empty file template_ability_example.
2. Open the project in VS Code. Add Epic’s imports for Abilities, Devices, Itemization, Scene Graph and Simulation. Define the template_ability class with ActiveEffects, MakeContext() and MakeAbility().
3. Save and select Compile Verse. In Content Browser, use Add (+) > Entity Prefab to create PF_SpicySprintItem.
4. Add an item_component, set its category to FortniteItemCategories.WeaponMelee, then add fort_item_ability_component with an ItemAbilities entry pointing to template_ability.
5. Set the input action to IA_Sprint and target query to self_ability_target_query. Add the burn and pepper status-effect elements for damage over time and a speed boost.
6. Place the item prefab in the level. Create Epic’s template_ability_item_granter_device, compile its Verse script, place the device and assign its prefab reference.
7. Launch a play session and press Sprint. The example increases movement speed while health takes periodic damage.

The item-granting step is what ties UEFN template abilities to something a player can use. Compiling the class won’t automatically add Spicy Sprint to your inventory. The prefab needs its item components, and the device must point at the placed prefab instance. Check that the player receives the item before troubleshooting its effects.

Can you publish islands using UEFN template abilities?

Yes. Version 42.40 moved Abilities and Fortnite Template Abilities out of Experimental, so islands using supported custom abilities can be published. They still need to pass the normal Creator Portal checks. If you’re preparing a release, our island thumbnail requirements guide explains the current Discover artwork rules.

One part of Epic’s tutorial needs care: its Spicy Sprint quickstart still instructs creators to enable Scene Graph Experimental Features and Custom Items and Inventory. That’s separate from the 42.40 announcement about abilities leaving Experimental. Follow the prerequisites for your example and check the project’s publishability before submitting it, rather than assuming every older setting has disappeared.

UEFN template abilities: what changed in 42.40?

If you built UEFN template abilities before v42.40, start by reviewing their targeting code. Abilities now use entities instead of agents. On fort_wedge_ability_target_query, CentralAngle became Angle and now uses radians rather than degrees (90 degrees is approximately 1.57 radians). The fort_ability_attach_socket and fort_target_query_affiliation enums are now open.

Epic also fixed several bugs: animations replicate and loop properly, rejected activations no longer play their timeline, and Cancel really stops the timeline. End events work when a player unequips an item during use. A failed Use call now logs the failure, making it easier to identify an activation problem.

What if UEFN template abilities aren’t activating?

Start by checking that Verse compiles, the prefab has fort_item_ability_component, the ability is assigned in the item, and the granter device points to the placed prefab. Then check the InputTrigger and targeting query. A power with no working item grant or mismatched input won’t activate even if its animation looks correct.

For older UEFN template abilities that stopped working, check whether the target query still returns the correct entity and whether any wedge angle uses the right unit. Then inspect the editor log for failed Use calls. That is more useful than swapping animation assets when the problem is targeting or item setup.

Do you need Verse for every power?

You can configure the effects, input and timing of straightforward powers through the editor, so you won’t write complex custom activation logic for every ability. But Spicy Sprint itself still requires a Verse class and an item-granting device. That makes the system simpler, not entirely code-free.

After Spicy Sprint works, change one thing and run another test. Try a different target, adjust the effect timing or swap the status effect. That’s a much easier way to build up UEFN template abilities than making three big changes before testing any of them.

Official tutorial and complete code: Epic Games, Fortnite Template Ability Quickstart.