PS4 - Error CE-30022-7 / Unable to download patch files [20512][25008][20525] Error
This is the 3rd day after the patch and I am still unable to finish patching. I get to the same point just about every time. 625-627mb of 3715mb and the screen goes black and then comes back with the error I listed in the subject.
This is not a new error from what I have been reading and occurs quite often after a new patch. I have tried patching at different times of the day and still same results, so probably not a load issue.
Need some assistance here, because I feel like I am banging my head against a brick wall and the wall is winning.
Static
PS4 - Error CE-30022-7 / Unable to download patch files [20512][25008][20525] Error
So, it's been 6 days.
Patch 3.2 is totally ruined for us, we missed on our chance to enjoy the story with our friends and community, we missed our chance to enjoy battle content and learn them with our friends from scratch, we missed our chance to make Gil from impulse buyers in Marketboard, we have been spoiled on everything, we have lost all dailies and weeklies, and we been robbed of 6 days of our hard earned money of our subscription, AND our ISP bills that will be through the roofs for those of us with data caps.
I could forgive all these. I really could.
But Square-Enix has not even acknowledged the issue, has not replied to the numerous topics here with what happened with that error [CE-300022-7] and even then, I took the advice of fellow players, killed my data cap for the month, deleted the entire 40 GBs of data from my PS4, and redownloaded it.
Then I logged in and started to download the patches.
Going to work all day, when I returned......
"Unable to download patch files [20512][25008][20525]"
I'm sorry, but I want to know how I can get an immediate refund of my current six month subscription + six month of 6 extra retainers to FINAL FANTASY XIV worth of 116.40 Euros that I bought last week, basically where I can get a live rep to talk through it right now.
Unless Square Enix issues an official response immediately, promises to fix the issues by tomorrow, and extends our subscriptions the whole week of downtime.
Not that this would make things right, as 3.2 is 100% ruined for us.