While I doubt the value of posting the same snarky line in a half-dozen or so different threads, the point about lack of communication is a valid one. It's a repeat of what we saw in beta, where the developer would seemingly disappear for a week to ten days, maybe even two weeks without a word.
I've said it before, and I'll say it again - the 3.0 engine is a huge improvement over the 2.0 engine. But it's not done, was not ready to push to public release, and still is not ready. The only positives to pushing it out to the paying worlds is that there is a broader number of vocal participants (the number of people providing feedback in the beta forums had dwindled to half a dozen or so) and that WIS had given out free seasons, something they SHOULD be doing at the start of every college football (and basketball) season. Doubtless most of those "freebies" wouldn't be renewing anyway, but I suspect the retention rate this time will be much smaller than usual, because they were given a free play of a flawed still-in-development product. (And I'm not referring to ongoing tweaks and minor bug squashes that SHOULD be going on all the time, I mean major factors, some of which remain unimplemented.)
Some of the issues are minor - almost all of the play-by-play related ones, I consider to be a minor nuisance at best. But the larger concerns are flawed penalty acceptance logic, flawed timeout logic, lack of missed PAT and pick-6, effects of stamina / fatigue are concerning. I dread the implementation of injuries, because my teams are now in the playoffs - and the last thing I need is a sudden burst of season-ending injuries because previously unimplemented variable is slightly off.
As much as some mock the "I'm working on it" responses, I'd rather have those than nothing at all.
11/19/2013 8:25 AM (edited)