Results 1 to 1 of 1
  1. #1
    Player ceown's Avatar
    Join Date
    Mar 2011
    Posts
    6
    Character
    Ceokitty
    World
    Phoenix
    Main Class
    WHM Lv 99

    Another unwanted character rollback

    Platform: Windows
    ISP: Shaw
    Type of Internet Connection:
    Cable
    Internet Connection Speed: 100Mbit
    Date & Time: Between 22:00 Mountain (0:00 EST) and 7:00 Mountain.
    Frequency: Once
    Character Name: Ceokitty
    Race: Mithra
    World: Phoenix

    GM has noted my case in game with the items lost and is escalating my case. However it was suggested to post in here as well.

    My character has been reset to roughly the same time period of April 28th much like others. Login screen showed me as WHM\BLM in my mog garden and when logged in appeared in the Nyzul staging area as THF\DNC. This is notable as I've turned in a great deal of Alexadrite and had started working on my relic sheild in this time period. Having to reaquire those materials is a time intensive issue.

    I'd like the restore to look at my last known good logout data of 22:00 Mountain (0:00 EST) on May 9th.

    Edit: Just proposed a theory to a GM that seems to fit what happened and it was suggested I update this post.

    After some much scurtinizing of my player data and some discussions with people who had been reverted to 2 week old data, then restored, I stumbled across a theory.

    The theory goes as such:
    Approximately 2-3 weeks ago Phoenix suffered a server crash that handled all the escha zones. This is what I suspect is the lynchpin to the entire thing. Most of the players impacted in this were fine, but a select few triggered a bunch of weird code that caused a revert to two week old data two weeks later. Unknown as to what that trigger is yet.

    What I speculate that happened is someone did a quick check to see who was in zone at crash time, or some other flag they knew of, and while i didn't trigger the 2 week revert, I was lumped in with this group of players which then had a mass restore to their last known good dataset. This means while I did have legitimate data loss, it's limited to a 2-5 day window rather than 2-3 weeks as thought as i was accidentally restored when they tried to fix things.
    (1)
    Last edited by ceown; 05-13-2016 at 06:34 AM. Reason: Formatting, new data\theory

Tags for this Thread