Well, for the record I am a computer programmer and systems engineer. And not to put too fine a point on it, but if you think it's so easy, then perhaps you'd like to show us your proposed software architecture document. Otherwise, you might want to reconsider aggressively expressing an opinion on a matter that you admit that you have no knowledge of or experience with.
I will adjust my opinion if there are worthwhile arguments to alter it.
Why should Bioware want to copy from an eight year old game architecture? An enormous amount changes in computer technology in eight years. Certainly NWN was a great game in many ways, and especially for its time. But any company that wants to be in business next year has to grow and change their products to keep up with current technology and maturing customer (player) expectations.
What im saying is that they do not need to reinvent the wheel.
And yeah current technology has progressed. This just makes my case stronger.
And one of those realities is that players don't generally come to the same game for both MP and SP experiences.
start counting the number in this forum alone....
It's really hard to make a game that does both well, and I don't see any particularly good reason to, either. NWN came about as close as any game could, and as much as I love it it's shot through with design issues that complicate and compromise the SP playing and building experience.
""NWN came as close as any game could""..utter bull****. SP campaign was very bad. And not purely due to conflicting MP/SP.
Also with such an attitude you never improve.
Its been many years..but lets never attempt it cause NWN did it as best as we ever could. Forget about technology improving or possibly more time and money for development. Forget that we do not have to reinvent the wheel.
Bioware obviously decided to focus on providing a better SP experience with their next game, and the price was MP support
You have to do different things if you want to design a good boat, or a good sports car. The same thing applies to software architecture. If you try to design a Ferrari that floats, you're not going to end up with a particularly good sports car. That ought to be just common sense, even if you're not a software engineer.
yeah i know it will come in part at the expense of other things. Never said it didnt.
My issue here is how much.
first its ""Not NEARLY as good"" which is what i was skeptic about.
And still am seeing you just keep repeating your same routine.
1. Telling your a ""programmer"" and ""engineer""!
2. Telling there are ""design issues"" and ""constraints""...can you be more vague in an argumentation?
3. Bringing up the ferrari analogy.I'm skeptic about how much would MP hinder SP, not IF it hinders it...so its a bit useless.
4. ""cut scenes"" as your example for 2. Which is a non-issue for me.
When I ask for more examples or more info, you just repeat the routine. Great job.
Your posts are riddled with huge bold statements such as ""NWN came as close as any game could"" and ""It will not NEARLY be as good""
What are your arguments?? Do you even really have any??
Basically your saying your a ""programmer"" and you feel there are ""design issues"" and I should just take your word for it seeing how i am not a ""programmer""???
it should be common sense that you understand why this is a **** way to argument your case.
And why you are not taking away my skepticism.