Eh...
So designing something to work differently than the intention is not a wrong design?
You have to be alone on that one.
Heck, I even remember back in the days when I learned software design that ANYTHING that wasn't part of the design document was a bug, even beneficial stuff.
So having your design end up not fulfilling the design intentions is the very definition of a wrong design.
So either the design intentions were not what we were led to believe, or they have issues with designing software.
Neither scenario looks good to me when we are considering a multimillion dollar software project.
Sounds like a very rigid 20th Century, waterfall development model to me.
In an undertaking this huge, with feature creep steered somewhat by the community, you can't develop in that manner. In my experience with business software, requirements get added (in this case a lot of them), some become unfeasible, get reevaluated and retracted.
This is a game. Not business software. The decision has been made by the developer, move on. It's clear that Offline single player isn't going to happen. So some people are disappointed- I think we all understand why, and you have a point. You have a choice to stick with the software despite this, or apply for a refund if it really doesn't match up to your expectations.
(And once you've made your point, I expect we'll see 99% of refundees on the forums under a different name when you've re-bought your release-day retail copies.....)