Roaming Flank

AttackStill being reviewed

In one sentence

While his team has the ball, his pull towards the middle grows as play moves up and is not capped.

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: LWF/RWF, LMF/RMF. In the mobile card data: 837 cards (wingers 590, side midfielders 247).

How it works

While his team has the ball, side midfielders and wingers are pulled towards the middle by a tuck-in factor; the pull is the factor times 50 % of his distance from the middle. For wide players without Prolific Winger or Roaming Flank the factor is capped at 0.5 (at most 25 % of the distance); a Cross Specialist is capped at 0.1 (5 %). For a Roaming Flank the factor itself is recalculated: it grows from 0 to its full value as the point the team shape is built around moves forward between two points the code derives from the defensive lines, and the 0.5 cap does not apply. Wide players without Prolific Winger or Roaming Flank whose spot is on the far side from where play is follow at most 10 % of the team block's sideways shift and keep at least 80 % of their own width. A Roaming Flank is exempt. 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

In possession: tuck-in factor = 0 to 1 as play moves between two points set from the lines (30 % of the way between two line pairs).
No 0.5 cap: he can be pulled in by up to 50 % of his distance from the middle.
Far side: not limited to 10 % of the sideways shift.
In one CPU option score (an option the code numbers 3, scored from his width, his distance to goal and his spacing) the style sets his weight: Prolific Winger 1.0; Creative Playmaker, Roaming Flank, Classic No. 10, Hole Player and Attacking Full-back 0.85; Deep-lying Forward, Target Man, Dummy Runner, Goal Poacher and Fox in the Box 0.7; no style 0.5.
Only in a winger or side-midfield slot.

Without it

A wide player without the style uses the normal tuck-in factor, capped at 0.5.

Common questions

Does Roaming Flank make him dribble inside?

Short answerNo

No dribble code reads the style; it changes his position without the ball.

Does he come inside even when play is deep?

Short answerNo

His tuck-in factor is 0 until play passes the first of the two points and grows from there.

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 answerNo

No for the positioning parts: they check his formation slot every time and do nothing outside winger or side-midfield slots.

The maths

ConditionWorks only while he is deployed in a LWF/RWF or LMF/RMF slot. The game checks the slot every time against a fixed list; in any other slot these parts do nothing.

DetailTuck-in grows as play moves up; no 0.5 cap.

StepOption-3 weight 0.85.

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: No player stat is read by the style's code.