Install
From Fab to the plugin enabled in your project, in a few minutes. It works the same in a Blueprint-only project and a C++ one.
Install it to the engine
- In the Epic Games Launcher, open Fab Library and find NPC Behavior & Daily Life System.
-
Click Install to Engine and pick your engine version (5.6, 5.7 or 5.8).
The launcher copies the plugin into the engine’s
Engine/Plugins/Marketplacefolder, ready built. Every project on that engine can now enable it.
Enable it in your project
- Open your project and pick Edit > Plugins.
-
Search for
NPC Behaviorand tick NPC Behavior & Daily Life System.
The plugin in Edit > Plugins, ticked. - Click Restart Now. The editor reopens with the plugin on, and the engine’s State Tree, Gameplay State Tree, Smart Objects and Enhanced Input plugins with it.
Enabling it adds, with nothing else to set up:
- NL Character, a ready NPC, and NL Spot in Place Actors, and a Brain component (NL Brain) for any actor of yours;
- the world’s NPC life: a clock that starts at 08:00 and runs an hour a real minute, and a scheduler that thinks every NPC in the level within a time budget;
- the
Npc.*console commands and the Gameplay Debugger’s NPCLife category.
Its settings, the clock, the factions and how often NPCs think, are under Project Settings > Plugins > NPC Life (the settings).

The plugin’s own content (its behaviours, roles, icons and the demo town) is under Plugins > NPC Behavior & Daily Life System in the Content Browser. If you don’t see it, open the Content Browser’s Settings and turn on Show Engine Content and Show Plugin Content: installed to the engine, it counts as both.
Use it from C++
Blueprint-only projects need nothing more. In a C++ project, add the module to your game
module’s Build.cs to call the plugin from your code:
PublicDependencyModuleNames.AddRange(new string[] { "NPCLife", "GameplayTags" });
Then include what you use, such as NLBrainComponent.h, NLSubsystem.h and NLLibrary.h. The
how-tos give the C++ beside each Blueprint answer.
[!TIP] A team or a build machine needs the plugin too. Copy its folder from
Engine/Plugins/Marketplaceinto your project’s ownPluginsfolder and commit it; the project then builds it with its own code, so a machine that packages the game needs Visual Studio with its C++ tools, as for any code plugin in a project.In a Blueprint-only project, also open the copied
NPCLife.upluginin a text editor and add the line"EnabledByDefault": false,after"CanContainContent": true,. Without it the packaged game is the engine’s ready-built one, without the plugin, and stops as it starts with “Unable to load plugin”. The project keeps the plugin ticked in Edit > Plugins either way.
Update it
When a new version is out, the Fab Library offers it. Close the editor, install it to the engine again, and open your project. Your NPCs, spots, behaviours and save games carry over; the changelog says if a version needs anything of you.
Remove it
- Delete the NL Characters and NL Spots from your levels, the Brain components from your actors, your behaviours and roles, and the Blueprints that call its nodes.
- Untick it in Edit > Plugins and restart the editor.
[!WARNING] Levels holding its actors, and Blueprints using its nodes or assets, don’t load or compile cleanly without the plugin. Remove them before you disable it.