Problem

A gem2lv command is supposed to take a valid number 2-10. Entering 9 or 10 causes an IndexError.

Problem

The latest discord.py "rewrite" version has not been implemented. This includes changes like the new cogs syntax.

Solution

Will update cogs to reflect new changes. Subsequently will also bump up discord.py version to meet new syntax.

Hi, can you add a timezone setting to the bot? There's several server where the game server time is different (thai tos, ktos, ina tos) than the time where the bot is hosted (where the time stamp is taken).

Summary

Basically, send an alert (with an optional mention/ping) to members of a guild.

How it will be implemented

Uses the guild offset implemented by #1. Creates another table in the database per guild. Events are based on server time per server region.

It may look like: $settings set offset n where n is the offset from the local computer's clock and the default timezone (Americas/New_York). Offsets may be enabled via something like: $alerts enable boruta, or $alerts enable all.

Ticket filed on behalf of Pegg.

Problem

Currently, there is no way to administrate the bot remotely. Critically, this includes cog reloading which could be useful if a cog misbehaves or an update is issued.

Solution

Add a cog for admin functions. Restrict access by adding a check to commands. Commands should only activate if sent by the person who set up the bot.

Problem

Although the time matched for "Boruta" on the live prod bot, the bot still output messages. This should only happen on the day it's supposed to start.

As title says, the code hasn't been updated to reflect the recent changes.

Boruta alerts do not seem to consistently fire unless the bot has been restarted. Perhaps #18 will address this.

Problem

When using the $boss x list command, results printed do not reflect the guild offset. Alerts are unaffected.

Solution

Implement an offset check in the boss cog.

Problem

$settings add talt (specifically, but may include related commands) does not process for users that are definitely of member role. In this particular case, the Discord role is present and belongs to Vaivora's member roles.

Ticket filed on behalf of sunshine.

Problem

Boss alerts on a timed schedule are incorrect. The alert does not account for the in-game server time.

Solution

Add offset from server time back into time processing.

Problem

Because gems2lv from the $gems command is so specific in name, even I have issues remembering how to type it.

Solution

Change or make an alias, level instead.

Problem

Even though a channel may be set for events, apparently the alert ignores the channel and uses one for boss.

Problem

Can't add events even with a valid date. Will need to investigate.

discord.py 1.1.x introduces new features, specifically background task improvements, that should be addressed. This will allow me to break up the main bot.py file into smaller manageable/modular pieces.

Problem

Currently, the only valid syntax for optional slices of the contribution leaderboard is a-b, where a < b.

Solution

Two slicing syntaxes (a- or -b) will be added to compensate. -b is basically a-b, whereas a- starts from a onward. These can be compared with list index slicing in python. e.g. a-b corresponds to a_list[0:b]. a- can be represented as a_list[a+1:]

Summary

A user runs a command that the bot will ping the user every two hours for six hours, to remind the user to water the guild crops.

How it will be implemented

Probably will be built similarly to $boss. May add a separate table per guild. Pings will probably be sent via DM.

Ticket filed on behalf of sunshine.

For some reason, the guild level calculation fails to roll over properly. Seeing a guild level below actual with an experience bar over 100%. Something is definitely wrong.

Problem

I have at least two subcommands in mind to use:

• $gems values <gem-color> [<equip-type>], for showing how much each level gives, for each gem
• $gems efficiency <gem-color> [<equip-type>], for showing how effective each level is, with respect to experience and value.

Solution

Implement these. Source and attribute from here

Problem

After an event has been added (for custom) or enabled (permanent), the bot outputs events repeatedly, starting from 60 minutes from event time until 15 minutes from event time. That's a total of 45 alerts.

Problem

Currently, Wings of Vaivora does not use the new and improved help formatting functions in discord.py. To be more in-line with the API, the project should at least attempt to reconcile with the help formatting available.