Once attacks can be recognized, the next question is immediate:
What protects the target?
A chessman can be attacked and defended at the same time. Several attackers can focus on one target. Several defenders can support it. Some attacked pieces are safe; some are vulnerable; some can be saved in several different ways.
This section introduces that first layer of piece safety without turning it into full tactical calculation.
Defending and protecting
A chessman is defended or protected when another friendly chessman exerts the relevant capture geometry toward its square.
The basic idea is:
if an enemy chessman captures this piece, a friendly chessman may be able to capture the attacker on that square afterward.
This does not guarantee that the recapture is legal, good, or sufficient in every real position. It means there is a defensive relationship that must be considered.
Defenders can be long-range or short-range
Different chessmen defend according to their normal attack geometry.
A rook can defend along an open rank or file.
A bishop can defend along an open diagonal.
A queen can defend along ranks, files, and diagonals.
A knight can defend one of its knight destinations.
A pawn defends its diagonal-forward squares.
A king can defend adjacent squares, although king-safety rules create special consequences that are covered in the legality guides.
A pawn's defended squares differ from its movement squares
This is especially important for beginners.
A pawn directly behind a friendly chessman does not necessarily defend it.
A pawn defends diagonally forward.
More than one defender
A chessman or square can be defended by several friendly chessmen.
This matters because exchanges can remove one defender while another remains.
Defended does not mean safe
A defended chessman can still be lost.
For example:
- the attacker may be worth less;
- there may be more attackers than defenders;
- a defender may itself be pinned or overloaded;
- a recapture may expose the king;
- a tactical sequence may remove the defender first;
- the attacked piece may be unable to retreat.
Most of those ideas belong later.
The foundation rule is simply:
Defense is a relationship, not a guarantee.
Defended ≠ safe. Attacked ≠ lost.
Those are different questions.
Pieces can defend squares
A friendly chessman does not need to stand on a controlled square for the square to be defended.
For example, a knight may defend an empty square that another friendly piece could later occupy.
This becomes important for:
- safe movement;
- recaptures;
- central control;
- king safety;
- tactical combinations.
The board-vision guides develop square control systematically.
Defended or not?
Create six simple positions.
For each selected White chessman, ask:
- Is it attacked?
- Is it defended?
- Which friendly chessman defends it?
Include:
- one slider defense;
- one knight defense;
- one pawn defense;
- one piece that looks defended but has a blocker;
- one piece with two defenders;
- one undefended piece.
Learning goal: Trace defensive geometry rather than guess from visual proximity.
Attackers and defenders
A useful beginner observation is to count how many chessmen currently attack and defend a target square or chessman.
This gives a first approximation of the local relationship.
Suppose:
- one Black rook attacks a White bishop;
- one White pawn defends the bishop.
We can say:
- attackers: 1;
- defenders: 1.
If a second Black chessman also attacks the bishop:
- attackers: 2;
- defenders: 1.
That is useful information.
But it is not enough by itself to evaluate the position.
Counting is a starting point, not a complete tactical evaluation.
Why counts help
Counting forces the reader to notice all relevant relationships before acting.
A beginner often sees:
"My knight attacks that pawn."
but fails to notice:
"The pawn is defended twice."
A simple local scan can prevent many avoidable losses.
Why equal counts do not imply equality
Suppose one attacker and one defender are involved.
That does not mean the exchange is automatically equal.
The chessmen may have different approximate values.
Example:
- queen attacks a defended pawn;
- pawn is defended by a rook.
If the queen captures the pawn and the rook can safely recapture the queen, the material result is terrible for the queen's side.
The local count was:
- 1 attacker;
- 1 defender.
Yet the exchange was not favorable.
This is why relative piece values matter as soon as attackers and defenders start interacting.
Order matters
A target may have:
- two attackers;
- two defenders.
But if one capture removes a key defender or changes a line, the relationship after the first exchange may differ from the initial count.
Likewise, a recapturing chessman may move away from another duty.
This is the beginning of exchange sequence reasoning.
Here we stay with elementary cases.
Full capture trees and tactical sequences require a more developed calculation method, so they are introduced later.
Visible vs effective attackers and defenders
At beginner level, count chessmen whose attack geometry clearly reaches the square.
Later, full legal analysis must ask whether each capture is actually legal.
For example:
- a pinned defender may geometrically attack a square;
- but moving it could be illegal because of king safety.
This is another reason not to treat a raw count as a final answer.
A simple attacker-defender scan
For one target:
- Identify every opposing chessman attacking it.
- Identify every friendly chessman defending it.
- Notice blockers.
- Notice the types of chessmen involved.
- Do not decide the final exchange until material and legality are considered.
This is not an algorithm for solving chess.
It is a beginner observational routine.
Count first, judge later
Show three positions.
For each target:
- count attackers;
- count defenders;
- identify the piece types.
Do not ask “Is the capture good?” until you have added basic material and exchange reasoning.
Learning goal: Separate observation from evaluation.
Undefended, hanging, and en prise pieces
Chess literature uses several overlapping terms for vulnerable material.
For beginner guides, terminology should stay stable and explicit.
Undefended
A chessman is undefended when no friendly chessman currently protects its square through the relevant defensive geometry.
This is a descriptive relationship.
An undefended chessman is not automatically in danger if no opponent can attack or capture it.
Hanging
For VeyraPlay beginner prose, use hanging for a chessman that can be captured in a way that appears to lose material without adequate compensation or recapture.
This is more practical than simply saying "undefended."
A hanging chessman is typically:
- attacked;
- inadequately protected;
- vulnerable to an immediate profitable capture.
Because tactical compensation can complicate the idea, hanging remains a practical beginner label rather than a formal FIDE category.
En prise
En prise is a traditional chess term meaning that a chessman is in a position to be captured.
Different writers use it with slightly different practical nuance.
For VeyraPlay:
- introduce the phrase for recognition;
- prefer plain beginner wording such as can be captured or is hanging when clarity matters;
- do not build a separate technical taxonomy around it.
House usage:
- undefended = no friendly defender;
- attacked = opposing capture geometry exists;
- hanging = immediately vulnerable to a materially unfavorable capture in the current simple context;
- en prise = traditional descriptive term for being capturable; explain rather than rely on it.
This keeps the terms useful without pretending chess literature has perfectly uniform boundaries.
Loose pieces deserve attention
An undefended or poorly defended chessman can become tactically vulnerable very quickly.
That creates a useful beginner habit:
notice loose material before looking for ambitious plans.
For now, stop at recognition rather than trying to calculate a full tactical sequence.
The famous tactical observation often paraphrased as “loose pieces drop off” becomes much richer in tactical play, where loose pieces interact with double attacks, removing defenders, and forcing sequences.
Classify the piece
For each marked chessman, choose the best beginner label:
- attacked;
- defended;
- both attacked and defended;
- undefended but not attacked;
- hanging in the simple material sense.
Use only positions where the classification is clear and no hidden tactical complication changes the answer.
Learning goal: Build vocabulary around piece safety.
Elementary ways to save an attacked piece
When one of your chessmen is attacked, there are several broad response families.
At beginner level, five are enough:
- move the attacked chessman;
- defend it;
- capture the attacker;
- block the attack when line geometry permits;
- create a stronger counter-threat.
The fifth option is only a preview. Full counterplay and defensive decision-making belong much later.
| Response family | Basic idea |
|---|---|
| Move | Remove the target from the attack |
| Defend | Add protection so a capture can be answered |
| Capture attacker | Remove the source of the attack |
| Block | Insert a chessman on a sliding attack line |
| Counter-threat | Create a more urgent problem for the opponent |
1. Move the attacked chessman
The simplest response is often to move the target to another square.
But the new square should itself be checked.
A beginner can "save" a bishop from one attack only to move it onto a square where another enemy chessman can capture it.
2. Defend the attacked chessman
Sometimes the target can remain where it is if another friendly chessman adds protection.
Example:
- Black attacks a White knight once;
- White moves a pawn so the pawn now defends the knight.
The target remains attacked, but the capture may now be answerable.
This still does not prove the position is safe: relative value and tactical sequences matter.
3. Capture the attacker
If the attacking chessman can itself be captured legally, removing it can end the threat immediately.
This response is especially natural when:
- the attacker is undefended;
- the capture is materially favorable;
- the resulting position is safe.
The material and exchange guides provide the first tools for judging that trade.
4. Block the attack
Blocking is possible only when the attack travels along a line with squares between attacker and target.
Therefore blocking can apply to attacks by:
- rook;
- bishop;
- queen.
It cannot normally block:
- a knight attack;
- an adjacent king attack;
- a pawn's immediate diagonal attack;
- a slider attack when attacker and target are adjacent with no intervening square.
You can block a line, not a jump.
5. Create a stronger counter-threat
Sometimes a player can respond to an attack by creating a more urgent threat elsewhere.
Example idea:
- opponent attacks your rook;
- you create a direct mating threat or attack a more valuable target.
This can be correct.
It can also be a beginner's excuse for ignoring a lost chessman.
For a beginner, the useful rule is conservative:
check whether the counter-threat actually forces a response before ignoring the attack.
Full counter-threat, zwischenzug, initiative, and counterplay concepts belong later.
Not every attacked piece needs to be saved
This is an important exception to the beginner habit.
Sometimes an attacked chessman can be deliberately left because:
- capturing it loses something more valuable;
- the attacker is pinned or tactically vulnerable;
- the capture allows checkmate;
- the piece is sacrificed intentionally;
- a stronger forcing move exists.
Those ideas require calculation.
So the correct beginner rule is not:
"Always save every attacked piece."
It is:
Always notice the attack and decide whether it requires a response.
Notice first. Evaluate second.
That habit scales all the way from beginner chess to master play.
A first piece-safety routine
Before making a move, a beginner can ask:
- What did the opponent's last move attack?
- Which of my chessmen are currently attacked?
- Which of them are defended?
- Is any chessman undefended and capturable?
- Can I move, defend, capture, or block?
- If I ignore the attack, what happens?
This is intentionally simple.
It is not the final thinking process for chess.
Later domains add:
- tactical scanning;
- candidate generation;
- calculation;
- king safety;
- strategic evaluation;
- practical time management.
But this first routine prevents one of the most common beginner failures:
making a move without noticing what is already under attack.
Choose a viable defensive response
Create five simple positions, each designed so one response family is especially clear:
- Move the attacked piece.
- Defend it.
- Capture the attacker.
- Block the sliding line.
- Create a clearly forcing counter-threat as a preview.
Question: Which response family works?
Do not require finding the objectively best move among many advanced alternatives.
Learning goal: Recognize defensive mechanisms before full tactical evaluation.
Piece-safety scan
Use one simple middlegame-like position with no checks or pins.
Ask the reader to:
- mark every attacked White chessman;
- mark every attacked Black chessman;
- identify which are defended;
- identify any undefended but unattacked chessmen;
- identify any clearly hanging chessman;
- list at least one way to respond to one attack.
Purpose: Integrate attack, defense, counting, and piece safety.
The piece-safety model to remember
The foundational relationship vocabulary is now complete.
Occupied
A chessman stands on the square.
Blocked
A movement path or destination is prevented by occupancy.
Capture
A move onto an enemy-occupied square that removes that enemy chessman.
Attacked
An opposing chessman has the relevant capture geometry toward the piece/square.
Controlled
A square lies within relevant attack influence even when it is empty.
Defended
A friendly chessman protects the target square through its attack geometry.
Undefended
No friendly chessman currently protects the target square.
Hanging
In VeyraPlay beginner usage, immediately vulnerable to a materially unfavorable capture in a simple context.
Attackers / defenders
The chessmen creating the local attacking and defensive relationships.
| State | Enemy attack? | Friendly defense? | What it tells us |
|---|---|---|---|
| Neither | No | No | No immediate local attack/defense relationship |
| Attacked only | Yes | No | Potential vulnerability |
| Defended only | No | Yes | Supported but not currently attacked |
| Attacked and defended | Yes | Yes | Capture/exchange may require evaluation |
This table describes relationships, not final safety.
A piece can be:
- attacked and defended yet still lost;
- undefended yet perfectly safe;
- apparently hanging yet tactically protected by a stronger resource.
The next step is to add material and elementary exchange reasoning so these relationships can be evaluated rather than merely observed.