Why Tags and layers in Unity? - Purpose & Use Cases

The Big Idea

Discover how a simple label can save you hours of debugging and boost your game's speed!

The Scenario

Imagine you have a big game scene with many objects like enemies, players, walls, and pickups. You want to find all enemies quickly or make sure the player only collides with walls, but you have to check every single object one by one.

The Problem

Manually checking each object is slow and tiring. It's easy to miss some objects or make mistakes. As the game grows, this becomes a huge mess and slows down your game's performance.

The Solution

Tags and layers let you group objects by type or purpose. You can quickly find or filter objects by their tag or layer, making your code cleaner and your game faster.

Before vs After

✗ Before

if (obj.name == "Enemy1" || obj.name == "Enemy2" || obj.name == "Enemy3") { /* do something */ }

✓ After

if (obj.CompareTag("Enemy")) { /* do something */ }

What It Enables

Tags and layers let you organize and control game objects easily, enabling efficient collision detection, filtering, and game logic.

Real Life Example

In a racing game, you can put all obstacles on one layer and all pickups on another. Then, the car only collides with obstacles, ignoring pickups, making the game run smoothly.

Key Takeaways

Manually managing objects by name is slow and error-prone.

Tags and layers group objects for easy identification and filtering.

This improves game performance and simplifies your code.

Practice

1. What is the primary purpose of Tags in Unity?

easy

A. To identify and find GameObjects by name

B. To control the rendering order of objects

C. To group objects for physics collisions

D. To store numerical values for objects

Solution

1. Step 1: Understand what Tags do

   Tags are used to label GameObjects with a name for easy identification.

2. Step 2: Compare with Layers

   Layers group objects mainly for collision and rendering, not identification by name.

3. Final Answer:

   To identify and find GameObjects by name -> Option A

4. Quick Check:

   Tags = Identify objects by name [OK]

Hint: Tags name objects; layers group them for collisions [OK]

Common Mistakes:

• Confusing tags with layers
• Thinking tags control rendering
• Assuming tags store numbers

2. Which of the following is the correct way to check if a GameObject has a specific tag in C# script?

easy

A. if (gameObject.CheckTag("Enemy"))

B. if (gameObject.tag == "Enemy")

C. if (gameObject.HasTag("Enemy"))

D. if (gameObject.layer == "Enemy")

Solution

1. Step 1: Recall Unity tag checking syntax

   Unity uses gameObject.tag == "TagName" to check tags.

2. Step 2: Identify incorrect options

   layer is an int, not string; HasTag and CheckTag are not Unity methods.

3. Final Answer:

   if (gameObject.tag == "Enemy") -> Option B

4. Quick Check:

   Check tag with .tag == "Name" [OK]

Hint: Use gameObject.tag == "TagName" to check tags [OK]

Common Mistakes:

• Using layer property to check tags
• Calling non-existent methods like HasTag
• Comparing layer to string

3. Given this code snippet, what will be printed if the GameObject's layer is set to 8?

void Start() {
    if (gameObject.layer == 8) {
        Debug.Log("Layer is 8");
    } else {
        Debug.Log("Other layer");
    }
}

medium

A. Layer is 8

B. Other layer

C. Compile error

D. No output

Solution

1. Step 1: Understand the layer property

   The layer property is an integer representing the object's layer number.

2. Step 2: Check the condition

   If the GameObject's layer is 8, the condition gameObject.layer == 8 is true, so it prints "Layer is 8".

3. Final Answer:

   Layer is 8 -> Option A

4. Quick Check:

   Layer 8 matches condition, prints "Layer is 8" [OK]

Hint: Layer is an int; compare with number, not string [OK]

Common Mistakes:

• Comparing layer to string instead of int
• Assuming layer is a tag
• Expecting compile errors from valid code

4. What is wrong with this code snippet?

void Update() {
    if (gameObject.tag = "Player") {
        Debug.Log("Player detected");
    }
}

medium

A. Tags cannot be compared in Update method

B. gameObject.tag is not accessible in Update

C. Debug.Log cannot be used inside if statements

D. Using assignment (=) instead of comparison (==) in if condition

Solution

1. Step 1: Identify the if condition error

   The code uses = which assigns "Player" to gameObject.tag instead of comparing.

2. Step 2: Understand correct comparison

   To compare, use == operator, so it should be gameObject.tag == "Player".

3. Final Answer:

   Using assignment (=) instead of comparison (==) in if condition -> Option D

4. Quick Check:

   Use == to compare tags, not = [OK]

Hint: Use == for comparison, not = assignment [OK]

Common Mistakes:

• Using = instead of ==
• Thinking Debug.Log can't be inside if
• Believing tag is inaccessible in Update

5. You want to make sure your player GameObject only collides with enemies on a specific layer called "EnemyLayer". Which approach correctly uses layers to achieve this in Unity's physics settings?

hard

A. Assign all objects to Default layer and ignore collisions in script

B. Use tags to identify enemies and check collisions manually in code

C. Assign player to "PlayerLayer" and enemies to "EnemyLayer", then configure Layer Collision Matrix to allow collisions only between these layers

D. Set both player and enemies to the same layer and disable collisions globally

Solution

1. Step 1: Understand layer collision matrix

   Unity's Layer Collision Matrix lets you control which layers collide with each other.

2. Step 2: Assign layers and configure collisions

   Assign player and enemies to different layers and enable collision only between those layers in the matrix.

3. Step 3: Evaluate other options

   Using tags for collision is inefficient; ignoring collisions or disabling globally is not selective.

4. Final Answer:

   Assign player to "PlayerLayer" and enemies to "EnemyLayer", then configure Layer Collision Matrix to allow collisions only between these layers -> Option C

5. Quick Check:

   Use layers + collision matrix for selective collisions [OK]

Hint: Use Layer Collision Matrix to control collisions by layers [OK]

Common Mistakes:

• Using tags instead of layers for collision filtering
• Assigning all objects to Default layer
• Disabling collisions globally instead of selectively