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

Feature request: Current game patch endpoint #233

Closed
martinmiglio opened this issue Sep 11, 2023 · 2 comments
Closed

Feature request: Current game patch endpoint #233

martinmiglio opened this issue Sep 11, 2023 · 2 comments

Comments

@martinmiglio
Copy link

Feature Description

This is a request to add an endpoint to return the current patch number of the game (i.e. 0.13.5.1.26126) .
A possible source for this is the the Changelog page on the EFT Wiki or from the Tarkov Changes site.

My use case

I'm in the works on creating a site for users to report hideout scav case inputs and returns. I want to be able to track data cross-patches, but be able to filter by certain patch numbers. At this moment, I store the games current minor version (i.e 0.12, 0.13, 0.14), with plans to manually update per patch. It would be preferable to save this value down to the exact patch but it is not feasible to manually record and update this.

I would be open to looking into contributing this endpoint, although I am inexperienced with creating API's in graphql. If someone can guide me to a similar endpoint (if it exists), one which scrapes data from the wiki or tarkov changes, I can give it a shot.

@GrantBirki
Copy link
Member

@martinmiglio Are you after an endpoint that just returns the current patch and nothing else?

We update the tarkov.dev website when each wipe come outs by just adding a new value to the following JSON file that can be viewed here -> https://github.com/the-hideout/tarkov-dev/blob/dff6012feeebe44aa629ef8970b1a4c3421623e2/src/data/wipe-details.json

You could possibly write some code that does the following:

  • Fetches this file every so often
  • Caches the results of this file somewhere within the system you are building
  • Sort the JSON contents by the wipe's start
  • Get the most recent value

Hopefully that helps!

It would also be pretty darn easy to include this data somewhere without our GraphQL API if it is not there already.

@martinmiglio
Copy link
Author

That is absolutely what I'm after, thank you.

Given it is this accessible, I'm not sure its necessary to add to the GraphQL API, although it may make sense for other use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants