All Worlds Emergency Maintenance (Jul. 9/ Jul. 11/ Jul. 12)Follow

Maybe its a ploy to get us to go play XIV beta.

Lol, that's what I'm doing

So does anyone know what battlefields were dropping what items? It's not like we can take advantage of it now anyway.

One person's speculation is that they have no way to mass delete the unintended items, so they have to hunt through the logs to find them all. I don't know that there is any basis to that claim, but it wouldn't surprise me. I desperately hope it's not the case.

It's possible that they're having to go back and nuke/modify the Delve MB drops (assuming that's actually what they are) out of players' inventories, since they aren't supposed to exist yet if that's the case.

This is coming into the realm of possibility, I left for work this morning before the daily reset at 8 AM (Pacific), and by the time I got home, maintenance had already started. If this maintenance goes on a few hours more, I won't be awake for the end of it...

I'll be a bit annoyed if I have to wake up at 7 AM on a Saturday just to log in for this event... >_>

My hypothesis is probably the new Wildskeeper reives were probably dropping things from future delve/skirmish expansions, rune/geo af gear on the limmit breaks, or other things that may currently be only available on the test servers were being randomly dropped sporadically in various battle fields. Like real randomly across in reive battles, delve, skirmish, limit breaks, bc, zenni, nyzule, salvage... The question I have is, what items were they and howmany people actually noticed? Then again, some folks may need to go through the recent data files with a comb to have an idea as to what it could be.

Edited, Jul 13th 2013 12:07am by akudama

From: http://www.playonline.com/home/polnews/news22411.shtml

Translated (via google):

I will inform you of the situation for emergency maintenance work which is being performed currently. A result of the investigation, in Battlefield in the "rock peaks Horure", failure has occurred to the setting of the drop items, in addition to (appear under the name "..." ※) unimplemented items, then drop in the normal We check the status of items never is dropping. In addition, we confirm that the problem has not occurred in the area and other Battlefield other than "rock peaks Horure". For this reason, for the area other than "rock peaks Horure", will end the maintenance work around 13:00. For "rock peaks Horure", preparation of bug fixes to complete continue, we will continue to maintenance work. End time concrete, will be announced as soon as determined. I deeply apologize that we are apologize for any inconvenience to customers. 　　　　　　　　　　　　　Symbol to 13:00 time from Saturday, 4:30 July 13, 2013: Date and time 　　　　to be determined end time only "rock peaks Horure" ※ 　　　　　will continue the maintenance work.

The game is back up.

Horlais Peak, really?

They had to take the whole game down for hours with virtually no warning because of "."s being dropped in some irrelevant zone? Man, that would have been a disaster. Imagine if it hit the press...

Yep you definitely are, since you know you wouldn't say sh*t or care if it came up in your primetime.



I know right? Because that's the only thing they did while the servers were off. Makes total sense, it's not like they could have done something else. Sheesh, some people.

Edited, Jul 13th 2013 7:50am by Theonehio

Looking over the maintenance history, I'll give you my best guess.

It's the "Fish Anywhere" hack in a new form. Ages and ages ago, there was a bug where you could fish anywhere, and pull up random items because you were basically skimming the database on the servers for items they have on there. Sounds like when they added the new stuff, they have create a situation where some events are accidentally pulling from these tables of either default/blank items (like the infamous "." placeholder), or even grabbing stuff not implemented like Gold Beds mentioned in that posting. Likely they were having to create a new table for the new loot but somehow some of the indexing values got snarled with older tables. But they didn't know what table was snarled with which because of their insistence on the "." placeholder.

Edited, Jul 13th 2013 11:27am by Pawkeshup