Missing tomestone of Mythology

[DragoonChampion7]

Good Morning

World name: Cactuar
Character name: Notchy Caitsithia

Class/Level: Dragoon/50
Party or solo: solo
In-game time: 11:40 EST (estimate)
Area and coordinates: Dragonhead

I actually noticed this yesterday and I don't think my class/location matters for this case. On Sunday, My total Allagan Tomestone of Mythology was at 405 but I also had maxed out during the week with 450. They weren't being added to the total. Then yesterday I checked my tome for the week had reset to zero but they were not added to my total. I was still at 405. I believe this is the second time this has happened to me. The first happened right after the last patch and I let it pass thinking it was going to be a one-time thing. However it happened again. Yesterday I noticed that the tomestones of Mythology I was getting yesterday is being added to my total. Right now I have Total 525, Week 120. So what happened with the 450 from before?

Has this happened to anyone else yet? Should I submit a report directly?

[Nekodar]

What likely happened is:
1) You had 450 from one week
2) You got 450 from the week after, for total of 900
3) You bought item for 495, which means you have 405 remaining
4) You got 120 so far this week for 525 total...

Looking at your lodestone page I can see you have the DRG ilvl 90 Myth piece, which does cost 495 myths...

[DragoonChampion7]

Okay, let me back track. 900 mythos, that had to me my relic+1, which I got a few weeks ago. The Wyrm helm was one of the first things I got using mythos, even before the relic, that was a long time ago.

Last week I exactly had a total of 405 mythos and I had maxed out for the week with 450. Why is the 450 not being carried over? The menu was showing exactly this:
405/2000 (total) 450/450 week. Like how does that make sense?
Yesterday it should have shown: 855/2000 (total) 0/450 (week) not 405/2000 (total) 0/450 (week)...which I was seeing yesterday.
I should have 855 total yesterday morning and from the 120 I made between yesterday and today I should have 975...
Actually, from what I'm seeing today, it doesn't even work like that anymore. It was suppose to be adding to the total in the first place until I hit the 450 max.

The last thing I purchased was the 300x3 items for my relic, and that was like 2-3 weeks ago...

[ZanderMist]

405/2000 (total) 450/450 week. Like how does that make sense?

Makes sense: you had 450 from the week before, added 45 for the current week (that makes 495, which is the exact cost for a myth piece), spent those 495, leaving you with 0/2000 total 45/450 week. Then proceeded to cap the remaining 405 for the week, and that's where 405/2000 (Total) 450/450 week comes from. Check your armoury, might have bought something by accident.

[Nekodar]

Whatever you get during the week is added to the total as soon as you get the tomes. There is no week -> total carryover at reset.

Example:
Before doing duty roulette low level today I had 6/2000 total and x/450 week
After duty roulette low level today I had 16/2000 total and (x+10)/450 week

If it worked the way you describe, I would have had
6/2000 total and (x+10)/450 week after the duty roulette.

If you actually have a problem or not is not for me to decide, just saying how the total and weekly tally actually works.

[DragoonChampion7]

Exactly that's how I thought it was suppose to work...like how it is working today. But last week I started the week off with the 405/2000 total. I was recieving my new mythos for the week, however none of it being carried over immediately. Reached 450/450 just to loss it all yesterday morning.

Thank you for confirming how it really works. I needed to know before I reported it. XD

[Furlamseere]

Greetings DragoonChampion7,

We encourage you to attempt the suggestion offered by Nekodar. As you have not responded, we are going to go ahead and assume this has resolved. If this does not resolve the issue, please create another bug report thread and use the bug reporting template found Here. Also, please state the steps you have attempted to resolve this issue.

- Furlamseere