Equipment unattuned by patch gets re-attuned on it's own

[Whailor]

<p>As the subject tells. After the patch I had many items unattuned in my personal bank. However after logging out on this char and later logging back in seems to have "automagically" re-attuned every single piece of equipment what the patch unattuned. Doesn't seem to affect the items in shared bank or in inventory, yet anyway, but every single item in personal bank is back to being attuned, without me even touching them.</p><p>EDIT: small update - seems that several items which were unattuned and in the inventory of the char got "automagically" re-attuned after logging out and back in...</p>

[Wingrider01]

<p><cite>Whailor wrote:</cite></p><blockquote><p>As the subject tells. After the patch I had many items unattuned in my personal bank. However after logging out on this char and later logging back in seems to have "automagically" re-attuned every single piece of equipment what the patch unattuned. Doesn't seem to affect the items in shared bank or in inventory, yet anyway, but every single item in personal bank is back to being attuned, without me even touching them.</p><p>EDIT: small update - seems that several items which were unattuned and in the inventory of the char got "automagically" re-attuned after logging out and back in...</p></blockquote><p>supposed to be fixed in this mornings patch, aa being reset again, adornments being popped on worn equipment, etc</p>

[Whailor]

<p>Well, it did not fix it! Earlier today I logged in to see the results of this so-called "hotfix". Indeed, attunable items were unattuned, all of the AA reset again, like before. Just had a quick look since I had some errands to run, so logged out right away and came back several hours later. Logged in, checked the char bank and inventory and guess what? ALL ITEMS ARE RE-ATTUNED. Again. On their own. What's up with this, can it be finally fixed? Items keep re-attuning themselves after relogging. Great "fixing of problems" there.</p>

[TSR-JoshuaM]

<p>Our support teams are aware of the issue and working towards resolving any situation where this may occur since the 8/27 hotfix.</p>