Re: (Nutaku) PeroPero Seduction
I guess I can't then. I'm already upset, so I'm not gonna go further into that. Why only feel sorry for the one with 149? Why not the hundred or more that would have had a chance if things were working properly? That were pretty much shut out of that aspect of the event if they didn't belong to "the club"?
Probably because they were only one away and you can tell they were really trying to get that last one based on their remaining pero. I just feel worse for people who gave it their all and fell just a step short than those who assumed they had no chance and didn't bother trying.
Then again, even if you did bother trying, it was a very tough event to do without having a dedicated group helping each other out like they did on harem battle club.
Was the event unfair? Of course it was considering it wasn't even working as intended. More or less impossible if you didn't save Coli items and a bunch of gold and use ALL of it for the event in addition to having help of strong players.
I have received feedback from the appropriate people. They are working on a fix, they have ran some tests in order to check it, but only time will tell if the fix has been implemented for this event. However, if we do not see that it improves, there is nothing the coding team can do for this particular event.
The biggest issue I can see from this event is that either the players aren't giving a clear enough report of the problem with the event when they send in support tickets, or the communication between Nutaku and the DMM creators isn't getting the actual problem across in their translations. As you can see from Nordland's post, it was eventually confirmed to not be working properly and it took too long for it to be acknowledged for a fix to be implemented in time.
Something similar happened with Angelic Saga as well. We got something unintended, someone asked about it through support and support assumed nothing was wrong and they just happened to have gacha tickets from quests. It was confirmed later that it actually was a major bug that was immediately patched when they confirmed it was indeed a bug.
http://www.ulmf.org/bbs/showthread.php?t=27525&page=31
So the question is whether the problem lies within the user's reports, or trying to get the message to the devs.