onenary wrote:

- I believe before applying any new patch, it should be tested that it won't make any upsets for the game, that's what I would have done if I were a manager over a game. - Number 1 Value for costumers should be Integrity. - Anyway, new players feel free to hit me up in-game, onenary.TS1 from Shu.

The testers wouldn't have seen this coming, as testing isn't done on fresh ducks. The game is over two years old now. Why would they think that they need to run through the tutorial with each new patch?

ivanKaliayev wrote:

onenary wrote: - I believe before applying any new patch, it should be tested that it won't make any upsets for the game, that's what I would have done if I were a manager over a game. - Number 1 Value for costumers should be Integrity. - Anyway, new players feel free to hit me up in-game, onenary.TS1 from Shu.   The testers wouldn't have seen this coming, as testing isn't done on fresh ducks. The game is over two years old now. Why would they think that they need to run through the tutorial with each new patch?

- Now that it happened you have to expect the unexpected.

- For me, it's ok to delay the patch if any problems during the testing is detected.

ivanKaliayev wrote:

onenary wrote: - I believe before applying any new patch, it should be tested that it won't make any upsets for the game, that's what I would have done if I were a manager over a game. - Number 1 Value for costumers should be Integrity. - Anyway, new players feel free to hit me up in-game, onenary.TS1 from Shu.   The testers wouldn't have seen this coming, as testing isn't done on fresh ducks. The game is over two years old now. Why would they think that they need to run through the tutorial with each new patch?

The point of testing (any type like Beta-testing, patch testing,...) is to find problems like these. Testers aren't expected to play the game, they're expected to find bugs, glitches and game breaking exploits in the game.

And this means, in any possible situation: for this game, the tests they do on content patches should also be done on new ducks as well as on other chars

In any case, I bet (and I hope) that Aeria and Koei won't make the same mistake twice and test the future updates on all types of chars

Dalis29 wrote:

The point of testing (any type like Beta-testing, patch testing,...) is to find problems like these. Testers aren't expected to play the game, they're expected to find bugs, glitches and game breaking exploits in the game. And this means, in any possible situation: for this game, the tests they do on content patches should also be done on new ducks as well as on other chars In any case, I bet (and I hope) that Aeria and Koei won't make the same mistake twice and test the future updates on all types of chars

The point of testing a new patch is to pick up on problems with new content. Ducks being unable to independently go into battle is an alpha/beta type problem, and could not be foreseen in a patch coming two years after beta testing ended. Additionally, testing everything imaginable, to a GM, would delay updates even more (would still miss bugs), and it wouldn't be a viable use of Aeria's resources. It is far easier for a community of gamers to find a bug than it is for a handful of GMs to do the same.

p.s. It is better to hope that communication between Aeria and KOEI improves so that fixes arrive sooner whenever bugs arise.

ivanKaliayev wrote:

Dalis29 wrote: The point of testing (any type like Beta-testing, patch testing,...) is to find problems like these. Testers aren't expected to play the game, they're expected to find bugs, glitches and game breaking exploits in the game. And this means, in any possible situation: for this game, the tests they do on content patches should also be done on new ducks as well as on other chars In any case, I bet (and I hope) that Aeria and Koei won't make the same mistake twice and test the future updates on all types of chars   The point of testing a new patch is to pick up on problems with new content. Ducks being unable to independently go into battle is an alpha/beta type problem, and could not be foreseen in a patch coming two years after beta testing ended. Additionally, testing everything imaginable, to a GM, would delay updates even more (would still miss bugs), and it wouldn't be a viable use of Aeria's resources. It is far easier for a community of gamers to find a bug than it is for a handful of GMs to do the same. p.s. It is better to hope that communication between Aeria and KOEI improves so that fixes arrive sooner whenever bugs arise.

Truth.

As for communication, I'm sure it's there but someone on either end is not pressing the issue or they just are like "Ok we found a bug." "Gotcha, we're working on it." followed by "K cool. Thanks." and let it end just there without any type of follow up such as "Hey guys, do we have an ETA on the bug we reported on [insert date here]" But at the same time there are some things that they just flat out can't tell us since we are not employees, such as "Oh the DAU/MAU is low so we're not going to focus on this right now and it'll get done when we have the (resources/budget) to do so."

Sadly, with games that have low player base, the priorities just are not there. It's "it'll get fixed whenever they get around to it." with this type of bug. (a non-game breaker so to speak).
This happened with a game that I was part of the community team for. There was a minor bug but it never got fixed since the DAU/MAU was so low there was no dedicated dev team to put a fix in for it. It would get done whenever a dev [random one at that] had some free time to volunteer to fix it.

I would have to dissagree with you Tyrael. For newbies this IS a game breaking bug.
All they can do is walk around and chat with other players otherwise DWO is unplayable for them untill a fix is implemented.

It's especially frustrating for those of us who want to help out the duckies and discovering we can't. The most we can do is encourage Aeria to ride KOEI about getting a fix as fast as possible. After all a loss of potential player base means a loss of potential income for Aeria. No one is going to buy AP or buy into promotions on a game they can't play.

I'm pretty curious, how does EN DWO run into these types of problems when it seems like JP server doesn't have them, and if JP does, why can't EN get the same patch (or similar) they used?

SilversoulGS wrote:

I'm pretty curious, how does EN DWO run into these types of problems when it seems like JP server doesn't have them, and if JP does, why can't EN get the same patch (or similar) they used?

I think this has been said a lot of times before, but aeria only has a license to publish the game, not modify it significantly, even for that game breaking bug.

They have to communicate with KOEI to get bugs fixed. That and how Tyrael explained it, I'm pretty sure that this game is low on Aeria's priority list.

Think of it like this: You want to make money and you have several products that are doing so. Let's 3: A, B and C. A and B don't make up a lot of your income, but C is taking off like mad. As a business decision, it would be wise to prioritize C, since many people will be using that. Anything to fix C will be done in about a millisecond. A and B however could take about a week or a month to fix, because they aren't as popular than C.

But that's just one thing. Here, we can only blame Tecmo Koei for not sending a bug fix. It's kind of hard to guess what both companies are thinking, since we're dealing with them both. Maybe DWO doesn't bring in a lot of income for TK, so they'll get to it once they can. The same can be literally said for Aeria. They'll communicate when they got spare time. That's quite cynical of me, but seeing as how DWO is doing, it's probably a safe bet tp say they'll get to it eventually.

This is all assuming Tyrael is right and DWO is one of the products that isn't bringing in too much cash as the products aeria provides.