Logic Driver Pro

Logic Driver Pro by Recursoft is the state machine plugin many Unreal projects use for AI, quests, dialogue and gameplay flow. With the Logic Driver extension, Ultimate Engine CoPilot builds those state machines for you: it creates the asset, adds states, transitions and conduits, writes the transition conditions, lays the graph out, compiles it, and checks it in PIE.

It works through Logic Driver Assist, Recursoft’s own authoring layer for Logic Driver, so every edit is the same one you would make by hand in the Logic Driver graph editor.

---

What you need

In your project’s Plugins folder:

• Logic Driver Pro 2.11 or newer, from Recursoft.
• Logic Driver Assist (the SMAssist plugin), from Recursoft.

Plus Ultimate Engine CoPilot with the Logic Driver extension switched on.

Without Logic Driver Assist the extension does nothing harmful. It adds one status tool and nothing else changes.

---

Setting it up

1. Install Logic Driver Pro 2.11+ in your project.
2. Put Logic Driver Assist in the same project’s Plugins folder.
3. In the CoPilot, open Settings > Extensions and switch on Logic Driver. It is off by default.
4. Restart the editor. On startup the CoPilot finds Logic Driver Assist’s operations and adds each one as a tool.
5. Ask the AI to check the Logic Driver status. It reports whether Logic Driver Assist was found and how many operations were added, and if something is missing, it says what.

---

What you can ask for

• “Make an enemy AI state machine with Idle, Patrol, Chase and Attack. Chase when the player is within 1,500 units.”
• “Add a Stunned state that any state can enter, and return to Idle after 2 seconds.”
• “Give each state a speed and a color, and show them on the nodes.”
• “Lay this graph out so nothing crosses, then show me a screenshot.”
• “Put the actor in the level, start PIE and tell me which state it is in.”

Behind those requests the AI can:

• Create state machine Blueprints and add states, transitions, conduits, link states, Any States and nested state machines.
• Write transition conditions inline, or assign a transition class. It can also make a transition fire on an event instead of every tick.
• Give states a node class with their own variables, and set each state’s values, shown on the node.
• Add the state machine component to an actor and set when it starts.
• Lay out the graph, find overlapping nodes and take a screenshot of the graph.
• Compile, then read a running PIE instance’s active state to prove the flow works.

---

Graphs a person can read

A state machine is there to be read, so the AI treats layout as part of the build:

• Every state is wired in. Exactly one state starts the machine, and no node is left unconnected.
• Its own folder. New state machines go into a clean folder. Your existing ones stay untouched unless you ask.
• Layout once, at the end. The AI lays out new graphs after it has added everything, so nodes that grow with their properties still have room. Edges that would cross a state get rerouted.
• Checked, not assumed. It looks for overlaps and takes a screenshot of the graph, and it uses link states and nested state machines instead of long edges back across the graph.
• Proven in PIE. A clean compile is not proof the flow is right, so it runs the machine and reads the active state.

---

Permissions

Reading is free: inspecting an asset, a graph or a running state runs without asking. Every change asks first, the same way as the rest of the CoPilot. The few changes that cannot be undone, like removing states or replacing a class, are marked as destructive.

---

How the bridge works

• Found, not hard-coded. The CoPilot reads Logic Driver Assist’s operations when the editor starts and adds whatever the installed version has. When Recursoft adds or changes an operation, the tools follow without a CoPilot update.
• Their descriptions, their parameters. Each tool carries Logic Driver Assist’s own description and parameter list, so the AI sees the real argument names and types. A call with a wrong argument is answered with the right ones instead of being sent on.
• Everywhere at once. The tools work in the CoPilot’s chat, in external MCP clients like Claude Code and Cursor, and in coding agents. See MCP Integration.
• Names. Logic Driver Assist names operations with a dot, like ld.add_state. In the CoPilot they become ld_add_state, ld_add_transition, ld_compile and so on. Recursoft’s Logic Driver Assist guide uses the dotted names, and lists every operation.
• No link between the plugins. The bridge talks to Logic Driver Assist through its console commands, so neither plugin depends on the other to build, and the CoPilot works the same with or without Logic Driver installed.

---

Experimental

Logic Driver Assist is marked experimental by Recursoft, and its operations may still change. Because the CoPilot reads them at startup instead of hard-coding them, the extension keeps up on its own.

See Extensions for how extensions work, the Logic Driver Assist guide for every operation it offers, and the Logic Driver documentation for Logic Driver itself.