A generic tracker doesn’t know what a Blueprint is. To it, “the door blueprint keeps double-firing” is just a string — no different from “buy milk.” You still have to go and find the door. The task points at nothing.
When the task and the work are strangers
The trouble with a tool built for every industry is that it understands none of them. It can hold the sentence “the muzzle flash is too bright in the night level” but it can’t hold the muzzle flash, or the night level, or the node doing the flashing. So a real part of every task becomes archaeology: working out which asset, which node, which level the note was ever about.
Multiply that by a sprint’s worth of tasks and you’ve built a second job out of finding things.
Point the task at the real object
In Kard, a task carries typed references to the things it concerns — and clicking one takes you there:
- A Content Browser asset → syncs the browser straight to it.
- A level → opens the map.
- A Blueprint or material node → opens the graph editor focused on that exact node.
- A Sequencer frame → opens the sequence and scrubs to the frame.
- A line of C++ → opens the file, and re-finds the line even if it has moved since.
You create most of these from a right-click — on an actor, a Content Browser asset, a Blueprint node, a Sequencer track, a PCG or Niagara node. The task remembers the object, and the object’s tile in the Content Browser shows a badge when tasks point at it. Delete a referenced asset and the reference marks itself broken, rather than rotting silently into a dead end.
Let the work file its own tasks
The most reliable task is the one nobody had to write down. Kard can scan your project for TODO / FIXME / HACK comments — across your C++ and your Blueprint comment nodes — and turn the ones you choose into tasks, writing a small marker back into the source so the next scan skips them.
It can also read the Unreal Message Log — Map Check, Blueprint, Lighting, and more — and turn warnings into tasks, each one already linked to the actor or asset that raised it.
Your Map Check errors become a to-do list that already knows where each problem lives.
Not another silo
The real fear with any new tool is a second place to keep in sync. Kard sidesteps it by pointing at the real objects instead of copying them. There’s no mirror of your project to drift out of date — only typed links to the assets you already have, that break loudly the moment the thing they point at goes away.
The task and the work finally speak the same language.