conner-anderson / discord-hvz Goto Github PK

This will probably require removing groups altogether.

https://stackoverflow.com/questions/13851157/oauth2-and-google-api-access-token-expiration-time

Probably because of the delay in setting roles when they are changed.

This system is to help users when setting up the bot know what's wrong. This could be done with more helpful exception messages, or an independent configuration checker.

Currently, a human who turns zombie does not know where on the Discord to turn in tags, because they have never seen the button or channel before. I propose a single channel with all buttons / interactions a player could ever use. Pressing a button they don't have access to simply does nothing (or preferably explains why)

To start with, these should assume the admin knows what they are doing. No confirmation. We can fix that later.

Delete user

• Revoke tag (maybe a stupid-check to see if it would break history?)
• Change item (should change any value in any cell of the database. Obviously this is dangerous, but it is needed anyways.
• Change item, safe (a set of commands that more safely change common variables in the database. Needs more thought.
• Force register (some means of registering another user in case something goes wrong. I'd suggest it just takes the admin through the normal process, but with changes with ChatBot that make it affect a different user.

The bot currently only works with one server. We should be able to have the bot joined onto multiple servers, but we can select which one it "runs" on in code or a config file. That way, we can do real testing on the actual LETU Nerf server before the game starts (with private channels of course), and switch over to a local version as well.

This way, we can still run the dev version during HvZ by running it from a duplicate folder and changing the server variable.

Any other checks too?

Can seamlessly resume conversations on a crash.

Sometimes when the bot launches, this error is thrown:

Ignoring exception in on_member_update Traceback (most recent call last): File "C:\Users\conne\Dev\discord-hvz-live\venv\lib\site-packages\discord\client.py", line 352, in _run_event await coro(*args, **kwargs) File "C:\Users\conne\Dev\discord-hvz-live\discord_hvz.py", line 106, in inner my_guild_id = self.guild.id AttributeError: 'NoneType' object has no attribute 'id'

This is probably because another event is firing before the on_ready event, and the check_event decorator needs information that is set during on_ready to work. This bug causes no issues besides the annoying log I believe.

!edit "Fred Fredrikson" is an example of a command that will cause a Discord.py exception.

Default role is human.

Probably force them to decide on registering for HvZ. Maybe ask if they are interested in the Nerf club too?

The first time succeeds, the second will fail... most likely at the database editing method.

After the verification step of tag logging, the server needs to validate the tag, then give feedback to the user.

Users already on the Nerf server should have a button (reaction) to click to start a registration conversation. New users on the server should be asked if they want to register for HvZ.

Should be a rich message with as much interesting information as is reasonable, all in a dedicated channel.

Just kind of annoying for the system admin testing stuff. Meh.

Have bot able to resume conversations on a restart, and the ability for admins to restart or shutdown gracefully.