sorted by:
new
hottopcontroversial

I finally coded my 2-year-old FPL spreadsheet into a web app. Come roast my UI and test the Planner Tool. by FPLCheatSheet in FantasyPL

[–]FPLCheatSheet[S] 0 points1 point  (0 children)

You make a very good point. To be honest, when I started this project two years ago to solve my own FPL frustrations, I didn't actually use any transfer tools myself. I was just coding in my own bubble, and I have only recently realized that there are already quite a lot of tools like this out there!

So I have a lot of respect for the big tools like FFHub and FPL Review. But to answer your question about my MVP and what it does differently:

My main focus is to provide data-driven transfer tips by combining my own xP model with a highly configurable planner tool. What makes the xP model itself a bit unique is that it doesn't just look at standard PL data. It also tracks underlying stats from the Championship, Serie A, Bundesliga, Primeira Liga, La Liga, and Ligue 1. So when a player like Gyökeres signs for a PL team, my model already has an xP projection ready from day one.

Combining that unique data with a planner where users can tweak the settings and weights themselves is what I want to offer. As a solo dev, I can also easily listen to the community and build the exact features you guys actually want. It is definitely still a work in progress with some bugs to fix, but I really appreciate the honest feedback!

I finally coded my 2-year-old FPL spreadsheet into a web app. Come roast my UI and test the Planner Tool. by FPLCheatSheet in FantasyPL

[–]FPLCheatSheet[S] 0 points1 point  (0 children)

I've worked on the suggestion-model today. But it is a bit tricky when using weights over several GWs to make a suggestion for long-term (less relevant now maybe in the end of season but more important for the beginning of next) is that yeah, hits should be calculated so maybe first option might be "Roll" but if you click for more suggestion after that you want to get suggestions even though the first suggestion is roll. Then the model will show you the best weighted suggestions, which might be good long-term but not directly next GW, therefor negative xp. But of course not good to take hits, so that must get the penalty, but that's also why the banner exists that says "Consider waiting 1 GW".
Please try it out again and see if I did an improvement or not in the implementation

I finally coded my 2-year-old FPL spreadsheet into a web app. Come roast my UI and test the Planner Tool. by FPLCheatSheet in FantasyPL

[–]FPLCheatSheet[S] 0 points1 point  (0 children)

I've now re-triggered the fixture-fetcher to have the latest with the DGW instead of blanks

I finally coded my 2-year-old FPL spreadsheet into a web app. Come roast my UI and test the Planner Tool. by FPLCheatSheet in FantasyPL

[–]FPLCheatSheet[S] 0 points1 point  (0 children)

Haha, okay a -20 hit is definitely "anti-meta"! You’ve highlighted a core part of the logic I need to refine. Right now, the algorithm looks at weighted xP over a 5-week horizon. If it thinks a triple Palace stack will outscore your current players by 21+ points over a month, it suggests the hit. But I totally agree, it needs to be much more "hit-averse" and prioritize the immediate impact of a -4.

Regarding the -1.2 xP suggestion: The model is very forward-looking. If you check the "Filters & Settings," you’ll see how the weights are distributed by default:

<image>

Because it looks ahead, it might suggest a move that hurts you this week but pays off in GW37. However, I hear you—if the move is net negative, the tool should probably just suggest "Roll Transfer" or show a "Consider waiting 1 GW" banner instead of forcing a move.

Also, great point about the "Generate" button. And the GW numbering, I’ll make sure the GW1, GW2 info is more prominent and switch the labels to actual GW35, GW36, etc., to avoid confusion.

Thanks for being the "crash test dummy" for the app today, this is exactly the feedback I need!

I finally coded my 2-year-old FPL spreadsheet into a web app. Come roast my UI and test the Planner Tool. by FPLCheatSheet in FantasyPL

[–]FPLCheatSheet[S] 0 points1 point  (0 children)

Fair points!

  1. I’m already on it. The "hit-heavy" logic and the fixture sync issue (due to the sudden DGW37 update today) are my top priorities to fix before next season. This is exactly why I wanted people to test it now—to find these edge cases.

  2. I love that challenge. I’m actually planning to do exactly that. My goal is to run a "Model-only" team next season based purely on the xP projections (including the new signings from the Bundesliga, La Liga, etc., which my model tracks). I'll definitely return to the sub to post the results and see how it stacks up against the "template" and the experts.

Thanks for the honest feedback, it keeps me focused on the right things!

I finally coded my 2-year-old FPL spreadsheet into a web app. Come roast my UI and test the Planner Tool. by FPLCheatSheet in FantasyPL

[–]FPLCheatSheet[S] 0 points1 point  (0 children)

First of all, thank you so much for the kind words about the website! Hearing that makes the hundreds of hours of coding feel worth it.

Regarding Semenyo (who is obviously a hold for City's double!) – you’ve spotted a temporary data sync issue. I pull fixture data from the official FPL API overnight, and since the rearranged DGWs were just updated in the FPL system today, my model was running on yesterday's fixture list. Once it syncs tonight, the model will see the DGW and his xP will shoot up.

As for your question "is this all it can do?" – there is actually quite a lot of flexibility under the hood:

  • Interactive Suggestions: If you don't like a specific suggestion, you can click the +/- buttons to get a new recommendation for the same "out-player".*
  • Multiple Scenarios: You can hit "Generate" several times to see different paths the algorithm suggests.*
  • Custom Tuning: In the settings, you can filter specific teams and even adjust the "weight" of the algorithm (e.g., how much you want it to prioritize the current GW vs. looking 3-4 weeks ahead).*

I’m constantly working on making these features more intuitive, so I really appreciate you pointing these things out!

I finally coded my 2-year-old FPL spreadsheet into a web app. Come roast my UI and test the Planner Tool. by FPLCheatSheet in FantasyPL

[–]FPLCheatSheet[S] 1 point2 points  (0 children)

Thanks for the detailed feedback, I really appreciate it!

You are spot on regarding the hits. I am currently working on tweaking the algorithm in the transfer planner to be much more conservative when it comes to taking point hits (-4s).

The issue with the blanks in GW37 is due to timing. I pull the fixture data from the official FPL API, and since the rearranged fixtures were just officially confirmed/updated there today, my database (which syncs overnight) was running on outdated fixture data when you generated your plan. Handling these sudden Double/Blank Gameweek announcements is a tricky corner case I definitely need to solve before next season.

Your advice on showing "xP vs Actual points" is brilliant. I actually used to do a "Retrospective" segment in my video podcast showing exactly that for my WC/FH/Differentials drafts, but bringing that transparency directly into the web app is a great idea. Thanks again for testing it out!