Prolific Winger

AttackStill being reviewed

In one sentence

While his team has the ball he escapes two rules that keep wide players narrow on the far side and limit their tuck-in, and one CPU support spot puts him on the touchline.

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 only. In the mobile card data: 1,670 cards (LWF 928, RWF 732, side midfielders 10 - no effect there).

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 %). A Prolific Winger is not capped. 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 Prolific Winger is exempt from that too. In one of the CPU's support-position calculations his spot is set on the touchline on his side (Cross Specialist the same). He also gets the top weight (1.0) in one CPU attacking option. 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, team shape: no 0.5 cap on his tuck-in factor (others: at most 25 % of their distance from the middle).
In possession, far side: not limited to 10 % of the block's sideways shift.
One CPU support-position calculation: spot on the touchline (34.06 m from the middle) on his side, unless a condition the code checks first (not identified) applies.
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 LWF/RWF slot.

Without it

A winger without the style has his tuck-in capped, is held to 10 % of the sideways shift when on the far side, and is not put on the touchline in that support calculation.

Common questions

Does Prolific Winger make him stay wide all the time?

Short answerNo

The code lifts two narrowing limits and puts one support spot on the touchline, but without the cap his tuck-in can actually be larger than another winger's; it is not a 'stay wide' rule.

Does it make him cut inside?

Short answerNo

No dribble or cut-inside code reads the style.

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 a LWF/RWF slot.

The maths

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

DetailExempt from the 0.5 tuck-in cap and the far-side 10 % rule.

DetailTouchline spot in one CPU support calculation.

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.