FPL Review

FPL planning toolset with integrated projections & multi-period solver

[FPL Review @fplreview]

https://t.co/h10ZWb0pTz is back for the 2026/27 season!

A lot of work has gone into the new interface, but hopefully it feels like it has retained much of its original DNA

- Redesigned interface & improved mobile UX
- Upgraded solver features
- Detailed player customisation
- Team strength customisation
- Ability to upload & blend/ensemble custom models fully supported
- Massive Data model update + adoption of new BPS rules
- Enables greater development capabilities in the long term

[FPL Review @fplreview]

@UltrawRBX Good to hear, at least this case is pretty benign- though it may become a thing for anti FPL managers😂

[FPL Review @fplreview]

Stumbled across a team that somehow managed to set the same player as captain and vice in GW6. Wonder what happened there...

https://t.co/w8aWaSQ4qT

[FPL Review @fplreview]

@FPLJoeYT It's a good shout that something like that could be at the root of the case

I wonder aswell if people still use 3rd party apps to actually set their selections etc. which could further open the door to storing invalid selections

[FPL Review @fplreview]

@UltrawRBX Wow, really interesting! Hopefully other selection cases are guarded😬

[FPL Review @fplreview]

@harrydukehd1 I believe VC stays with the player subbed off in that case. At least this is the only case I've come across this from the ~70M selection dataset, only found out as it crashed a script

[FPL Review @fplreview]

Hey, the default settings should be totally fine to work with

There is a documentation site, which is in the process of being updated for the new interface, that will cover much of the settings- but typically I would suggest just running on default

In terms of suggestions- it absolutely will vary from team to team based on the circumstances, you can exclude specific players if you don't like them, or force specific transfers as you prefer

The image attached for example would block bringing in Odegaard, and will force solves to bring in Mbeumo this week

I'd suspect Saka being out increases the appeal of Ode for context though

[FPL Review @fplreview]

A few smaller updates added over the past week or so

- Page load should be much snappier (especially on mobile)
- WC/FH diversity added as a solver setting
- Arrows keys can control both GW (←→) and draft (↑↓) selection in planner
- Solver gain/loss in evaluation score now displayed
- Significant backend upgrade

[FPL Review @fplreview]

@FlapjackFpl No idea either, maybe something the app can be stepped into but not on desktop?

[FPL Review @fplreview]

@Salfetnikov24 Hi Oleg, the redesign of fplreview over the summer moved away from php fortunately which inadvertently was good timing

[FPL Review @fplreview]

@_PeteO_ What device/browser are you using? Can you send me on a screenshot?

I'll try to get to the bottom of this for you

[FPL Review @fplreview]

@_PeteO_ Eval should be changing based on FT val, total EV won't though. Seems to be working on my side, might be worth double checking. If it's still not working I can investigate

[FPL Review @fplreview]

Agree. I think in general there can be a few upgrades to the chip planning process- one in particular is that it should be feasible for the tool to recommend good weeks for specific chips as it's a significant enough task to leave to the user and there's a bit of a temptation to just click for every chip combo

[FPL Review @fplreview]

@FPL_White Hey, I sent you a DM now

[FPL Review @fplreview]

He's predicted pretty highly over the past GWs since he effectively won the LW role with his competition out injured

Before GW1, there was a lot of uncertainty around medium term mins due Mitoma in particular, which has obviously dragged on longer than people expected. There is still uncertainty for whenever Mitoma comes back

Beyond minutes, he's certainly performed beyond any reasonable expectation, not to mention his underlying numbers

Still a strong right now, and I even have him myself!

[FPL Review @fplreview]

Schade is on 75% availability and projected as unused ~26% of the time

In simple terms, Schade will enable autosubs on top of his EV, while Mbeumo will not

The maths will look like this
- If you start Schade you 3.3 + (26% x 4.3) = 4.375
-If you start Mbeumo you get 4.3 + (1% x 3.3) = 4.333

Very marginal, and I'd suggest fine tuning the settings as you prefer

[FPL Review @fplreview]

It forces the minimum amount of differences between the solved plans for WC/FH

If the solver is left just looking for unique outputs, typically it will just shuffle one bench fodder player etc. while settings of 2/3 force it to actually generate meaningfully diverse suggestions

So for example with the new default settings, the 3rd plan it generates must have 2 different squad members than each of the initial two plans

[FPL Review @fplreview]

Forgot to mention one of the more requested changes, selling a player now no longer forces a replacement immediately. You can click to buy a direct replacement, or you can open up multiple empty slots and go to the player list seperately

[FPL Review @fplreview]

Also worked through a number of the remaining issues during the IB, eg. for synced selected the 'my team' in the prices changes view needed to be updated

If you have any feedback/bug reports, please continue to use the Google Form => https://t.co/IU0yWdM1Hd

That form is anonymous, so if you need direct support the best route is email

[FPL Review @fplreview]

Hey, yes!

This is because Konsa is modelled as being unused ~43% of the time

So you get his 2.6pts + ~43% of Halls 4.2 pts = 4.4pts

While Hall is modelled as being unused only 1% of the time.

Starting Hall would get 4.2pts + 1% of 3.0pts = 4.23pts

You can adjust those distributions- for example if you think Konsa is likely to sub on, then he quickly loses his spot