The information was literally updated 3 hours ago. That is were they are posting ALL updates on the situation.Originally Posted by LadyCierra
Drop the victim act it won't get you far. You asked for a update the is the most up to date post. I will even copy and paste it for you sense your too busy being a victim to read the latest update when you asked for it and were told exactly were it is.
Originally Posted by Miztah
To clarify a bit, Basilisk was up but still in the process of validating the integrity of most of the database objects. The server is currently running through our backup HDD's, which is causing the server's loading to take a lot longer than it normally would on SSD's. We shut down the login server because any actions triggered on Bas will delay the database check, and it's going to take long enough as it is.
The good news is, the server didn't explode using the recovered database. There's no current bad news, but as of right now, that's the only good news. We still have to verify that all of the objects in the database are actually valid and load properly, and it will take time. The possibility of a wipe still remains if we find too much corrupted data. Time will tell, but in the meantime you'll see Basilisk go online and offline multiple times, but you won't be able to access it. Those still connected will not be able to reconnect when they disconnect, and in the interest of getting this testing done as quickly as possible, they should disconnect on their own anyway.
