Level 6301

bearwithme

Hello @miish and welcome to our wonderful King Community. Yes there is a fix and the comments about this issue were combined in the thread below. Please check it out.

https://community.king.com/en/candy-crush-saga/discussion/278307/level-6301

Once you update your game to the latest version, you should be able to play the level OK.

Werner_Cichy

@miish,

Welcome in the King Community !

I'm not sure i understand you correctly

You probably always get the ooops in level 6301. I had that too. However, if you have the lucky candy at the start, the level works.

This Candy

bearwithme

Hello @Werner_Cichy - they shouldn't need to play the level starting with a lucky candy. There was a glitch with the level but it has since been fixed by the studio.

Werner_Cichy

@bearwithme I just tried again on facebook, 5 attempts without the start booster, every time oops, 5 attempts with the start booster and it worked. It has not been fixed yet.

bearwithme

Hello again @Werner_Cichy - the studio fixed this level and other players can now play the level fine. You need to make sure you have updated your game's software - Version 1.165-1.169 include the fix for this level.

Werner_Cichy

@bearwithme That's right, the Win 10 app is up to date, and that's where it's fixed. But on Facebook, with the current Opera browser, I still have the error. It may not be updated until the next update

bearwithme

OK - thanks for letting me know @Werner_Cichy I’ll pass it on.

eugene

get the oops message - playing on FB - windows 7 - chrome.

I see where you need the latest version but it just happens on a desktop - please fix

it did let me play with the ck booster but still didn't give me enough

Jan_Bevins

cleared cache and cookies. lost all my lives people sent me and the format looks different but it still says Oooops not enough targets and I haven't even played yet. Now don't have lives to check if it's working or not

Ivan1966

I've read a lot of errors on level 6301 as it breaks up constantly. I've even read that it was solved. I can confirm that this is NOT THE case! Please solve asap!!