To read a position reliably, board vision must move through several layers:
- coordinates;
- lines and rays;
- piece-specific reach.
The next step is to reverse the question.
Instead of asking only:
Where can this chessman reach?
we also ask:
What affects this square?
That shift from a piece-centric view to a square-centric view is one of the foundations of board vision.
A single square may be:
- attacked by one side;
- attacked by both sides;
- defended by several friendly chessmen;
- unaffected by either side;
- connected to a latent line hidden behind a blocker.
These are spatial relationships.
They do not yet tell us:
- whether occupying the square is safe;
- whether a capture works tactically;
- who strategically "owns" the square.
Attack, control, defense, and legal movement
Several related words are used in chess literature.
They should not be collapsed into one idea.
Attack
FIDE defines attack through capture geometry and explicitly preserves an important king-safety nuance:
a chessman can still be considered to attack a square even when moving there would be illegal because that move would expose or leave its own king under attack.
That means:
attack map ≠ legal move map.
A square can be attacked even when the corresponding move is not legal.
Control
Control is common explanatory chess language.
In this guide, control describes a side's spatial influence over a square.
But the exact meaning should be stated in context.
For example:
attacked squarecan be used when the FIDE attack relationship is intended;controlled squarecan be used pedagogically for a broader spatial map;defended square/piecedescribes friendly protection.
Do not silently use control as a synonym for:
- legal destination;
- safe square;
- strategically owned territory.
Defense
A friendly chessman is commonly said to defend or protect another friendly chessman or square when its capture geometry would support that location against an enemy presence.
This is a spatial relationship.
It does not prove that:
- a recapture works;
- the defended chessman is safe;
- the position is tactically sound.
Legal move
Legal movement is narrower than geometry/attack.
It includes:
- own-king safety;
- check restrictions;
- special rules.
Full move legality adds another layer beyond geometric attack and defense.
From piece to attacked squares
The piece-centric question is:
What squares does this chessman attack from here?
The answer depends on:
- piece type;
- origin square;
- board boundary;
- blockers;
- pawn direction;
- current occupancy;
- the FIDE pinned-piece attack nuance.
Rook attack scan
For a rook:
- choose one rank/file ray;
- move outward square by square;
- include clear squares along the ray;
- stop at the first occupied square;
- evaluate the contact according to occupancy/context;
- do not continue direct line influence beyond that blocker.
Friendly blocker nuance
A friendly chessman stops direct rook travel.
In ordinary chess language, that friendly chessman may be described as:
- defended/protected by the rook.
For visual systems, it is useful to distinguish:
- empty/enemy squares in the direct attack map;
- friendly-occupied defended contact square.
Bishop attack scan
The bishop works identically in principle, but only on diagonals.
For every diagonal ray:
- scan outward;
- stop at first blocker;
- preserve square-color geometry.
Queen attack scan
The queen combines:
- rook-style rays;
- bishop-style rays.
Attack-map construction is therefore:
- four orthogonal scans;
- four diagonal scans.
A slider attack map is the union of its independently scanned rays.
One blocker affects:
- one ray;
not
- every queen direction.
Knight attack scan
A knight does not ray-scan.
Instead:
- generate the eight theoretical 2+1 offsets;
- discard destinations outside the board;
- inspect the remaining destination squares.
Intervening occupancy is irrelevant.
King attack scan
A king attacks its geometrically adjacent squares.
At board-vision level:
- interior → up to 8;
- non-corner edge → up to 5;
- corner → up to 3.
The attack relationship must not be confused with legal king movement.
A king can geometrically attack a square that it cannot legally enter because:
- the opposing side also attacks that square.
King attack neighbourhood ≠ legal king destinations.
Pawn attack scan
Pawns require their own directional map.
White pawn
Attacks:
- one rank forward;
- one file left/right where those board squares exist.
Example: White pawn e4 attacks:
- d5;
- f5.
Black pawn
Example: Black pawn e5 attacks:
- d4;
- f4.
The square directly in front is not a pawn attack square.
Do not derive pawn attacks from:
- forward movement;
- occupied destination.
Pawn attack geometry exists even when the diagonal target square is empty.
Pinned-piece attack nuance
Consider this example:
- White king e1;
- White rook e2;
- Black rook e8.
The White rook is constrained from moving horizontally if doing so exposes its own king.
Yet FIDE Article 3.1.3 still treats the rook as attacking squares according to the attack rule even when the corresponding move is forbidden by own-king exposure.
Therefore:
attack map;legal move map
must remain separate visual/conceptual layers.
Piece-centric attack-map exercise
For each isolated piece position:
- mark every attacked square;
- mark friendly defended contact squares separately;
- mark legal destinations only if the exercise explicitly asks for them.
Include:
- rook;
- bishop;
- queen;
- knight;
- king;
- White pawn;
- Black pawn.
Learning goal: build correct piece-specific attack sets before whole-board overlays.
From square to attackers
Now reverse the viewpoint.
Target square:
e4
Question:
What attacks e4?
Do not scan piece by piece randomly.
Use a structured square-centric search.
Square-centric attack scan
For a target square, inspect potential attacker source families.
1. Knight-source squares
Which squares are one knight move from the target?
For e4, theoretical sources include:
- c3;
- c5;
- d2;
- d6;
- f2;
- f6;
- g3;
- g5.
Then inspect:
- which of those squares actually contain opposing knights.
Knight-source geometry is symmetric: if A is a knight move from B, B is a knight move from A.
2. Pawn-source squares
Pawn sources depend on color.
To find:
"Which White pawns attack e4?"
reverse White's attack direction.
Potential White pawn sources:
- d3;
- f3.
To find:
"Which Black pawns attack e4?"
potential Black pawn sources:
- d5;
- f5.
Pawn attack lookup must include color direction.
3. King adjacency
Any opposing king on a square adjacent to the target geometrically attacks it.
For e4:
- eight surrounding squares if on board.
Legal positions prevent kings from standing illegally adjacent, but the geometric source scan remains useful.
4. Rank/file rays
From the target square:
scan outward in four orthogonal directions.
The first encountered chessman on each ray is the only direct slider candidate from that direction.
If it is an opposing:
- rook;
- queen;
then it attacks the target along that clear ray.
If the first blocker is another type:
- direct rook/queen line from farther beyond is blocked.
For slider-source scanning, nearest blocker first.
5. Diagonal rays
Scan outward in the four diagonal directions.
The first encountered chessman on each ray can directly attack the target if it is an opposing:
- bishop;
- queen.
Again:
- farther aligned sliders are blocked by the nearer chessman.
Complete target-square scan
For a chosen target square:
- [ ] Knight sources
- [ ] White-pawn sources
- [ ] Black-pawn sources
- [ ] King adjacency
- [ ] Four rank/file rays
- [ ] Four diagonal rays
This procedure can identify all direct geometric attackers without scanning the entire board without structure.
Example: all attackers of e4
Create a legality-checked position where e4 is attacked by:
- one knight;
- one bishop;
- one rook/queen;
- one pawn.
Ask:
- list every attacker;
- state each attack family;
- identify any aligned piece blocked from attacking e4.
Square-centric vs piece-centric vision
These are complementary.
Piece-centric
What does my bishop attack?
Useful for:
- piece footprint;
- move consequences;
- attack-map construction.
Square-centric
What attacks d5?
Useful for:
- destination scanning;
- defended/contested square analysis;
- king-safety reasoning;
- tactical awareness later.
Good board vision can move in both directions: piece → squares and square → pieces.
Defended squares and pieces
The same square-centric method can identify friendly defenders.
Suppose a White knight stands on e4.
Ask:
Which White chessmen protect e4?
Search:
- knight source squares;
- White pawn source squares;
- king adjacency;
- rank/file rays for White rook/queen;
- diagonal rays for White bishop/queen.
Because the target square is occupied by a friendly piece, it is clearer to say:
- defended;
- protected;
- supported;
rather than pretending the friendly chessman can literally be captured by its own side.
Attacker
Opposing chessman producing the relevant attack relationship.
Defender
Friendly chessman supporting the target through appropriate capture geometry.
Defense count
Number of friendly defenders identified under the stated spatial model.
This is descriptive data, not a tactical verdict.
Multiple defenders
A piece can have:
- zero defenders;
- one defender;
- several defenders.
Example:
White pawn d4 may be defended by:
- pawn c3;
- knight f3;
- queen d1 along a clear file? Only if line geometry actually supports the target; verify final example.
Defender order on slider lines
Only the nearest compatible slider with a clear segment provides direct line support.
If:
- White rook a1;
- White bishop a4;
- White queen a7;
the rook does not directly defend the queen through its own bishop blocker.
Alignment: yes.
Direct defense: blocked.
Aligned behind a friendly blocker ≠ direct defender.
Hidden or blocked defensive relations
A farther chessman may be geometrically aligned with a friendly target but currently blocked.
Example:
- White rook a1;
- White bishop a4;
- White queen a7.
The rook-target relationship can become active if:
- bishop leaves the a-file.
At the geometric level this is a latent line relationship.
Do not yet call it:
- x-ray;
- discovered tactic;
- tactical battery
unless the later domain defines that exact usage.
Defended does not mean safe
The basic safety principle still applies.
Suppose a queen is:
- attacked once;
- defended once.
That information alone does not answer whether a capture works.
Why?
Because:
- attacker/defender values differ;
- move order matters;
- recaptures can open lines;
- pins can make a defender unusable as a legal move;
- tactical sequences can continue.
Defense count is descriptive, not sufficient tactical evaluation.
Board vision maps these relationships before tactical calculation begins.
Domains 05 and 07 calculate consequences.
Contested squares
A square is contested when both sides exert relevant attack/control influence on it.
Example: d5.
White attackers/controllers:
- knight f4;
- pawn c4.
Black attackers/controllers:
- bishop g2? Only if geometry is correct in final position;
- pawn e6.
The exact pieces do not matter conceptually.
The square has:
- White influence;
- Black influence.
Therefore: contested.
Contested square
A square affected by both sides under the stated attack/control model.
Do not use contested to mean:
- tactically safe;
- strategically owned;
- equally controlled.
It describes two-sided influence.
Counting attackers and defenders on a contested square
A contested square can have counts such as:
- White: 2;
- Black: 1.
Or:
- White: 3;
- Black: 3.
Those counts are useful descriptive data.
But:
2 vs 1 does not automatically mean White can safely occupy the square.
Counts alone do not establish tactical safety.
Possible reasons:
- values differ;
- pinned pieces;
- overloaded defenders;
- forcing captures;
- king exposure;
- intermediate moves;
- tactical motifs.
Those belong later.
Contested-square overlay
Contested-square exercise
For target d5:
- list all White attackers/controllers;
- list all Black attackers/controllers;
- count each side;
- classify:
- uncontested;
- exclusively controlled by White;
- exclusively controlled by Black;
- contested.
Do not ask:
"Who wins the square?"
That tactical evaluation is a separate step beyond the spatial description.
Putting attacks, defenses, and contested squares together
Board vision now works in two directions.
Piece-centric
What squares does this chessman attack?
Square-centric
What chessmen attack or defend this square?
The structured square scan checks:
- knight sources;
- pawn sources by color;
- king adjacency;
- rank/file rays;
- diagonal rays.
A target can have:
- attackers;
- defenders;
- multiple relationships;
- two-sided contest.
But:
- attack ≠ legal move;
- defended ≠ safe;
- contested ≠ strategically owned;
- counts ≠ tactical conclusion.
Attack-and-defense mastery check
- [ ] I can build an attack set from one piece.
- [ ] I preserve pawn attack direction.
- [ ] I preserve the pinned-piece attack nuance.
- [ ] I can scan one target square for knight sources.
- [ ] I can reverse pawn-source geometry.
- [ ] I scan slider rays nearest-blocker-first.
- [ ] I distinguish attackers from defenders.
- [ ] I can count multiple defenders descriptively.
- [ ] I identify contested squares.
- [ ] I know attacker/defender counts are not a tactical verdict.
The next section broadens from one square to:
- uncontrolled/exclusive control;
- direct/latent relationships;
- side-wide attack maps;
- before/after spatial updates.
Frequently asked questions
Is an attacked square the same as a legal destination?
No. A piece can geometrically attack a square even when moving there would be illegal. Pinned pieces and kings make this distinction especially important.
Is a defended piece always safe?
No. Defense means a friendly piece supports the square or piece; it does not prove that an exchange, tactic, overload, pin, or sequence is favorable.
What is a contested square?
A contested square is one influenced by both sides. That describes the current attack/control relationship, not who strategically “owns” the square.