I'm going to let someone else test that out first...
Printable View
Please see my earlier comment on testing and test procedures.
The concept that you intend to fix the only problem (really?) that you know about and then wait for customers to provide further problem reports (we haven't already informed you that more than one general suffers transport time problems???? and even though these comments are telling you that generals other than Anslem suffers the problem!) does not fill me with a great deal of confidence. You already use a test server to do some of your job for you (which I really don't have a problem with, sometimes it is difficult to do all the testing yourself) - I'm sure that users there reported problems with the Observatory and now you are telling us that rather than do your job, you're going to wait for us to do more of it?
I'm getting the impression that BB have abrogated, if not all, then maybe the majority of testing to either the test server or the actual real user base. I am realistic, no software is without bugs, but you are surely aware that if you make your product buggy enough we will start looking elsewhere for our entertainment? The Valentine was obviously too big a change in the timeframe for BB to handle. A (much) delayed, (very) buggy product speaks for itself.
And let's not get into the lack of information on the weather station....... I know players who have just put the building into their menu because they don't know what it does, how it is supposed to help and are just hoping that one day somebody else - obviously not BB - will work out that information for them and post it somewhere.
Overall, the Valentine Event was pretty unimpressive and it's followup seems to be continuing in that vane - I get the impression of a product team that is struggling to keep its head above water and a management team desperately looking to increase gem sales......
I didn't do any co-ops, but I did a bunch of Second Thief, which can be done solo if you want. I like that people had the choice. The problem with weeklies is that is says one adventure from the following list, then proceeds to list only one, which is always something awful. I don't even look at the weeklies. I just wait for them to bug me with the red quest failed warnings and repeat again.
Gwalben - most ppl I know have given up on the weeklies. The cost and "difficulty" (especially in running some adventures) just isn't worth the low XP and the few tokens is the general consensus. It is far cheaper to run some adventures for the equivalent XP and the tokens? well, you need too many to make any difference and besides, as you advance in the game, some buildings become redundant, so you end up replacing them with something else - this applies to pop buildings especially, so why bother? :)
Observatory is still broken, all generals still getting there at the unbuffed times
That's OK, we just have to follow the process BB_Ogden has outlined (implied in his earlier post in this thread):
1. BB make a change - doesn't matter if it addresses the entire problem previously reported or not, just as long as it appears like they are addressing our concerns (my interpretation btw)
2. we test it for them on the live system - because apparently if BB do have a test team, they are snowed under and can't test everything (again, my interpretation of what we are seeing)
3. we inform them it is (still) broken - partial or full (as per BB_Ogden's request)
4. BB disappear to who knows where to contemplate life and any of the other great mysteries..... Including (maybe?) why their "fixes" don't work? Policy obviously being to NOT keep the user base informed.... (again, my interpretation of what we see and therefore, maybe wrong?)
But I really shouldn't be so cynical or critical, after all, I have worked in the software industry for over 35 years and have observed the extremes..... I have seen software teams who use the test teams to find their bugs for them, I have seen management say "why waste money on testing, the user base is captive, let them find it for us" :)
my gift tree looks the same as before maint: http://prntscr.com/n0jbry
hello, I made a simple experiment with my generals;
- activated detailed star chart
- started an adventure
- sent all my generals to the adventure
- as stated by other players before in this treat, my "FULLY SKILLED" COA generals including Anslem not effected by this new buff and traveled as usual in slow pace (both ways to the adventure and from the adventure).
- unskilled generals traveled 75% reduced time both ways (to the adventure and from the adventure)
- now 3 generals surprised me in this test with their different behavior patterns;
a) General MOD only given JOG skill and traveled as usual in slow pace both ways (to the adventure and from the adventure)
b) General Mary Christmas FULLY BOOKED (only difference not having JOG skill) but traveled fast by 75% reduced time as intended to be both ways (to the adventure and from the adventure)
*** the difference between MOD and Mary Christmas is the JOG skill besides all my generals including COAs which are not effected by the Observatory's buff, have the JOG skill, however before blaming the JOG skill see the last one,
c) Quartermaster Claus FULLY BOOKED but not having JOG skill since not on his skill tree, traveled as usual in slow pace both ways (to the adventure and from the adventure)
here is a start point for you for further search, good luck and hope you fix the Observatory or the skill effecting that buff soon.
Hey BB's, how about letting us buy more Demo Crew, Shotfirer and Gem Pit?
Oh. That's why I had scarecrows in my star. I wondered where they came from.
Unskilled generals worked before the fix as well. I cant tell what would be their behaviour if sent separately, but if you send them in group with skilled generals, the "constant rebuilding" bug is still there - they will just land faster and most likely will fall under the endless landing sequence curse (for those who dont know, this effect stops once all sent generals landed on the target island, so adventures are still playable).