Manchester City will be without a full-time striker ahead of the visit of Crystal Palace on Saturday as Sergio Aguero, Stevan Jovetic and Edin Dzeko are all nursing injuries respectively.
Elsewhere, Manuel Pellegrini will also be without captain Vincent Kompany who has picked up a similar injury to the one he has just recovered from during last weeks 1-0 win against Leicester.
Manchester City aren't particularly keen on facing London opposition this season with just one win against a side from the capital; a 4-1 triumph against Tottenham Hotspur. But an uncharacteristic defeat against West Ham as well as draws with Queens Park Rangers, Chelsea and Arsenal have seen Manuel Pellegrini's side drop several points which could cost them a second successive Premier League title in the long run of things.
However, times have changed since the dark Champions League days and struggle some Premier League fixtures as City have won their previous seven fixtures in all competitions.
But the absence of a threatening strikeforce presence was obvious at the King Power Stadium last weekend as a Frank Lampard goal was all that separated the two sides.
Crystal Palace will be looking to capitalise on the unwanted misfortunes at the top of the field for their opponents, but have striker issues of their own with Marouane Chamakh struggling with a hamstring issue, so that could clear the pathway for the unsettled Dwight Gayle who has been recently linked with a move to Leicester or Burnley during the week.
Neil Warnock will be bolstered by the return of defender Adrian Mariappa following a knee injury.
The Eagles are always a side who are prepared to stir up an upset, just as they did last month when they took Liverpool to the cleaners in a 3-1 slaughtering.
However, times have been hard at Selhurst Park after the visit of the Reds with Neil Warnock's side failing to win since, albeit picking up reasonable points against Spurs and Swansea.
Do YOU want to write for GiveMeSport? Get started today by signing-up and submitting an article HERE: http://gms.to/writeforgms