UEFN Nested Loot Pools: Build Multi-Stage Rewards and Control Duplicates

UEFN nested loot pools let one loot-table entry point to another pool, so a reward can be selected in stages. The experimental system arrives with Fortnite 43.10 and is useful for designing a chest that first chooses a category, then chooses an item within that category. You cannot publish an island using this API while it remains experimental.

Think of a boss that usually drops healing items but occasionally drops a weapon. A parent pool can choose the reward category first. The child pool then decides which item to give. That keeps the category chances separate from the weights assigned to individual items.

How UEFN nested loot pools are structured

The LootPools module provides weighted_loot_entry_pool for a weighted entry that represents another loot_pool. By comparison, a weighted_loot_entry_item represents an item entry. A parent weighted pool can select a pool entry; the child then supplies its own selection. Check the exact API shape against your installed UEFN version before writing the Verse object construction.

The concept is straightforward, but v43.10 is the first experimental release and signatures may change.

UEFN nested loot pools: an example with category odds

Suppose a parent pool chooses healing items 80% of the time and weapons 20% of the time. If the weapon pool contains two equally weighted items, each weapon has a 10% chance overall in a simple one-roll selection. Those are example values, not the drop rates of an existing Fortnite chest.

Prevent duplicates with UEFN nested loot pools

UEFN nested loot pools do not automatically prevent duplicates. The weighted_loot_entry class includes MaxSelectionCount, which limits how many times an entry can be selected during one SelectLoot call. Decide whether that limit belongs on the parent category, a child item, or both. Test several rolls with a small pool before adding more entries.

UEFN nested loot pools: where player context fits

Epic also provides loot_context, which can allow loot selection to depend on information about the actor or player accessing a pool. Keep context-dependent conditions separate from category weighting when debugging. First prove that your category odds behave as expected with a fixed context. Then vary one condition at a time.

Otherwise a reward may appear unusually rare simply because most test runs did not meet its requirements.

Nested chest versus boss drop

A chest might select one category and one item. A boss could make two independent selections: a standard drop and a bonus reward. They can share the same child pools, but remember that changing a shared pool changes every chest or enemy that uses it. Test each lootable separately.

What happens when a nested selection cannot return loot

The parent pool chooses a weighted_loot_entry_pool, which then asks its child pool for a result. If that child cannot produce loot, the selection can fail. That is different from the parent simply choosing an item you didn’t expect. Test a child pool on its own before nesting it inside a larger table, especially when entries have conditions.

Selection limits also matter. Epic’s weighted_loot_entry_pool reference says MaxSelectionCount set to zero prevents the entry from being selected, while false means there is no limit. With several rolls, an exhausted entry drops out of the eligible options. The parent pool’s weights may therefore mean something different on the second roll from the first.

If a chest sometimes returns nothing, log which parent entry was selected and whether its child produced a result. Check the child pool’s available entries, weights and selection limits. Then check how many rolls the parent requested. That gives you a much clearer diagnosis than changing weights at random and hoping the missing reward starts appearing.

UEFN nested loot pools FAQ

Does nesting prevent duplicate loot? No. Use entry limits and tested roll rules if you need to control repeated selections.

Why use a nested pool instead of one flat pool? It lets you adjust a category chance separately from the probabilities of items inside it.

Is this ready for published islands? Not in 43.10. The LootPools module is experimental.

Official source: Epic Games documentation.