We have a large number of people writing in that are encountering patching or permissions issues after the patch, which is pretty common.
We've had more advance warning of the contents of the patch prior to receiving it, so we knew that it would be controversial and would be changing things that a lot of people have been used to.
I should hope that the people who are leaving will come back eventually when things are sorted out, though it's unfortunate if people leave without expressing what they would have wanted to change. As you can see from the recent patches on kRO, there are ongoing patches being made to the skill updates being requested by their community as well-even they have to admit that there are changes necessary.
The focus for getting the skill updates on the main servers was first and foremost knocking out showstopping bugs, conflicts with VIP or other systems and making sure that the servers weren't sideways and on fire on Wednesday morning. With the size of our team we have to work with what we've got.
I'll be updating the drydock thread and putting a "Oda: we're testing this/Oda: can you get screenshots/Oda: this will be fixed next maintenance" on bug report posts.
Feedback given before it is even on Sakray is IGNORED because it is not feedback based on fact, it is based on speculation.
And the feedback on specifics is very poor in general, complaints of general I feel underpowered or I want this skill to be stronger isn't nearly as helpful as:
Arrow Storm has a long cast time, a small AOE, and poor damage, increasing damage so that it is double that of Double Strafe applied to an area could be a better solution.
I agree that there are very specific feedbacsk that some have given which fits the criteria for us to move on with requesting the changes. This was a problem last year, as 1 person trying to collect data that is not well presented is a monumental task especially when some players don't post factual information. There have in fact been many posts with players posting downright lies about what a skill effect currently is, and then others have to correct them. That sort of "noise" is not only aggitating to us but it aslo stirs up more problems in the community.
Heim and Oda,
I understand why, from a budgeting and marketing standpoint, your priority was to get this patch implemented before the start of the new year. That said, while the new patch has some functionality and didn't crash the live servers,
it was not ready for release. And while having to delay a release when multiple deadlines have already come and gone is never a desired outcome, it is sometimes unavoidable in order to ensure quality--and ultimately 'delay' is the lesser of the two evils (inferior product vs delayed product) when catering to customers. To use an analogy, it's the student's dilemma when up against a due date: submit an inferior assignment below the professor's expectations, or request a time extension so that although late, the professor is provided with something worthy of his or her evaluation. Two options, but the former leaves your professor questioning your competency.
And, yes, there has been a lot of "noise." Just don't be too quick to dismiss customer feedback as "lies." Your perceptions and expectations will rarely match up with others. The concept of Truth is subjective. Please remember that.
All feedback communicates something--whether it's a rash of players threatening to quit or general discontent and flaming/trolling. You might ask yourselves how on earth is rampant customer dissatisfaction at all helpful to you?
It isn't--However, the fact that you have the option of seeing
why your customers are dissatisfied is a strategic advantage if you choose to harness it and make it useful! You can use this free information to guide your decisions on how best to maintain your customer base. Even if you can't delight the majority of your customers, you can at least work towards reassuring and placating them. Otherwise you have customers out the door.
We've been reading the threads, using them to test and collecting information-if you'd like I can put a blanket "yes we are looking at this" response to every post on the 14.1 testing subforum because that's what we're doing.
We're trying to decide between a forum type feedback or something like a survey for each WP account, probably be the latter. I do know they want to wait until 14.1 is put on the mains to see how much the new equipment help, then tweak from there.
Here's a suggestion: Make a sticky post that that has a running list of reported bugs and whether they're confirmed, fixed, or require more investigation:
- Bug Description
- Date Reported
- Priority Level [Optional--but good to have]
- Confirmed, Investigating, or Fixed
- Work-around / Solution [If applicable]
.
.
.
I may not be the happiest of customers right now, but I hope you can benefit from this criticism. This is my feedback--take it or leave it.