Motifs do not register as known/read

Carbonised · January 2018

I haven't seen this mentioned anywhere here, but there is a bug with the CWC motifs (apostle & ebonshadow) and Reach dungeon motif Dreadhorn but NOT Bloodforge, that even when you read a page from the motif, that page does not show as "known" when you find other similar pages, or in guild stores.
It also does not register in your Eidetic memory section, though it does register for the achievement.
It means that when you use addons such as awesome guildstore to do a filter of "unknown" motifs in a guild store, these ones still show up, and on one occasion I bought a duplicate motif, because I thought I did not know it, as it didn't show as "known".

This happens only for the 3 new motifs, the Dreadhorn Reach ones and the 2 CWC ones, but NOT the Bloodforge one for some reason. It appears to me that there is merely a flag/property that is not set correctly on these 3 motifs, to make them shown as known, and to register them in the eidetic memory section as well.

PC EU

rachelle.arringtonb14_ESO · January 2018

This is happening for me, but only for Ebonshadow motif.

Carbonised · January 2018

rachelle.arringtonb14_ESO wrote: »

This is happening for me, but only for Ebonshadow motif.

Are you sure it doesnt happen with apostle too? What server btw?

Apache_Kid · January 2018

Was happening for Apostle and Ebonshadow motifs for me a few weeks ago on Xbox NA but it has since been fixed and all mine are now showing up in the lore library. So hopefully it'll be fixed on your platform soon as well.

rachelle.arringtonb14_ESO · January 2018

PC NA, and Apostle is fine.

Carbonised · January 2018

Different server. Might be affecting different amount of motifs on different servers then.

patrick_smyth · January 2018

Carbonised wrote: »

I haven't seen this mentioned anywhere here, but there is a bug with the CWC motifs (apostle & ebonshadow) and Reach dungeon motif Dreadhorn but NOT Bloodforge, that even when you read a page from the motif, that page does not show as "known" when you find other similar pages, or in guild stores.
It also does not register in your Eidetic memory section, though it does register for the achievement.
It means that when you use addons such as awesome guildstore to do a filter of "unknown" motifs in a guild store, these ones still show up, and on one occasion I bought a duplicate motif, because I thought I did not know it, as it didn't show as "known".

This happens only for the 3 new motifs, the Dreadhorn Reach ones and the 2 CWC ones, but NOT the Bloodforge one for some reason. It appears to me that there is merely a flag/property that is not set correctly on these 3 motifs, to make them shown as known, and to register them in the eidetic memory section as well.

PC EU

How much longer do we have to wait for a fix, ZOS?

Apache_Kid · January 2018

patrick_smyth wrote: »

Carbonised wrote: »

I haven't seen this mentioned anywhere here, but there is a bug with the CWC motifs (apostle & ebonshadow) and Reach dungeon motif Dreadhorn but NOT Bloodforge, that even when you read a page from the motif, that page does not show as "known" when you find other similar pages, or in guild stores.
It also does not register in your Eidetic memory section, though it does register for the achievement.
It means that when you use addons such as awesome guildstore to do a filter of "unknown" motifs in a guild store, these ones still show up, and on one occasion I bought a duplicate motif, because I thought I did not know it, as it didn't show as "known".

This happens only for the 3 new motifs, the Dreadhorn Reach ones and the 2 CWC ones, but NOT the Bloodforge one for some reason. It appears to me that there is merely a flag/property that is not set correctly on these 3 motifs, to make them shown as known, and to register them in the eidetic memory section as well.

PC EU

This is a variation of probably the most reported problem over the last few months. As far as I can tell it was first reported on 31st October. Granted, it has been almost two weeks since the last report which is probably the longest gap we have had.

In no particular order:

https://forums.elderscrollsonline.com/en/discussion/386791/motifs-known-but-seem-unknown

https://forums.elderscrollsonline.com/en/discussion/379560/new-motifs-do-not-registre-with-eiditic-memory

https://forums.elderscrollsonline.com/en/discussion/378907/ebonshadow-motifs-not-properly-showing-as-collected-under-lore-library

https://forums.elderscrollsonline.com/en/discussion/378497/new-motifs-and-lore-library This is the oldest I have found. Note that one of the posts mentions the problem being reported on PTS previously.

https://forums.elderscrollsonline.com/en/discussion/379790/apostle-staves-already-learned-but-game-doesnt-recognize

https://forums.elderscrollsonline.com/en/discussion/383025/learned-motifs-vanishing

https://forums.elderscrollsonline.com/en/discussion/382870/apostle-ebonshadow-motif

https://forums.elderscrollsonline.com/en/discussion/380562/ps4-na-apostle-ebonshadow-motifs-do-not-show-in-lore-library This one has a reply from @ZOS_GinaBruno to say a fix was being tested (in November)

https://forums.elderscrollsonline.com/en/discussion/380281/new-motifs-does-not-install-in-librairy

https://forums.elderscrollsonline.com/en/discussion/380118/missing-ebonshadow-motifs

This is not an exhaustive list, it is just the ones I have collected over the past few months. As far as I can tell they are all reporting the same problem on different platforms and each person has a different take on it.

I have just checked on PC/EU and we still have this SNAFU How much longer do we have to wait for a fix, ZOS?

Spaghetti code. That's why everything in this game is such a long and complicated fix. It's why bugs like this, Razgarug and Cyrodiil quest boards not giving quests, and shadow image being broken for 3 months. The code is too complex now and many of the original writers of it are no longer there. That's the only explanation other than isn't ZoS just being straight up negligent and lazy which I don't think and hope isn't the case. Otherwise why would these bugs persist for months?

wlb · January 2018

yep apostle is the one that displays this bug for me on na pc