Maintenance for the week of December 8:
• [COMPLETE] ESO Store and Account System for maintenance – December 10, 9:00AM EST (14:00 UTC) - 12:00PM EST (17:00 UTC)
• [COMPLETE] ESO Store and Account System for maintenance – December 10, 9:00AM EST (14:00 UTC) - 12:00PM EST (17:00 UTC)
[PC/NA] Rollback in the West Weald
Volkster
✭✭
Hello,
Last night I had a strange rollback occur while fighting the World Boss at Lake Olo in The West Weald, at 12:24 AM CT, PC/NA server. I was kicked back to character selection mid fight, and when I logged back in I was placed near the Fall's Glade World Boss, near where the video posted starts. The achievement/item from that boss was deleted as well as discovery of the wayshrine I teleported from in the video. The time rolledback was about 12 minutes. I'm posting it here for raising awareness in hopes that it gets fixed, so something similar doesn't happen to anyone else. Thank you.
https://youtube.com/watch?v=Q0kCl7ooD6Q
Last night I had a strange rollback occur while fighting the World Boss at Lake Olo in The West Weald, at 12:24 AM CT, PC/NA server. I was kicked back to character selection mid fight, and when I logged back in I was placed near the Fall's Glade World Boss, near where the video posted starts. The achievement/item from that boss was deleted as well as discovery of the wayshrine I teleported from in the video. The time rolledback was about 12 minutes. I'm posting it here for raising awareness in hopes that it gets fixed, so something similar doesn't happen to anyone else. Thank you.
https://youtube.com/watch?v=Q0kCl7ooD6Q
2
-
Gabriel_H✭✭✭✭✭
✭Sounds like an extended de-sync issue.PC EU
Never get involved in a land war in Asia - it's one of the classic blunders!1 -
CaiWenji✭✭✭✭@ZOS_Kevin I was there too that night with my account PangTong. It rolled me back too exactly the same. Although I do not have a video I can confirm it was about 12 minutes that was undone. We finished a Direfrost Keep random normal dungeon and the last item I got had 1 hr and 48 minutes left to trade on it after logging back in when getting kicked to character select screen. I recall another player in the zone at the time also saying the server had an aneurysm or something.1 -
Volkster✭✭
It wasn't an issue with my client, as in a de-sync or latency, it was caused by server instability. You can see right in the video my ping and fps are fine throughout. There was at least one other player in zone chat that night asking if anyone else experienced it too. It's the first time I've ever encountered a bug like that in ESO, and I've been playing on and off since beta.Sounds like an extended de-sync issue.
1 -
Gabriel_H✭✭✭✭✭
✭Sounds like an extended de-sync issue.
It wasn't an issue with my client, as in a de-sync or latency, it was caused by server instability. You can see right in the video my ping and fps are fine throughout. There was at least one other player in zone chat that night asking if anyone else experienced it too. It's the first time I've ever encountered a bug like that in ESO, and I've been playing on and off since beta.Sounds like an extended de-sync issue.
De-sync and latency are not the same thing. While the former can cause a spike in the latter they are different, and de-sync doesn't necessarily affect fps.
De-sync can be the result of an issue client-side or server-side (i.e. server instability).PC EU
Never get involved in a land war in Asia - it's one of the classic blunders!0 -
CaiWenji✭✭✭✭Sounds like an extended de-sync issue.
It wasn't an issue with my client, as in a de-sync or latency, it was caused by server instability. You can see right in the video my ping and fps are fine throughout. There was at least one other player in zone chat that night asking if anyone else experienced it too. It's the first time I've ever encountered a bug like that in ESO, and I've been playing on and off since beta.Sounds like an extended de-sync issue.
De-sync and latency are not the same thing. While the former can cause a spike in the latter they are different, and de-sync doesn't necessarily affect fps.
De-sync can be the result of an issue client-side or server-side (i.e. server instability).
Did you even watch the video? A de-sync will NOT allow you to play the game fighting bosses with the boss behaving normally and see other people playing the game fighting bosses moving around doing regular combat for this long. The boss dropping equipment only for it to get repossessed in a roll back is the biggest factor that this was NOT a desync. I am sure the server has to generate the equipment like the Greatsword of Macabre from a dead boss. The client cannot generate loot without the server permitting it.0 -
Gabriel_H✭✭✭✭✭
✭Sounds like an extended de-sync issue.
It wasn't an issue with my client, as in a de-sync or latency, it was caused by server instability. You can see right in the video my ping and fps are fine throughout. There was at least one other player in zone chat that night asking if anyone else experienced it too. It's the first time I've ever encountered a bug like that in ESO, and I've been playing on and off since beta.Sounds like an extended de-sync issue.
De-sync and latency are not the same thing. While the former can cause a spike in the latter they are different, and de-sync doesn't necessarily affect fps.
De-sync can be the result of an issue client-side or server-side (i.e. server instability).
Did you even watch the video? A de-sync will NOT allow you to play the game fighting bosses with the boss behaving normally and see other people playing the game fighting bosses moving around doing regular combat for this long. The boss dropping equipment only for it to get repossessed in a roll back is the biggest factor that this was NOT a desync. I am sure the server has to generate the equipment like the Greatsword of Macabre from a dead boss. The client cannot generate loot without the server permitting it.
Depends on the nature of the de-sync. You yourself called it server instability - that's de-sync.PC EU
Never get involved in a land war in Asia - it's one of the classic blunders!0 -
CaiWenji✭✭✭✭Sounds like an extended de-sync issue.
It wasn't an issue with my client, as in a de-sync or latency, it was caused by server instability. You can see right in the video my ping and fps are fine throughout. There was at least one other player in zone chat that night asking if anyone else experienced it too. It's the first time I've ever encountered a bug like that in ESO, and I've been playing on and off since beta.Sounds like an extended de-sync issue.
De-sync and latency are not the same thing. While the former can cause a spike in the latter they are different, and de-sync doesn't necessarily affect fps.
De-sync can be the result of an issue client-side or server-side (i.e. server instability).
Did you even watch the video? A de-sync will NOT allow you to play the game fighting bosses with the boss behaving normally and see other people playing the game fighting bosses moving around doing regular combat for this long. The boss dropping equipment only for it to get repossessed in a roll back is the biggest factor that this was NOT a desync. I am sure the server has to generate the equipment like the Greatsword of Macabre from a dead boss. The client cannot generate loot without the server permitting it.
Depends on the nature of the de-sync. You yourself called it server instability - that's de-sync.
I didn't call it that. But anyway normally standard de-syncs are usually between 1 individual person and the server. This wasn't a standard de-sync, even if we call it that because the server lost all the progress of 3 people for 12 minutes roughly. What if we would have done a vet tri-fecta trial run in that time?
So, that's why I wanted to contribute to confirm that it happened to at least 3 people and the server simultaneously. It happened to Volkster, me which was PangTong, and some other person that mentioned it in zone chat.
In the video you can see we got a lead and a set weapon that were no longer acquired. I also lost the boss clear achievement. But the loss of the progress alone is not that important, at least for me, but the fact that this can happen and should be addressed because it could have been a lot worse, is why I wanted to comment.
0
