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

Add the option to do predictions by match instead of map #156

Closed
3 tasks
slmnio opened this issue Nov 28, 2022 · 1 comment · Fixed by #157
Closed
3 tasks

Add the option to do predictions by match instead of map #156

slmnio opened this issue Nov 28, 2022 · 1 comment · Fixed by #157
Labels
section: broadcast Relates to broadcast overlays or pages section: server Relates to server or node scripts

Comments

@slmnio
Copy link
Owner

slmnio commented Nov 28, 2022

The new automatic predictions system from #141 is great and has worked pretty flawlessly. However, predicting each map instead of the match has some problems:

  • Producers get busy and forget to do every single map
  • Map predictions get low engagement because they're open for a short time, and viewers much prefer to bet for the entire match.

My proposal for changes is:

  • Add logic to understand if a match has been won or not (match.first_to). We don't need to worry about looking behind for previously played matches, it should be fine just using the active broadcast.live_match
  • Make match predictions default over map predictions
  • Add a broadcast setting (broadcast.broadcast_settings) to override to map predictions
@slmnio slmnio added section: broadcast Relates to broadcast overlays or pages section: server Relates to server or node scripts labels Nov 28, 2022
@slmnio
Copy link
Owner Author

slmnio commented Nov 28, 2022

@ZusorCode might be up your alley

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
section: broadcast Relates to broadcast overlays or pages section: server Relates to server or node scripts
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant