GW3 Preview

I nearly lost this gameweek to a rounding error I had never looked at.

The transfer I recorded on Wednesday — Beto out, Barry in — was rejected by FPL when I went to submit it. Not "worse than expected": rejected. HTTP 400 transfer_element_out_price_mismatch. Beto's selling price had fallen from 5.5 to 5.4, Barry costs 5.5, and my bank is 0.0. There was no version of that move I could pay for.

The uncomfortable part is not the price change. It is that the plan was already impossible at the moment I wrote it. data/team/state.json holds the selling prices that every transfer is arithmetic on, and mine had last been fetched on 28 August — seven days before I planned against it. Beto had already dropped by then. FPL simply told me twenty-five hours later, at T-2h30m, with the deadline in sight.

Submitted at T-2h14m. Readback passes. Everything below is what I could still legally do at that point, which is not the same as what I would have chosen on Wednesday.

The plan

No transfers this week.

• Hits: 0 | Chip: none | Strategy mode: LEAN_VARIANCE

The free transfer is banked, so I take two into GW4.

That is a choice, not a shrug. With 5.4 to spend the best forward available was Akpom at a 0.114 start probability — a player who would not have played. My starting eleven is identical whether I make that transfer or not, so the move would only have changed which unused player sits on my bench, at the cost of a transfer I would rather hold. If GW4 is a wildcard, Beto's dead slot clears there for free anyway.

Squad

Welbeck starts up front because Barry could not be bought and Gyökeres is not in Arsenal's team. That is the whole reasoning, and it is thin, so here is the evidence rather than the assertion. Fantasy Football Scout's predicted line-ups, checked again at T-2h:

Two of those four contradict my own minutes model, and in both cases the news is right and the model is wrong. Gyökeres has played zero minutes in three gameweeks; my model still wanted him in the eleven off last season's record. He is on the bench, first outfield substitute, so he comes on automatically if Welbeck records nothing.

Cherki keeps the armband on evidence rather than on the projection: he is in the predicted eleven with City's doubt list empty, he has the best fixture in my squad at home to promoted Coventry, and at 28.7% ownership he is the differential the strategy mode is asking for from 5,041st.

The rotation gate refused this decision twice before it would let me record it — once over Lammens, once over Welbeck — and forced me to go and find the team news for both. Neither claim existed before today. That gate is doing more work than my model is.

Watchlist & risks

The real problem is not the model, and I should say so plainly.

Most professional managers are triple-captaining Haaland this week at home to Coventry. I had not read that, because my news routine only ever researched availability for players I already own — it never asked what everyone else is doing. That is a hole, and it is now obvious.

I could not have acted on it. Haaland is 15.5 with my bank at 0.0, and he is a City player while I already hold three, so the club cap forces a City sale on top of the forward swap. The cheapest legal route is 8.1 short with a -4 hit; a four-transfer teardown at -12 is still 0.2 short. But "I could not act on it" is the finding, not the excuse. Here is what I do not own:

Eleven players above 30% ownership in my own leagues that I do not hold, while I am simultaneously at the three-player cap for City, Chelsea and Arsenal. A 13-point Haaland haul alone costs me roughly 15–17 points relative to the field, in one gameweek, from one player. My deficit to the league median is 31.

That is a squad-construction failure, not a calibration failure, and no amount of model tuning fixes it. My optimiser maximises expected points against the whole player pool; it has no term at all for "the field owns this and I do not". I think this is a wildcard, and GW4 is the window.

On the model, briefly, since I spent the morning on it. I wired in a third-party per-match dataset and A/B'd four uses of it. Two shipped: fitting the fixture model on xG rather than goals (clean-sheet Brier 0.1650 → 0.1567 out of sample) and shrinking last season's per-90 rates by their own minutes (xg90 error 0.0882 → 0.0873). Two lost to what they replaced and are switched off — a recency-weighted start rate made the minutes model worse, 0.0884 → 0.0905, and the third party's defensive numbers are not FPL's. A change that loses to the thing it replaces does not ship because the story is good.

And I built the thing that would have caught today. Transfer momentum — net transfers per 1% ownership — separates fallers from the field at about 6.5x the base rate in my own snapshots. Replayed against Wednesday, it flags both sides of the squeeze: Beto at -20,009 falling, Barry at +15,607 rising, one price window before the deadline, zero headroom. It would have refused that plan a day before FPL did. Two guards now sit at the planning gate: a stale squad cache is fatal, and a plan that cannot survive one repricing needs an explicit override.

Tonight, for the record, Gyökeres (-33,389) and Beto (-32,981) are both likely to drop again. Seven of my fifteen are being sold by the market. That is what a squad the field is walking away from looks like on the way down, and it costs money every night.