We need a "math enclosed" sub-forum where you people can take your horrible number-thingies.....
I had a couple days last week where I was pretty much beyond too tired to really play, so that set me back by a mile...I had dismantled by Orc city and built a mini-city for fellowship adventures, so finished it Saturday just after the tournament ended. 54.5 hours.
I will say that this event's main quest line has been *MUCH* more enjoyable than the last clusterfeth of a seasonal event, so really good job there Inno!
Even smaller cities should be able to chug through the entire questline in time, which is exactly how events should go.
Now granted, if you went & grabbed the questline from Beta as soon they got it up & running, and then began prepping your city to crush the event as efficiently as possible, you could easily complete everything within a week or so. (or sooner!)
Me? I'm just the idiot who read "Thursday" and translated it to obviously mean "Tuesday", so I was already cruising through quest #30-something within a few hours!
However, I really prefer the ability to race through the quests as fast as possible, as it means I have plenty of event currency to go after the rewards I really, really want!
(and yes, I know Inno hates this because it means no $$$ for them...), but then, I don't spend on events anyways, so not having insanely unfair questlines like the summer event just means that I'll 100% be back for the winter event, instead of just ignoring it.
They display the notification screen late. I called it a bug the first time it happened and someone, whom I won't name, suggested it might be intentional instead of a bug. I still say it is a bug.EDIT: apparently I missed the screen with the double sprouts!
I'm not afraid to be named. It might be a bug, it might not, It might be intentional, it might be someone screwing up, but I I still say the time a notification appears does not appear to meet the definition of bug, since it probably has nothing to do with code.They display the notification screen late. I called it a bug the first time it happened and someone, whom I won't name, suggested it might be intentional instead of a bug. I still say it is a bug.
Computers do not do anything unless the programming instructs them to do it. It is coded that way. Either intentionally or unintentionally, and any sort of unintentional result from a set of instructions is considered a bug.since it probably has nothing to do with code.