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

QOL: Differentiating channels, assuming !play when a link is posted on its own #235

Open
Noctimor opened this issue Apr 30, 2016 · 5 comments
Labels
t/request Someone requested a new feature

Comments

@Noctimor
Copy link

In my Discord room, I have a "#music" channel designed to keep the clutter out of the main chat when adding songs to the bot. Given that the sole purpose of this channel is to add music, it'd be nice if there was an option to assume that if a standalone link is posted in a designated channel, then that song should be placed in the queue, as it's more convenient to just Ctrl-C, Ctrl-V a link and then go back to whatever I was doing. Definitely more of a quality-of-life thing than anything, and I totally understand (and agree) that other things should probably come first.

@rrbailey89
Copy link

It sounds like what your saying is that you want the bot to read other channels that its not bound to.. and if someone posts in the wrong channel to move it to the correct channel and then execute?

@Noctimor
Copy link
Author

Noctimor commented May 1, 2016

Not quite. I'm fine with the current system of only accepting commands from the channels its bound to, it's just within those channels I want to forego having to put !play in front of a link. When I have a channel that's dedicated to queueing music, it'd be nice to just copy-paste a link and get on with what I'm doing.

@imayhaveborkedit imayhaveborkedit added the t/request Someone requested a new feature label May 2, 2016
@imayhaveborkedit
Copy link
Collaborator

This is extra low priority, but if I ever run out of things to do this seems like something decent to add.

@catgirlinspace
Copy link

You could set the prefix to nothing. @Noctimor

@Noctimor
Copy link
Author

Noctimor commented May 3, 2016

If I set the prefix to nothing, wouldn't I still have to say "play" first? And yeah, definitely low priority -- just aimed to get the suggestion out there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t/request Someone requested a new feature
Projects
None yet
Development

No branches or pull requests

4 participants