-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Voice activity XP contribution #199
Comments
In case a separately tracked statistic would be too annoying to implement, it might be fine to pre-multiply the XP when adding it? Though I’m unsure if that would work too well |
A separately tracked stat would be perfectly fine to implement. I think the annoying part here is just tracking voice states. Do you want to work on this at all? |
I'm not familiar with how experienced is structured, but maybe. I wouldn't count on it though |
I can help if you wish. I might also be able to work on this directly at some point. |
Is this still planned? |
Yes, this is still planned for someday. I have a few other things I want to get to first, and the demand for this has seemed pretty low. If you really want it, I will get to it (and please let me know, so i can prioritize accordingly)- however, if you know a little rust, I can also absolutely coach you through working on the codebase. |
Thinking about the design for this- my main concern is giving people new roles? that seems like it would be a lot of database requests made passively? not sure |
I would love to, but I‘m currently overrun by school. If I ever have free time, why not? |
Maybe just every minute to the database and checking? |
On the other hand, database load is currently very low. So it may not be a problem. The other problem is just tracking who's in voice, and having an interval timer for each- not sure how i feel about running an arbitrary number of background tasks? on the other hand, that's what tokio is designed for. |
Problem
There are multiple cases where a server member might be far more active in voice channels than in text channels. At the moment, voice activity is at all factored into the XP calculation, leading to these members having extremely low levels despite being some of the most active ones.
Proposed solution
To solve this issue, I propose that voice activity (perhaps only during microphone activation? I can’t recall if that’s visible to the bot without being in the call) contributes to a secondary experience stat, that is added onto the currently existing XP system upon level calculation.
The advantage of it being a separately tracked statistic is that it is trivial to dynamically change how much influence voice activity should have upon the calculated levels on a per-server configurable basis.
The text was updated successfully, but these errors were encountered: