<r>Previous behavior:<br/> <br/> (1st queued non-request) (Request #1 @3:00 PM) (Request #2 @3:01 PM) (Queued non-requests)<br/> <br/> Current behavior:<br/> <br/> (Request #2 @3:01 PM) (Request #1 @3:00 PM) (Queued non-requests)<br/> <br/> Desired behavior:<br/> <br/> (Request #1 @3:00 PM) (Request...

A command of !next or related, shows the next X songs in queue as specified via configuration. Obviously subject to change, but since the queue is SQL this should be pretty easy to write.

As with the other per-channel options.

(This is so I can disable !np on a network)

A way to have the bot join a Mumble server and accept commands via chat would be really cool. Not sure if you can do it, but certainly something unique!

Is there a way to detect that then so it can use the now playing feature rather than "is not listening to anything right now"?

What kind of rules that would get it a ban? Would this be something better suited to the actual broadcasting software?

Currently the bot only scrobbles at the end of a song - an option to have "live" scrobbling for compatibility with people's IRC commands and other things would be cool.

If your host doesn't support PHP you should probably get a new host... free websites are not really the way to go if you're doing anything that is custom written.

<r>SAM automatically downgrades the weight of each song played a fraction each time it's played so theoretically more popular music circulates when requests drive up the weight, but the bot isn't set to edit the weight when a request is inserted.<br/> <br/> Just adding the extra query would vastly i...

The bot works great if each DJ has a copy of it, but on a per-dj basis with one copy running there's no good way to manage multiple SAM DJs.

It would be great if we could specify users that the bot would match and connect to the respective database to enable requests.