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: @bgsbot bgsreport settime auto #58

Open
Jahfry opened this issue Jan 21, 2021 · 1 comment
Open

Feature request: @bgsbot bgsreport settime auto #58

Jahfry opened this issue Jan 21, 2021 · 1 comment

Comments

@Jahfry
Copy link

Jahfry commented Jan 21, 2021

Suggestion: "bgsreport settime auto" to tell the bot to report as soon after the tick as is viable.

Based on a quick Discord exchange I realize you can't report immediately after a tick as data has to finish processing.

I'm not looking for the bot to report at exactly tick time. Just a way to tell it to report as soon as that day's data is done. An hour or 2, or more, delay is fine.

Tick rate seems to be able to swing fairly significantly over time. Looking at the ticks from September 2020 compare to now via https://elitebgs.app/tick it's anywhere from 10am UTC to 21 UTC. I've set my server to 20 UTC just to catch most changes every 24 hours but over a long period I imagine it might tick past 20 UTC again at some point. It would be nice to know the bot will report whenever it feels the current tick data has compiled.

Also not worried about you sending to every subscribed Discord at the same time. Add in staggered transmission so you're not blasting a ton of servers at once. Again, not looking for real time just a way to make sure each report is the next set of data rather than having a possibility of having tick go well past whatever time is set for reporting.

@SayakMukhopadhyay SayakMukhopadhyay transferred this issue from Elite-Kode/elitebgs Mar 4, 2021
@SayakMukhopadhyay
Copy link
Member

Hi @Jahfry , this request has come up before but I this feature is pretty challenging and so I am unwilling to take it up at this point. Maybe sometime in the future I will have enough time to brainstorm this and hence I will keep this issue opened. I hope you understand.

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