Tags and layers in Unity - Step-by-Step Execution

Concept Flow - Tags and layers

Create GameObject

↓

Assign Tag

↓

Assign Layer

↓

Use Tag/Layer in Code

↓

Check Tag/Layer in Scripts

↓

Perform Actions Based on Tag/Layer

This flow shows how you create a GameObject, assign tags and layers, then use them in scripts to control behavior.

Execution Sample

Unity

GameObject enemy = new GameObject("Enemy");
enemy.tag = "Enemy";
enemy.layer = LayerMask.NameToLayer("Enemies");

if(enemy.CompareTag("Enemy")) {
    Debug.Log("This is an enemy!");
}

Creates a GameObject, assigns it a tag and layer, then checks the tag in code to print a message.

Execution Table

Step	Action	Variable/Property	Value	Result/Output
1	Create GameObject	enemy.name	"Enemy"	GameObject created with name 'Enemy'
2	Assign tag	enemy.tag	"Enemy"	Tag set to 'Enemy'
3	Assign layer	enemy.layer	LayerMask.NameToLayer("Enemies")	Layer set to 'Enemies' layer index
4	Check tag with CompareTag	enemy.CompareTag("Enemy")	true	Condition true
5	Print message	Debug.Log	"This is an enemy!"	Message printed to console
6	End			Script ends

💡 Script ends after printing message because tag check is true

Variable Tracker

Variable/Property	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
enemy.name	null	"Enemy"	"Enemy"	"Enemy"	"Enemy"	"Enemy"
enemy.tag	null	"Untagged"	"Enemy"	"Enemy"	"Enemy"	"Enemy"
enemy.layer	N/A	0	0	Layer index of 'Enemies'	Layer index of 'Enemies'	Layer index of 'Enemies'
CompareTag result	N/A	N/A	N/A	N/A	true	true

Key Moments - 2 Insights

Why do we use CompareTag() instead of directly checking enemy.tag == "Enemy"?

CompareTag() is optimized by Unity and avoids errors if the tag does not exist. See execution_table row 4 where CompareTag returns true safely.

What happens if the layer name "Enemies" does not exist?

LayerMask.NameToLayer returns -1 if the layer name is missing, so enemy.layer would be set to -1, which means no valid layer. See execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What does enemy.layer get set to?

A -1 because layers are not assigned

B The integer index of the 'Enemies' layer

C The string 'Enemies'

D The tag 'Enemy'

💡 Hint

Check the 'Value' column at step 3 in execution_table

At which step does the script confirm the GameObject has the 'Enemy' tag?

A Step 4

B Step 2

C Step 5

D Step 3

💡 Hint

Look for the CompareTag check in execution_table

If enemy.tag was set to "Player" instead of "Enemy", what would CompareTag("Enemy") return at step 4?

A true

B null

C false

D throws error

💡 Hint

CompareTag returns true only if tags match exactly, see variable_tracker CompareTag result

Concept Snapshot

Tags and Layers in Unity:
- Tags identify GameObjects by name for easy grouping.
- Layers help with rendering and physics filtering.
- Use CompareTag() to check tags safely.
- Assign layers by name with LayerMask.NameToLayer.
- Tags and layers control behavior and interactions.

Full Transcript

This visual execution shows how to create a GameObject in Unity, assign it a tag and a layer, then check the tag in code to perform an action. First, the GameObject named 'Enemy' is created. Then, its tag is set to 'Enemy'. Next, the layer is assigned using LayerMask.NameToLayer with the name 'Enemies'. The script then uses CompareTag to check if the GameObject has the 'Enemy' tag. Since it does, the script prints 'This is an enemy!' to the console. The variable tracker shows how the name, tag, and layer properties change step by step. Key moments clarify why CompareTag is preferred and what happens if a layer name is missing. The quiz tests understanding of layer assignment, tag checking, and CompareTag behavior. This helps beginners see how tags and layers work in Unity scripts.

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