-
Notifications
You must be signed in to change notification settings - Fork 18
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
[Util Change]: Server jars Fabric release date bug #193
Comments
After looking a bit at it, it is a apparent that it's a problem with the fabric API itself. I will see if I can inform them. There might need to be a workaround for this though. |
I think the issue is we're just pulling the wrong release date - maybe from the installer or loader (rather than the game version's release date), as I assume they regularly update those. |
@joshbker For this I would say that the release date that we need to pull would be the fabric loader release date right? If so, I'm quite sure that the v2 fabric meta does not store this. I suggest taking a workaround such a stating "Release date not accessible" or just removing the release date column all together. |
Agree with above, doesn't appear to be possible to pull this release date from the data the Fabric API gives us. Here's a (formatted) snippet of a JSON response: Both the timestamps represent the same date and time, always being very close to the current date/time. Therefore these data points are worthless. Therefore, it doesn't look like they expose this data. Perhaps something we should nag them on. But nothing we can do from here for this issue. Closing and adding a note on the site regarding this. |
Util Name
Server Jars
Changes
Extra Info
No response
The text was updated successfully, but these errors were encountered: