Skip to content
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

Banners, Langauge, Commands, Times and Lists, oh my! #48

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

skylordjason
Copy link
Contributor

Not quite the same ring, but it's what was done.

Added the following banner to the top of the Readme, because banners are awesome. (Or to make it look better)
image

Added the ability for a user to do @bot list all to get a generated PM of all videos currently in the queue. Splits the list into multiple messages to fit Discord's Char Limit.

Modified the time that is shown on Remaining Play Time: to say hours and minutes versus an unmodified time. (1 hour and 30 minutes over 90:00 minutes)

Modified the Language of some of the Readme to be more friendly or logical, whichever came first.

Modified the Readme to represent the added command above as well as link to the Usage wiki for detailed usage info.

Modified the Readme to explain how the bot will initialize depending on your connected channel.

Just a logo idea for Lethe. Plus, a bit of changes to keep it up to date with current commands and features.
This one is a necessity to PM, as it would flood the chat for large
queues.
@@ -23,18 +23,30 @@ npm install
```

## Usage
####Run by Command Line Arguments
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you follow the correct markdown hierarchy here? (Sub headers of a second-level header are always third-level)

@meew0
Copy link
Owner

meew0 commented Jan 13, 2016

Also, the problem with the list all command is that even though it's sent over PM, Discord's rate limiting still applies so for very long queues it will eventually break. I suggest that if it gets too long (>3 messages) it gets sent to hastebin instead like list saved does.

When you intended to have something else there for the 3rd heading, but then decided against it and never reverted it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants