Thread: Sooooo...late May for 2.28?

So it was a week long blackout then!?


........suuuuuure


(¬_¬)

I'll quote myself from a different topic to answer this question.

Edit:

...in terms of specifics, he said that they're experiencing company-wide network issues, which have also hindered their ability to address bugs for the patch (it's cost them about three days of work). Furthermore, the building is being shut down for a yearly maintenance on May 31st and June 1st (saturday and sunday). If they released the patch on that friday, they would have no way of addressing issues if something went wrong that weekend, so they had to push it back to the following week.

Source: The live letter 29:30-31:00 (I understand Japanese)

June 5th would make more sense over-all due to E3 usually kicking off June 6th for preps and shows, this means the update will be released so they can talk about it further at E3 and bring new content to the table without having to worry about further restrictions to speaking about content, it also makes more sense due to their power outage issue which took place not long ago aswell as most updates have been on a thursday to free up the heavy load for weekend play.

Please Look Forward to it.

Originally Posted by Spellbinder

I'll quote myself from a different topic to answer this question.

Edit:...in terms of specifics, he said that they're experiencing company-wide network issues, which have also hindered their ability to address bugs for the patch (it's cost them about three days of work). Furthermore, the building is being shut down for a yearly maintenance on May 31st and June 1st (saturday and sunday). If they released the patch on that friday, they would have no way of addressing issues if something went wrong that weekend, so they had to push it back to the following week.

Source: The live letter 29:30-31:00 (I understand Japanese)

Thank Chenn, nice one. Still it was for bugs as we should be expecting.

So in 2 weeks, I will put my 90000 full-proof Set, with high Morale

We have both Patch 2.28 and I think 2.3 is still coming in late June/early July.

I wish they were more upfront about delays and not being able to meet deadlines instead of giving vague release dates and then announcing delays on the very last second, they obviously knew well in advance about building maintenance on the last week of May so the late May date was always sketchy, it just comes off as insincere and as an excuse instead of a legitimate delay. A simple "Sorry it looks like we won't be able to meet our deadline, we apologize for the inconvenience" a month in advance would be fine, I mean it would still be somewhat disappointing but it's an announcement given with plenty of time. They've done this way too many times before, biggest example is how CT was promoted for over a year as being included at launch and then it was announced it would be taken out only around the last beta phase. Yes, development changes, armchair dev, entitlement, etc. you can save those responses I just posted them for you.

My point being I do not see how SE finds it acceptable for an unofficial translation to be the only form of communication about the delay for a million plus subscribers. The Q&A translation posts were great, it just seems like a fairly big thing to leave out.

Originally Posted by DukeBurden

Lolz. If they said in the live letter it wasn't till June 6th, how is that NOT an official word? Way to get offended for no reason, you "english speaking player."

If it wasn't for the fan translation, the english speaking player base never would have known it was on the 4th/5th/6th/whatever. So yeah, they did leave us in the dark and the OP has good reason to be offended. Derp.

Originally Posted by Seif

So it was a week long blackout then!?


........suuuuuure


(¬_¬)

Ever work any place where phone lines are part of a business? Ever get a power surge/outage in place like that? I work at hotel, we had a power surge and our phones were down for five days. Think of the possibilities of what it could do to a computer.. or a dev that may have forgotten to save a bit of programming before it happened.

It's not entirely impossible.