AttackStill being reviewed
In one sentence
It only changes CPU choices: a distance rule that keeps deep forwards out of some CPU attacking decisions is skipped for him.
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: 1,358 cards, almost all CF (1,353).
How it works
Goal Poacher changes nothing in his stats and nothing in what you do with him. It changes CPU decisions: in one shared check that ten CPU attacking decisions use to pick a forward, other forwards outside the attacking third must be within 12 m of the offside line (a Hole Player 17 m); a Goal Poacher skips that rule. In another CPU check his allowed distance is raised to at least 25 m. The style is read in about 35 places, all in CPU decision code. 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
- Shared CPU check used by ten CPU attacking decisions: a forward without the style who is less than 18 m past halfway (outside the attacking third) and more than 12 m behind the offside line (17 m for a Hole Player) is dropped when two further conditions also hold. A Goal Poacher is never dropped by this rule.
- One CPU distance check allows him at least 25 m (other players 15 to 26 m depending on the situation, 35 m in one case).
- Only in a CF slot of the formation.
Without it
A CF without the style has to meet the 12 m rule before those CPU decisions can pick him, and keeps the normal distance limit.
Common questions
Does the style raise any of his stats?
Short answerNo
No stat is changed by the style. It only changes which CPU decisions can pick him.
Does Goal Poacher make him run in behind more often?
Short answerPartly
The code makes him eligible in more situations for ten CPU attacking decisions (no 12 m rule for him). Which on-pitch move each decision starts could not be established (see the limit above), so we cannot confirm they are runs in behind.
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. Three checks inside one CPU on-the-ball decision read the style without looking at the slot; what that decision does could not be established (see the limit above).
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.
DetailOutside the attacking third, other forwards must be within 12 m of the offside line (Hole Player 17 m) to stay in one shared CPU check; a Goal Poacher is exempt.
BendOne CPU distance limit is at least 25 m for him.
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: None of the checks described here reads a player stat: Offensive Awareness, Speed, Acceleration, Finishing and the rest are not part of the style's code.