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

[Util Change]: Server jars Fabric release date bug #193

Closed
stephendotgg opened this issue Mar 31, 2024 · 4 comments
Closed

[Util Change]: Server jars Fabric release date bug #193

stephendotgg opened this issue Mar 31, 2024 · 4 comments
Labels
Bug Something isn't working

Comments

@stephendotgg
Copy link
Member

Util Name

Server Jars

Changes

image

Extra Info

No response

@stephendotgg stephendotgg added the Bug Something isn't working label Mar 31, 2024
@StillLutto
Copy link
Contributor

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.

@joshbker
Copy link
Member

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.

@StillLutto
Copy link
Contributor

StillLutto commented May 19, 2024

@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.

@stephendotgg
Copy link
Member Author

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:
https://paste.learnspigot.com/ilibokisaw.bash

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.

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

No branches or pull requests

3 participants