| Commit message (Collapse) | Author | Lines |
|
|
|
|
|
|
|
|
|
Previously, this was done by the SeasonManager cog, which was removed
during our deseasonification efforts.
|
|
|
|
|
|
|
|
This way, we can standardize the way Months are shown to both the user
and the developer. Note that if passing a Month member to an f-string,
the `!s` format code must be specified to ensure our __str__ is used.
Co-authored-by: MarkKoz <[email protected]>
|
|
Previously, the `should_cycle` iterator would signal that it is time
to cycle by yielding True. As per Mark's suggestion, this is adjusted
to yield either None, or ints representing days since last cycle.
This is more transparent, as the daemon can now perform the comparison
against the configured cycle frequency itself, rather than relying
on being fed the correct value from a "black box".
See `_reset_should_cycle` docstring for further clarification.
Co-authored-by: MarkKoz <[email protected]>
|
|
Add a static check confirming that no seasons overlap. This avoids
having to deal with ambiguities in `get_current_season` at runtime,
as we can now rely on `len(active_seasons)` always being 0 or 1.
Co-authored-by: MarkKoz <[email protected]>
|
|
For the sake of consistency - all other seasonal bot names have
the B capitalized.
Co-authored-by: MarkKoz <[email protected]>
|
|
With the 'seasonal-structure' branch being merged in the branding
repository, we can start polling master.
|
|
After 00af207de3087a41270f216ad86e06ba7dbf9d42, we should ensure that
the month names aren't shown to the user in all caps.
Co-authored-by: MarkKoz <[email protected]>
|
|
It is not necessary for these to be coroutines.
Co-authored-by: MarkKoz <[email protected]>
|
|
This should be more readable.
Co-authored-by: MarkKoz <[email protected]>
|
|
Reduces code duplication.
Co-authored-by: MarkKoz <[email protected]>
|
|
Co-authored-by: MarkKoz <[email protected]>
|
|
* Capitalize month names
* Add backticks to `sha` attr reference
* Avoid misusing the term 'poll'
Co-authored-by: MarkKoz <[email protected]>
|
|
Co-authored-by: MarkKoz <[email protected]>
|
|
Co-authored-by: MarkKoz <[email protected]>
|
|
Changed `hours` argument in `refresh_genres_task` from `1.0` to `24.0` due no need for so fast updating.
|
|
|
|
matching in `.games` command.
|
|
that have higher than 0.60 ratio.
|
|
|
|
|
|
Previously, the env var was only being used for seasonal decorators,
not branding. Although for testing purposes, seasons can be easily
set via bot commands, it makes sense to also use the env var to
choose the current season.
|
|
The function is useful to other modules as well - not only decorators.
This declares it as public and moves it to a more accessible place.
|
|
Constant is no longer used.
See: 9259f985e6e327a522b4420c879a50cb4f75a09d
|
|
A persistent config file will remember whether the daemon is supposed
to be running, or not. This means that instead of relying on the env
variable, the daemon can be turned on or off "once and for all"
via a command, and will not violate this decision on restart.
This effectively deprecates the `Branding.autostart` env var. It is
believed that having two ways to configure the same thing would
be more confusing than useful. The env var will be removed.
The two helper functions for reading and writing have been implemented
in a generic manner, meaning that should a new config key be added in
the future, the helpers shouldn't require any further adjustments.
Suggested by lemon and scragly.
Co-authored-by: Leon Sandøy <[email protected]>
Co-authored-by: scragly <[email protected]>
|