Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect "last played" date displayed when Java version is incompatible #2422

Closed
1 task done
telecter opened this issue May 19, 2024 · 0 comments · Fixed by #2423
Closed
1 task done

Incorrect "last played" date displayed when Java version is incompatible #2422

telecter opened this issue May 19, 2024 · 0 comments · Fixed by #2423
Labels
bug Something isn't working

Comments

@telecter
Copy link

telecter commented May 19, 2024

Operating System

macOS

Version of Prism Launcher

Prism Launcher 8.3

Version of Qt

Qt 6.6.3

Description of bug

Observed Behavior:
When the game crashed due to an incompatible JRE version, The "last played" date displays as Dec 31, 1969.
The "last played" date would either not show, or show the current date.
Expected Behavior:
The date would either not show, or show the current date.

Steps to reproduce

  1. Create a new instance of Minecraft in Prism Launcher
  2. Ensure you have an incompatible version of Java set for that instance
  3. Observe the "last played" date at the bottom of the launcher after the games fails to launch

Suspected cause

It could possibly be related to the launcher setting the "last played" date to the Unix epoch (Jan 1, 1970) before you actually play it. The date that is displayed, Dec 31, 1969 at 19:00, is only a few hours from the epoch.

(I might be wrong about this though!)

This issue is unique

  • I have searched the issue tracker and did not find an issue describing my bug.
@telecter telecter added the bug Something isn't working label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant