By using this site, you agree to our Privacy Policy and our Terms of Use. Close
scottie said:
curl-6 said:
scottie said:
curl-6 said:
scottie said:
Putting an exact date means that if the game needs even an extra day's work, you have to announce a delay and piss your fans off. This encourages devs to rush their game to avoid having to announce a delay, which leads to worse games.

Have patience, it is coming.

Patience is one thing, but the current drought just isn't acceptable, gamers shouldn't have to put up with this kind of treatment. Nintendo have had TWO YEARS of neglecting the Wii to work on Wii U games; being new to HD graphics and programmable pixel/vertex shaders just isn't a good enough excuse for having  nothing to show after a two year plus drought. I can only hope their current abysmal sales teach them a lesson, that they can't treat us like this and get away with it.

At least give us a month's window for Christ's sake; April for Pikimin, July for Wonderful 101, (So they can waste time at E3 wanking on about that old, well known, unexciting game instead of showing actual new ones) or something like that.


I was meaning patience related to knowing release dates, not patience related to the games coming out. The current lack of releases has absolutely nothing to do with Nintendo's policy on announcing release dates, so I shall not discuss it in this thread.

 

As for Month, that has exactly the same problem I originally pointed out. If you say it will release in April, then your bug finders say "We need some more time to work out the bug that is making the game shit to play, we can't have it done until May 2nd" What do you do? Release a buggy game? Announce a delay? Isn't it better to stay vague about release dates until you are sure?

Just factor bug testing time into your release schedule.


Never coded before, I take it?

Many other companies don't have such problems delivering a quality piece of software on time.