Hi i wonder if anyone can help, for some reason i had been blocked from playing Fairyland for a week ?  I wasn't given a reason why , Could it be because while playing the game quickly to spot my birds to get the bonus points  i seem to have been penalised . The question is will this happen again and if it does how can we play quickly from garden to garden for the bonus points when starting a new game ?.......Or was it Facebook i can't seem to get an answer .

It all depends on what error message you were getting.
I doubt you were blocked form the game as people that get banned have no way of coming back unless Mike pardons them (for lack of a better word lol).

i asked for a friend who was unable to get in. will add the reply i got here as it could be the same reason.

'This appears to be a Facebook issue which is affecting a few games and a few players at the moment (although not everyone)

Some players have reported that the issue was temporary and they could get in again after a while.

Some players have reported that they could get in ok when going via our website at https://www.fairylandgame.com rather than through the Facebook link, so you could also try that.

Other than that (and also trying different browsers, in case it helps), it's unfortunately just a case of waiting until the issue is resolved.

Regards,

Fairyland Support'

Thankyou for your lovely replies ladies much appreciated, but i think ill now refrain from trying to get the bonus points when starting a new game if this blocking is going to happen.

There were other games affected and the issue has  now been resolved. It was a strange thing because it seemed to only be at certain times of the day. It was a FB issue and they never seem to explain or apologise which leaves players confused.

A friend of mine was blocked by fb because when people liked and commented on his amazing insect photos and he answered them was blocked for spamming , he can only ' like ' there comments. Fb is very strange.

Ain't that the truth, Jayne!

But at least it's fixed now.