@ZOS_GideonZOS_Gideon wrote: »Ack, the <<1>> showing up has been fixed internally for a while, but hasn't made it to the live servers yet. We'll be merging it over soon, and once that's done it will show up in an incremental patch.
Incidentally, the text for that error is essentially "An unknown error occurred", and it happens when you get disconnected from the server without an error code -- a 'catch-all' of sorts. As for the <<1>>, it's not actually intended to represent anything graphically, it's a placeholder for "parameter #1".
We're still investigating why the disconnects actually happen, but in the meantime, the UI should at least display correctly.

@ZOS_GideonZOS_Gideon wrote: »Ack, the <<1>> showing up has been fixed internally for a while, but hasn't made it to the live servers yet. We'll be merging it over soon, and once that's done it will show up in an incremental patch.
Incidentally, the text for that error is essentially "An unknown error occurred", and it happens when you get disconnected from the server without an error code -- a 'catch-all' of sorts. As for the <<1>>, it's not actually intended to represent anything graphically, it's a placeholder for "parameter #1".
We're still investigating why the disconnects actually happen, but in the meantime, the UI should at least display correctly.
So basically this is what happened?
ZOS_Gideon wrote: »Ack, the <<1>> showing up has been fixed internally for a while, but hasn't made it to the live servers yet. We'll be merging it over soon, and once that's done it will show up in an incremental patch.
ZOS_Gideon wrote: »Ack, the <<1>> showing up has been fixed internally for a while, but hasn't made it to the live servers yet. We'll be merging it over soon, and once that's done it will show up in an incremental patch.
Incidentally, the text for that error is essentially "An unknown error occurred", and it happens when you get disconnected from the server without an error code -- a 'catch-all' of sorts. As for the <<1>>, it's not actually intended to represent anything graphically, it's a placeholder for "parameter #1".
We're still investigating why the disconnects actually happen, but in the meantime, the UI should at least display correctly.
davidbarryb16_ESO wrote: »Good to know that this issue is known and that a fix is in the works for error <<1>>.
I have been getting this occasionally since 2.0.7, when loading a character from character selection screen, or (rarely) when zoning to a different (and busy) zone. It seems like some sort of timeout - and is an indication of how much the game has slowed down for me recently. (Bigger cities are becoming unmanageably slow - very low frame rates, high latency).
Some guild members that I speak with have this error much more often though.