Repository navigation
Conversation
d10sfan
marked this pull request as draft
October 3, 2026 01:41
Contributor
Author
|
Moving this to draft, will rebase on develop after the rest of the changes make it in. |
Contributor
Author
|
Completed the re-do, so it's ready for review |
d10sfan
marked this pull request as ready for review
October 5, 2026 16:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new ingame API based on the new REST API server.
This as a starting point is used so you could call an API and get item categories and then all the items themselves, with support for searching. This dosen't expose the database itself, just specific API calls.
This could eventually be used to extend other commands that are outside the scope of the gm commands in the chat interface.
The way it works is that there's a new command that the python layer can use to trigger an exchange token to be created. This is then used with a new API call to get a jwt token back. Then the client can use this token to do the API queries.
This way this data API is not accessible outside having a valid game session. The separate jwt token is so that we can use a more traditional rest api structure.
Right now I'm able to use this with the imgui gui that I'm building to have a list of all the items and their metadata, and be able to use the gm commands to add to their inventory.