Fix: Unity DOTS Entity Query Missing Tag Component

Here is how to fix Unity DOTS entity query missing tag component. You have a PlayerTag empty struct. You author a GameObject with a MonoBehaviour that should get baked into an entity with PlayerTag attached. You query [WithAll<PlayerTag>] in a system. Zero entities match. The tag exists, the query compiles, the system runs — but nothing has the tag. DOTS authoring has several places where a tag can get lost.

The Symptom

An EntityQuery with a tag component in its WithAll or WithAny clause returns zero entities. You confirm entities exist for the expected objects. You confirm the tag struct compiles. But no entities actually have the tag. Systems that depend on tagged entities never run their logic.

What Causes This

Baker does not add the tag. The MonoBehaviour-based authoring component defines what entity is created, but the Baker translates the authoring data into entity components. If the Baker does not explicitly call AddComponent<PlayerTag>(entity), the entity has no tag.

Tag struct in wrong assembly. DOTS uses assembly reflection to find component types. A tag struct in an asmdef that is not referenced by your Baker’s asmdef cannot be added. The Baker compiles but does not link the tag.

Empty struct declaration wrong. A tag is public struct PlayerTag : IComponentData {}. Missing IComponentData implementation makes it just a plain struct, not a component. Unity does not treat it as a component and queries ignore it.

Enableable components confusion. An IEnableableComponent can be present but disabled. A query with [WithAll<MyTag>] where MyTag is enableable and currently disabled skips those entities. Use SystemAPI.HasEnabledComponent or query with explicit enabled state.

Subscene not baked. If your entities live in a subscene that has not been baked (editor just opened, subscene recently edited), the entities may not exist yet. Check Entity Debugger’s World dropdown for the right world.

The Fix

Step 1: Define the tag correctly.

using Unity.Entities;

public struct PlayerTag : IComponentData { }
public struct EnemyTag : IComponentData { }

Empty struct + IComponentData is the canonical tag. Zero-size, no runtime cost beyond existing in the entity’s chunk signature.

Step 2: Write the Baker to add the tag.

using Unity.Entities;
using UnityEngine;

public class PlayerAuthoring : MonoBehaviour
{
    public float Speed = 5f;
}

public class PlayerBaker : Baker<PlayerAuthoring>
{
    public override void Bake(PlayerAuthoring authoring)
    {
        Entity entity = GetEntity(TransformUsageFlags.Dynamic);

        AddComponent<PlayerTag>(entity);
        AddComponent(entity, new MoveSpeed { Value = authoring.Speed });
    }
}

Every tag or component you want on the baked entity must be explicitly added in Bake(). Data components take a value; zero-size tags take no second argument.

Step 3: Verify in Entity Debugger. Window > Entities > Hierarchy (or Entity Debugger in older versions). Select a GameObject’s corresponding entity in the Entities Hierarchy. Inspector shows all components on that entity.

If PlayerTag is not listed, the Baker did not add it. Re-check Bake code. If PlayerTag is listed, queries targeting it should match.

Step 4: Write the query correctly.

using Unity.Entities;
using Unity.Burst;

[BurstCompile]
public partial struct PlayerMoveSystem : ISystem
{
    public void OnUpdate(ref SystemState state)
    {
        foreach (var (transform, speed) in
            SystemAPI.Query<RefRW<LocalTransform>, RefRO<MoveSpeed>>()
                .WithAll<PlayerTag>())
        {
            transform.ValueRW.Position += new float3(0, 0, speed.ValueRO.Value);
        }
    }
}

.WithAll<PlayerTag>() filters to entities that have PlayerTag. Combined with Query<T> which itself filters by type, you get only Player entities.

Enableable Components

For runtime-toggleable tags, use IEnableableComponent:

public struct IsAttacking : IComponentData, IEnableableComponent { }

// In a system:
SystemAPI.SetComponentEnabled<IsAttacking>(entity, true);

// Query respects enabled state by default
foreach (var e in SystemAPI.Query<...>().WithAll<IsAttacking>())
{
    // only entities with IsAttacking enabled
}

Enableable components are fast to toggle (no archetype change) and great for “is currently doing X” states.

Debugging Entity State

If queries return zero unexpectedly, log entity counts:

public void OnUpdate(ref SystemState state)
{
    int total = SystemAPI.QueryBuilder().WithAll<PlayerTag>().Build().CalculateEntityCount();
    Debug.Log($"Player entities: {total}");
}

Log once on first update. If it prints 0, the tag is missing. If it prints >0 but your logic does not run, the query inside your foreach is further restrictive.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“DOTS is strict. Every tag must be explicitly added in a Baker. The ECS is honest — if it says zero, there are zero.”

Related Issues

For Burst compilation issues, see Burst Compile Error Managed Code. For general query issues, DOTS Entity Query Returning Empty covers related diagnostic patterns.

Bake adds the tag. Entity Debugger confirms it. Query finds it. Three steps, reliable ECS.