Noticed that the F95Checker doesn't update the mod's
Last Updated date entry in its list if the
Game Version date of a
mod forum OP stays the same, but
Mod Version changes. Even changing the
Updated date is ignored.
Here's an example mod page where the Checker's date still shows
20/08/2025 when the
Game Version was corrected from
v0.8.1b to
v0.8b1 what can be checked in the Checker's
Timeline tab. There have been a couple of mod updates afterwards without date update although at least gave an alert popup.
The separated
Mod Version and
Game Version entries are part of the default F95 Mods template when someone starts a new topic in the Mods forum, so this should really be respected and better supported. In the end, the mod's version changes are more important than the game version here.
I personally mixed both dates to
Game/Mod Version with my own mod page what the Checker scans correctly for changes.
right, i see. so for some backstory, last updated date has always been a pain. there is no reliable way to have this info. the latest updates api has the date that an update was "promoted" (as in, bumped to the front of latest updates), which some games never get promoted as its only for major updates usually and there is a system in place to prevent abuse, and also sometimes moderators promote with incorrect date or forget to promote. there is the "thread updated"/"release date" field in game threads, which moderators can forget to update or typo it and put a date in 2053. there is the date that the thread was edited, which would mean it would register non-updates as a new last updated date.
long ago f95checker only used the "thread updated"/"release date" field in game threads, some time later i switched to only using latest updates "promoted" date, and neither worked well.
what happens now is that it bumps the last updated date when the cache api (which is what your f95checker client gets info from, it sits between f95checker and f95zone to prevent ddossing the forum) notices the version changing. that has been the best system so far. new version number means an update, so bump the updated date.
when possible, version info uses what latest updates reports, as even if promoting can be hit or miss the versions are very reliable on it. however as
GrammerCop pointed out mods are held to a lesser standards than games, they are not tracked by latest updates, so there is no "single source of truth" for mod versions. in this case it falls back to parsing the thread for version info. currently the code that does this is:
Python:
thread_version = get_game_attr("version", "game version", "mod version")
which finds the first field (case insensitive) of the names provided and uses that one if present.
the example you gave has "game version" and "mod version", so it finds game version before mod version. hence why updating the mod versions for same game version doesnt change the version attribute in f95checker and why last updated date doesnt change.
i suppose i could prioritize mod version over game version, afterall even if a game thread included a link to a mod with the version listed in the game thread too, it would list the game version just as "version" and thus still be prioritized over mod version.
being a change in the cache api, this will slowly apply to all threads over the next week as caches get invalidated and refreshed. for your example, f95checker will start reporting 0.7.1 (mod version) instead of 0.8b1 (game version) sometime within a week from now.
As I understand it, the reason is that the mod pages are not held to as rigid a standard as the game pages, which in turn makes it nearly impossible to compensate for programmatically. The mod pages will be loaded, but it's considered pot luck.
I personally have mod pages in my library, but only for lazy convenience since they are not reliable.
edit: the date may have been updated but the database has not. Edit2: you can search the threads. I do remember this has been discussed.
this is absolutely correct, mod pages get recached less often on average, but yeah i think they meant a more subtle nuance with how the last updated date behaves