Deep Bot - Twitch Streamer Assistant

Deep Bot => Bug Reports => Topic started by: darthclide on January 30, 2015, 09:58:59 AM

Title: commands sometimes stop working
Post by: darthclide on January 30, 2015, 09:58:59 AM

Sometimes the only command that works in the "song" subset is !songrequest. All others stop working. Any idea why this is happening?

Title: Re: commands sometimes stop working
Post by: darthclide on January 31, 2015, 06:42:20 AM

Update, the songrequest command sometimes doesn't work either now... Why is this happening?

Title: Re: commands sometimes stop working
Post by: LostPirates on March 13, 2015, 08:36:45 PM

it might be because its "!requestsong" not "!songrequest"

Title: Re: commands sometimes stop working
Post by: darthclide on March 14, 2015, 02:12:16 AM

*update* This problem hasn't been seen since, I am guessing the bug was fixed whatever it was.

Also, LostPirates I have custom commands that use the deepbot commands. In this case, all default deepbot commands stopped working. Fortunately I haven't seen this issue in over a month now.

Title: Re: commands sometimes stop working
Post by: LostPirates on March 19, 2015, 03:30:04 PM

wait darthclide you can change what the commands are for "!requestsong" and other's? i would love to know how to do this. if you could help me out i would be very much thankful

Title: Re: commands sometimes stop working
Post by: TheNumbLock on March 19, 2015, 03:56:10 PM

You just do a custom command. Example: !songrequest Message of the command: !requestsong @target@

@target@ grabs the next word/link after the command. So !songrequest youtubelink

You can find a list of custom variables here: http://deepbot.deep.sg/wiki/Custom+Commands&structure=Index&page_ref_id=16

If you need any other examples, let me know.

Title: Re: commands sometimes stop working
Post by: darthclide on March 20, 2015, 03:36:21 AM

^ what he said.

Also, I realize now I made a duplicate post talking about this issue which just came up again a couple nights ago. I am guessing this is 99% likely a problem with twitch and deepbot's ability to connect, but I just wanted to mention it here in case it is a 50/50 split problem between the two.