Community Team Reveal Gameweek 24 – FPL Shake n Bake

Each Gameweek brings an FPL community team reveal. As a result, that person gives insight into their transfers, captaincy and future plans.

Ahead of Gameweek 24, it’s the turn of FPL Shake n Bake (Brett) to tell us what is happening to his team.

Hi Brett and thanks for the team reveal. So how did Gameweek 23 go?

It signalled the end of a very dismal run of six straight red arrows, as I’d dropped from 34k to below 200k. But these 79 points took me back up to 169k. As for many, Phil Foden and Ollie Watkins were the stars of the show but unfortunately I captained Dominic Solanke in hopes of him repeating his hat-trick versus Nottingham Forest. Alongside these were returns for Cole Palmer, Anthony Gordon, Bukayo Saka, Erling Haaland and Emiliano Martinez.

What does your defence look like?

In goal, the latter rotates with Martin Dubravka and I often play the wrong one! The back five consists of Pedro Porro, Pervis Estupinan, Josko Gvardiol, Malo Gusto and James Tarkowski. The attacking potential of the first two is well documented but they play in leaky defences, so I may look to move at least one of them on soon – likely Pedro Porro with his upcoming blank.

The blank also applies to Gusto, so he could be on the chopping block too. Tarkowski is a solid option who can slot in when the fixtures suit, whilst I’m most excited about Gvardiol. He appears to be as nailed as a Man City defender can be, thriving in his new left-back role by getting involved in their attack. Against Brentford, he registered three shots (only Foden and Julian Alvarez took more) and created two chances (better than all but Foden and Kevin De Bruyne).

If Man City could stop finding annoying ways to lose clean sheets, then a haul could be coming.

Meanwhile, what about your midfield and attack?

It seems to be a cursed midfield. I brought in Eberechi Eze for Gameweek 22 – he grabbed two goals but then hurt his hamstring. This week, Gordon assisted in the goal-fest v Luton but also went off injured. I’ll await further news on both before deciding who to take out.

Next to those, I have Saka – who seems to be coming back into form – golden boy Foden and his previous understudy Palmer. Up front, the aforementioned Haaland, Watkins and Solanke.

So what are your transfer plans for Gameweek 24 and beyond?

I think it’s going to be a four-point hit that sets me up for Double Gameweek 25 by bringing in some Liverpool assets for their tasty-looking meeting with Burnley beforehand. I’m hoping they can deliver some big returns.

The first transfer is Solanke out for Darwin Nunez. I can’t quite believe I’m bringing him in, having been a massive critic ever since he signed for Liverpool. I know it’s going to be frustrating but also one hell of a ride. Anything can happen with him and I’m going to embrace the chaos for a few weeks, maybe I can get lucky.

Solanke is unlucky to get the chop but with Newcastle and Man City coming way before his Double Gameweek 28, short-term fixtures go against him. In midfield, I’m bringing in Diogo Jota for either Gordon or Eze, depending on their injury updates. With £5.6m in the bank, budget won’t be an issue.

One player I really want but can’t yet work out a plan for is Ross Barkley. He’s been really impressive for Luton this season and, against Sheff Utd this weekend, he could be a real differential. But I’m not sure I can gamble on him, as I want to play 3-4-3 and wouldn’t start him ahead of Jota, Saka, Foden or Palmer.

If there’s an early leak of Foden being benched in the early kick-off, I could potentially bring him in for the other part of my injured duo. If not, he could replace Palmer for his double, whereas Palmer travels to Man City.

Finally, what about captaincy?

Tough call this week. Haaland and the Man City guys have the risky early kick-off. That makes Jota or Darwin the favourites. I’m not sure embracing Darwin’s chaos needs to go to this extreme, so it’s either playing the EO game and going with Haaland, or Jota. Currently, the armband is on Jota but that may change nearer the deadline.