This post is about a possible fix for the playtime glitch I mentioned here (steam://openurhttps://gtm.steamproxy.vip/groups/SteamClientBeta/discussions/0/601917139265459334/)).

The main cause for this glitch is the existence of the 2 playtimes, although simply REMOVING them is problematic:
-If you play offline, but forget to turn on Offline Mode, removing the local playtime is problematic, because it doesn't record offline play.
-If connection to the Steam servers is lost, and you don't play (e. g. when your PC shuts off during play), removing the server playtime is problematic, because it adds playtime during which you haven't even played.
Although, I have a possible fix:
If this glitch occurs, the user would be notified.
-EXCEPTIONS:
-If the user has hidden their playtime of the game, the glitch cannot be fixed, because from what I've heard, Valve is unable to access a user's local playtime when it's hidden. A notification pops up, saying something like: "Steam ran into an error while trying to fix this glitch. Cause: your profile is hidden."
-If the user is not connected to the Steam servers, trying to update the playtimes is unsuccessful, because the server playtime cannot be updated. A notification pops up, saying something like: "Steam's servers cannot be accessed. Try reconnecting to the internet."
If the user clicks on the notification, a choice selection would pop up, which labels both playtimes.
Here's what it would look like:
Choose one playtime which overwrites the other to itself to fix playtime discrepancies.
[Server playtime]: If you've suddenly disconnected from the internet, and haven't played after disconnection, select this playtime.
[Local playtime]: If you've played offline without turning on Offline Mode, select this playtime.
After selection: Are you sure you want to overwrite both playtimes to [server/local playtime]?
YES
You playtime has been corrected to [Server/local playtime].
NO
The user goes back to the selection screen.

After selection, the playtimes are written to the same value. If the user re-triggers this glitch, they can do this again.
Because so many people are still getting this glitch, hopefully this is gonna get fixed soon.

FOR EVERY MODERATOR AND VALVE EMPLOYEE:
Please don't lock this thread. This issue is still prevalent.