the stuff on latest updates is based on a redis cache, which is a lot faster and lighter than going through the xenforo backend. when uploaders update a thread and the version number changes, it gets updated in the redis db that latest updates uses. this however, does not automatically trigger a "promotion". a promotion is triggered manually by uploaders, marking the date that the update happened, and this pushes it to the top of latest updates (or not, if they manually mark a date in the past, which they often do if the update was a few days ago, in which case its not at the top but higher than it was before). they dont always do this, either because the game author is abusing the system publishing tiny updates every day to stay at the top of latest updates, or by simple human error by the uploaders forgetting or typoing the date of promotion. the same way that human error couldve occurred with the old method of parsing the update date from the thread description, in which case uploaders could typo it, forget to update it, or use the wrong date format, or put a date 20 years in the future (yes, this did happen). and making the cache api record its own "update date" of when it noticed a change of version number is error prone too, because despite how many users use f95checker, even all of them combined do not track all games, and do not track them 24/7, so if a game gets an update on monday but no one that uses f95checker refreshes that game until sunday, then the new version is picked up on sunday and the updated date is wrong (or it could be several months inbetween instead of just monday to sunday, which would be more of a problem). there is no good way to solve this correctly. and so we must bear with human error. i suggest you sort your list according to the finished and installed checkboxes instead of just by the updated date, then the only risk is your human error. something like this:
View attachment 4712329