The Elder Scrolls Online

Maintenance for the week of February 23:
· [COMPLETE] NA megaservers for maintenance – February 23, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] EU megaservers for maintenance – February 23, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
· [COMPLETE] ESO Store and Account System for maintenance – February 23, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)

9 March 2020, no patch ?!?

Leave a Reply
Sarousse
Sarousse
✭✭✭✭✭
✭
Nothing to fix all this lag/desync/skill not responding mess ?

Really ?

Edit : I've just seen the post in the Maintenance announcement section. Guess we'll wait then.
Edited by Sarousse on March 8, 2020 9:16AM
  • relentless_turnip
    relentless_turnip
    ✭✭✭✭✭
    ✭✭✭
    Sarousse wrote: »
    Nothing to fix all this lag/desync/skill not responding mess ?

    Really ?

    They have said in the maintenance section that they think the patch they had for Monday will cause a new problem in combat... But feel it's totally good to roll the patch out to console without delay 😂
  • Banana
    Banana
    ✭✭✭✭✭
    ✭✭✭✭✭
    Fingers crossed people.
  • Nemesis7884
    Nemesis7884
    ✭✭✭✭✭
    ✭✭✭✭✭
    since every new patch seems to bring more and new issues its probably a good thing they go back to the drawing board for a while

    Edited by Nemesis7884 on March 8, 2020 10:15AM
  • Aznarb
    Aznarb
    ✭✭✭✭✭
    ✭
    Atm I've just totally stop to weave/anim-cut on my healer, if I do it most of my skill and LA don't work..
    My last vSS with MK I had an atrocious uptime..
    Hope they fix this.
    [ PC EU ]

    [ Khuram-dar ]
    [ Khajiit ]
    [ Templar - Healer ]
    [Crazy Gatherer & Compulsive Thief]

  • redgreensunset
    redgreensunset
    ✭✭✭✭✭
    ✭
    Gina made a post about why they won't. May I suggest people at least attempt to use the dev tracker before screaming about lack of communication?
  • MJallday
    MJallday
    ✭✭✭✭✭
    ✭
    Sarousse wrote: »
    Nothing to fix all this lag/desync/skill not responding mess ?

    Really ?

    Edit : I've just seen the post in the Maintenance announcement section. Guess we'll wait then.

    My take is that this isn’t something that’s going to be fixed in 30 seconds

    There are more fundamental issues with the code - and it’ll will take time to diagnose, resolve, test and deploy

    Be patient (which i appreciate is frustrating) but at least it’s been acknowledged
Sign In or Register to comment.