we had a scroll incident on each server on our platform (playstation)...one where our (DC) scroll got stuck at blue road keep, lasted a couple of weeks...
second where the scroll seemingly bounced around while on the move from AD grabbing it from an EP owned keep (BRK), something happened with the scroll and it ended up back at a keep (KC) the covenant had recently captured...i wasn't with the scroll to see what it looked like in person though...who knows? maybe because the keep (BRK) was no longer owned by the alliance which had planted it there - it went somewhere else, for some reason, while it was on the move...
you can't report the player for that either, it was a bug
I dont' remember the player's name either, but I was there when it happened, and the player was surprised and called it out in zone themselves
acastanza_ESO wrote: »we had a scroll incident on each server on our platform (playstation)...one where our (DC) scroll got stuck at blue road keep, lasted a couple of weeks...
second where the scroll seemingly bounced around while on the move from AD grabbing it from an EP owned keep (BRK), something happened with the scroll and it ended up back at a keep (KC) the covenant had recently captured...i wasn't with the scroll to see what it looked like in person though...who knows? maybe because the keep (BRK) was no longer owned by the alliance which had planted it there - it went somewhere else, for some reason, while it was on the move...
While a scroll is on the move there is a timer. If that timer runs out while the scroll is on the move the scroll tries to return to the keep it was last at. However, if that keep is no longer controlled by the faction that had the scroll there, the scroll will instead attempt to return to a random home keep controlled by that faction that doesn't already have a scroll at it. (If the scroll is dropped during this process and the timer runs out the same thing happens, however, if there is no eligible keep for the scroll to return to it'll just sit there on the ground). Or at least, that's what is supposed to happen, there are probably a bunch of weird edge cases where different behavior could occur.