ct-bess/bean-stalk

Personal Discord Bot

I use vim

bean-stalk's Issues

3D Tick Tack Toe

For mical

Channel List command

Currently we have the phenomenal -yeet command. But with no way to see the available channels, we lack a good way to reliably send messages to other servers which we may not be members of. the current workaround of a $echo -yeet loop is unreliable and a nuisance to the channels it lands in. I propose that we include a command to list all of the channels of which bean stalk is a member, including the name and ID of each channel (and possibly the server name if you can work out the formatting)

Context

Most programs allow for a programmatic way of viewing all of the various options they can use in their commands. In many, that simply involves a list of args and their possible values being produced by the --help arg, but in some, there is an entirely separate command that lists out a database or other data to be used in a different command. Either of these approaches could be effective here.

Possible Fix

The bot should have an attribute showing all of the guilds it is a member of. For example, the discord.py bot has a bot.guilds attribute that is a list of guilds. Ideally each guild object will have an attribute for all text channels (in discord.py it is text_channels). From here it would be simple to iterate over each guild and each text channel in turn and print output based on that.

webhook issue test

bruh

Event Command Overhaul

The way this command was initially implemented is really bad; Every minute Bean filters a map of events for ones that match the date & time. Rather than doing a search every minute and wasting precious resources, let's assemble the events in such a way that all Bean needs to do is look into an object's index using the date/time as the key, and if there's something in there at that index we proceed to do the normal event stuff.

Old way:

• search all events for ones that match the current date/time

New way:

• look into an object using the date/time as the key; truthy at that index implies we have an event there

ok have a nice day

add vim

please

Discord 12.4.1 API upgrade issues

1. message.content.messages.last() is apparently not a function anymore

2. sending message.author no longer @'s a user

   Have to do <@!${message.author.id}> now

3. channels isn't a collection anymore, so don't forEach it, you have to do channels.cache or somethin