Messages

1

Feature Requests / Re: Include more User Database fields in the Database Export

« on: August 27, 2018, 04:07:21 AM »

YES!  This feature is very important for pretty much an product that is used to manage a large number of users.  I love Deepbot, but I need this capability to manage my users and community, and I do not want to have to change to a different bot, just because I cannot live without this feature!

2

Feature Requests / Re: users DB XML export

« on: August 27, 2018, 04:05:41 AM »

I love Deepbot.  However, not having the ability to export/import the user database is one of a few very important features I would really like to see added to Deepbot.  I actually might have to switch bots, if I can't find some workaround to be able to *at least* export my user data, so I can use it for many more stream and community related tasks.  Deepbot is an excellent bot, but this needs to be a feature of any product that potentially manages a large number of users.  Please consider adding this!  I need this functionality so bad that I don't know if I can wait for it to be added.  I love Deepbot, but I need this capability.

3

Feature Requests / Re: Show cooldown time remaining when someone tries a command currently on cooldown.

« on: April 13, 2018, 03:14:51 AM »

Even a global cooldown response of "You must wait ("11 minutes" or "xx seconds" if less than 1 minute) before running this command..." would be enough to prevent the problems we are having.

4

Feature Requests / Re: Add "cooldown timer pools" where any command in that "pool" can only be run...

« on: April 13, 2018, 02:49:38 AM »

Each custom command can have it's own "Access Denied" or "Insufficient currency" message.  it would be nice if each command could have it's own "@cdtime@ remaining until this command can be run..." message set that is appropriate for that command.

5

Feature Requests / Add "cooldown timer pools" where any command in that "pool" can only be run...

« on: April 13, 2018, 02:46:38 AM »

Add "cooldown timer pools" where any command in that "pool" can only be run during the cooldown perion.  For instance, if I have the following "Spawn Pool" set up for 10 minutes, I could create a bunch for spawn commands where people in chat can spawn zombies on me in my game (I currently have this set up for 7 Days to Die), but I only want one person to be able to run a spawn command every 10 minutes.  I thought about creating a single command with a 10 minutes cooldown called (!10mincd), renaming my "!spawn_bear" command to "!xspawn_bear", then having new "!spawn_bear" command immediately run the "!10mincd !xspawn_bear" command as "user", and then have the "!10mincd" command set to run "@target@" as "user". I think this would work.  Now, if we could just get a generic "time left on cooldown" message for commands on cooldown that say "You must wait 4 minutes before running this command..." or "You must wait 34 seconds before running this command..." when the users try to run a command currently on cooldown.  Currently, when a user runs a command on cooldown, it just seems like the command doesn't work, so they run it multiple times.  I have commands with 45 minutes cooldowns, and people that know about the cooldown will just run it every 5 minutes, hoping the cooldown is over.  I would really like to see something simple added to allow cooldown times to be shown when people try to run a command on cooldown.  I really don't want to have to add a complicated script to every single command with a cooldown, because a lot of those commands already run a complicated scripts, and it would get very difficult to troubleshoot problems with adding a script withing a script within a script.

6

Help/Support / Re: Cooldown check?

« on: April 13, 2018, 02:35:06 AM »

I would really like to see a cooldown time remaing response, just like user's get an "access denied" message.  if a command is on cooldown, it would be really nice for users tyo automaticall be notified of how much time is left until it can be run again.  I have dozens of commands that have 5+ minute cooldowns, and some voer 30 minutes, and it is impossible to keep track of more than 1 or 2, and when people try the command, there is no indication that it is on cooldown, except the command doesn't work.  I would really like to see this added as an an option for all commands, and not need to have complicated customization for each command, which may already include complicated customization.

7

Help/Support / Re: Is there a way for channel mods to access my deepbot?

« on: April 13, 2018, 02:27:13 AM »

Where can mods access this "web dashboard"  This would be really great!

8

Feature Requests / Show cooldown time remaining when someone tries a command currently on cooldown.

« on: April 13, 2018, 02:05:13 AM »

This is something that I see a lot, and it's really having a negative effect on my stream.  I have commands that affect the games I am playing... a lot of commands, and many have 30-45 minute cooldowns to prevent people from ruining the game from too much interaction.  My viewers love it, but it gets really frustrating when they try a command, and have no idea why it's not working, and I find myself constantly explaining that the command is on cooldown... and that is if I catch it!  I usually do, but then I have no idea how long until they can run the command.  It would be really nice to have the option to show "26 minutes until @command@ can be run again..." or "52 seconds until @command@ can be run again..." or something like that!  It seems simple to implement, and something that I thought was already there, until I looked for it!

9

Pre-release Feedback / Re: Sound Effects Suggested Change - Queue sounds

« on: November 24, 2017, 02:49:31 PM »

I don't know if it's better to start a new thread.  Mostly because this post almost exactly describes the issues we have within sounds overwriting each other, and for the same reasons.  Our supporters are very enthusiastic about these intro commands that allow subscribers to announce their presence in chat, but with style. They love the sound clips they choose, but as our chat gets more active, I have been reqired to remove all sounds from Deepbot alerts and notifications, because it was rare for sounds to finish without being abruptly cut off by another sound. I keep finding myself needing other bots to handle stuff that just doesn't work right in Deepbot. Song requests, commands utilizing OBS Remote web sockets (for commands to pop a video clip/meme in OBS), commands that launch external commands or scripts, an now everything that plays sounds.  I really like Deepbot, and I see OBS Remote is being addressed in the latest beta, but if I keep needing to use other bots to do things that Deepbot should be able to handle, it starts to make more sense to move to using one of those bots as my primary bot. I would really like to avoid this, and continue using Deepbot as my bot of choice!

Please consider addressing this!

-TSForrest