Slitherine

Currently playing on Game Center. We were on the 22nd when we received an unexpected Dusk at around Noon. I can't recall the exact time, but I know we had plenty of time left and neither of us passed. This happened following the German move.

Thanks for letting us know, if you still have that game could please submit a Bug Report so we can take a closer look?

Thanks!

mpnagel wrote:Currently playing on Game Center. We were on the 22nd when we received an unexpected Dusk at around Noon. I can't recall the exact time, but I know we had plenty of time left and neither of us passed. This happened following the German move.

I posted another instance (and screenshot) of this issue in another topic on this forum, before I saw this tech support section:

http://www.shenandoah-studio.com/Forum/ ... 1623#p1623

Unfortunately, the game was deleted before I read about the method for reporting a bug. If I encounter it again, I will use the bug reporting tool.

Thanks.

I'm experiencing early dusk or other clock issues at least once in actually every game I'm playing since the update.
Dusk coming around 1630-1730. The time "lost" one day seems to be deducted the next. The worst case was when the whole of the nineteenth was played over again once, the clock just reset one day, and then on the twentieth at 1630 every turn after that lasted from 1630 to 1730 until we passed twice.

I sent in a bug report the two first time, but got tired of it, especially since I didn't hear anything after that.

For me the bugs seriously is killing the joy of playing BotB, since in every game I'm playing there is at least one minor or major game turning incident caused by bugs. Have you concidered a rollback to v1.0?

Btw: we now call the time between 1630-1730 the groundhog hour...

Jarling wrote:I sent in a bug report the two first time, but got tired of it, especially since I didn't hear anything after that.

Did you not get an acknowledgement email?

I got the acknowledge mails, But the status never changed so i didn't care to send in more. Which anyway is much the same bug.

The status can’t change until the bug gets fixed, and this one was very hard to reproduce (despite the fact that it clearly can happen more than once).

We really do appreciate bug reports, and try to make sure that they don’t get ignored, even if we can’t always reply personally to each one.

Understood. But is it helpfull to send in every time even if it apparently the same bug? (i guess I already know the answer to this one)

Jarling wrote:is it helpfull to send in every time even if it apparently the same bug? (i guess I already know the answer to this one)

Right: sometimes.

When in doubt, do — it may not give us new information, but at the very least it indicates how often something occurs.

It’s definitely helpful to get reports of the same thing from different people.

At the moment, we think we finally understand all the different ways this issue can happen, and are testing a fix.

I have encountered this error many times as well, and finally was able to send in a report after learning how.

Interestingly, I've never encountered it when playing the AI, so it must be some kind of GameCenter related issue.

Here is a link to my post about submitting the bug report: http://www.shenandoah-studio.com/Forum/ ... t=20#p1641

Thanks.

wargamer11 wrote:I have encountered this error many times as well, and finally was able to send in a report after learning how.

Interestingly, I've never encountered it when playing the AI, so it must be some kind of GameCenter related issue.

Thanks for filing from the game!

Actually, probably a Review issue. But Game Center play makes extensive use of Review so you can see what the remote player did. So it can be hard to distinguish the root cause.