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 Suggestion: Sync data between players through HunterPie account #448

Open
GuidoBelluomo opened this issue Jul 30, 2023 · 3 comments

Comments

@GuidoBelluomo
Copy link

GuidoBelluomo commented Jul 30, 2023

Haven't checked the source code to determine feasibility, but shortly after closing #447 I realized that it could be possible to have the mission host sync data to the other players connected to the same mission.

This could work with a web API thanks to HunterPie accounts, but since it might require a lot of bandwith if many players use this feature, it could probably also be implemented in other ways like hosting a local server for syncing the data and having other clients connect to it.

@Haato3o
Copy link
Member

Haato3o commented Jul 30, 2023

That's the plan in the future, I want it to sync both parts for MHW and also damages in expedition/guiding lands, as those are local only

@codegoose
Copy link

I think that we could host a discovery service wherein player clients provide updates regarding what sessions they're in. The host could then stream updates via TCP and information would be forwarded to the appropriate clients.

I'd like to try this out. Does HunterPie have access to session or quest UUIDs, player UUIDs relative to the current quest?

Haven't looked at the source yet but this would be a very cool feature indeed.

@Haato3o
Copy link
Member

Haato3o commented Jan 13, 2024

That's one of the planned features for HunterPie, but it's not a priority yet. But no, it does not track player's ids nor session id at the moment

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

No branches or pull requests

3 participants