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

Support multiplayer spectate data #250

Open
KittyLikeme opened this issue Dec 1, 2024 · 5 comments
Open

Support multiplayer spectate data #250

KittyLikeme opened this issue Dec 1, 2024 · 5 comments
Assignees
Labels

Comments

@KittyLikeme
Copy link

Describe the solution you'd like
Add support for multiplayer spectating with the data structured similarly to the tournament clients.

@KittyLikeme KittyLikeme added the feature request New feature or request label Dec 1, 2024
@KotRikD
Copy link
Member

KotRikD commented Dec 10, 2024

Can you provide details, why you need this functionality? Like maybe some idea or why?

@KittyLikeme
Copy link
Author

Just like custom overlays are using tosu to read data, I want to read the multiplayer data to create a tournament overlay for an upcoming tournament. Of course the data doesn't need to be structured like the tournament clients, that was just an idea.

@KotRikD
Copy link
Member

KotRikD commented Dec 11, 2024

Why you need multiplayer data then? Use tourney field in v1/v2 api

@KittyLikeme
Copy link
Author

KittyLikeme commented Dec 11, 2024

I should have specified that I wanted lazer multiplayer spectate data, my mistake. Lazer doesn't have tournament clients yet so hosting a match in lazer and streaming it is not possible. I would need to read the lazer multiplayer match data and display them live on the overlay.

@KotRikD
Copy link
Member

KotRikD commented Dec 11, 2024

Oh, I got it, yeah, you need specify this in description) We have plans to implement lazer multiplayer data, but no deadlines. Probably I will force it, if I want to host a lazer tournament soon (i'm trying to bait one host, but it doesn't work yet)

current eta: Q1-Q2 2025

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

No branches or pull requests

4 participants