AttackStill being reviewed
In one sentence
While his team has the ball he follows the team's sideways shift at most 30 %, so he stays more central.
Who does this affect?
Only players the CPU is moving: your AI teammates and the opponent's players. The style changes where the CPU puts him and what the CPU decides for him; while you steer him yourself, your input decides. Found on: Compatible: CF only. In the mobile card data: 562 cards, all CF.
How it works
While his team has the ball, every outfield player's spot moves sideways with the team block. A centre-forward or second striker without this style takes at most 60 % of that shift; a Fox in the Box at most 30 %; a Target Man and all other positions 100 %. So he stays nearer the middle. In one CPU movement his target is also kept within 9.16 m of the middle (the six-yard box's width), and one CPU on-the-ball option score gets +20. Limit: these CPU decisions give players numbered roles that have no names in the code. Turning each role into a named move (for example a run in behind) needs the whole CPU role system mapped, which this audit could not complete, and live measurement was not possible (no device connection). They are therefore described only by what the code checks.
When it applies
- While his team has the ball (team shape): share of the block's sideways shift at most 0.3 (CF/SS without the style at most 0.6; Target Man and every other position 1.0). For strikers the share can be smaller still depending on where play is.
- One CPU movement (used for a numbered role the code does not name): his target point is kept within 9.16 m of the middle of the pitch.
- One CPU on-the-ball option score: +20 (same as Target Man; Deep-lying Forward +10). This part ignores his slot.
- One CPU on-the-ball decision is skipped when he has the ball (also for Anchor Man, The Destroyer, Build Up and Defensive Full-back); what the decision does could not be established.
- Only in a CF slot for the positioning parts.
Without it
A centre-forward without the style follows up to 60 % of the team's sideways shift and has no 9.16 m limit in that CPU movement.
Which stats it reads
Physical Contact sets how strongAdds 0 to 60 points to one CPU on-the-ball option score: nothing at 60 or below, the full 60 at 80 and above. The style adds 20 on top; the score is kept between 20 and 100.
Offensive Awareness sets how strongAdds 0 to 20 points to the same score: nothing at 60 or below, the full 20 at 90 and above.
Common questions
Does Fox in the Box make him shoot more or better?
Short answerNo
No shooting or finishing code reads the style; it changes where the CPU positions him and one CPU option score.
Does he never leave the box?
Short answerNo
The code only limits how far he follows the team's sideways shift (30 %) and keeps one movement target within 9.16 m of the middle; nothing pins him inside the box.
Does the style help when I control the player myself?
Short answerNo
Every place in the code that reads this style is CPU positioning or a CPU decision. Your own dribbles, passes, shots and runs never look at it.
Does the style still work if I play him out of position?
Short answerPartly
No for the positioning parts: they check his formation slot every time and do nothing outside a CF slot. The +20 option score and one on-the-ball check ignore the slot.
The maths
ConditionWorks only while he is deployed in a CF slot. The game checks the slot every time against a fixed list; in any other slot these parts do nothing.
LimitSideways shift with the team block at most 30 % (normal striker 60 %).
LimitTarget kept within 9.16 m of the middle in one CPU movement.
DetailLimit: this score belongs to one of the options the CPU weighs when it has the ball at his feet; the option class has no name in the code and its follow-up action could not be identified, and live measurement was not possible, so the card does not name the move (for example holding the ball up).
DetailLimit: these CPU decisions give players numbered roles that have no names in the code. Turning each role into a named move (for example a run in behind) needs the whole CPU role system mapped, which this audit could not complete, and live measurement was not possible (no device connection). They are therefore described only by what the code checks.
DetailNot used by this style: Finishing, Heading, Speed and the other stats are not read by the positioning parts of the style.
Booster points per stat
Physical ContactBooster points do not count here.
Offensive AwarenessBooster points do not count here.