![]() ![]() It requires you to make two adjustments so that it knows what user name to look up by default. Usage: This command is not copy/paste friendly but my suggested method. Important to note, that if you’re playing on PC and not in the NA/US region, you will need to explicitly give the region. You can find an entire list of the various stats you’re able to look up here, and further general documentation here. This allows you to use a shorter command to check the stats, and also limits the usage so that any Overwatch player isn’t able to be looked up – just you (or whoever you define). The second Response is for a command that checks a defined Overwatch player, and what I personally recommend. While this allows your viewers to check any Overwatch player on any platform, it makes it so the command can be longer for the user to type, as well as has a chance to become a source of chat spam if too many people are using it. The first Response is for a command that checks a user-inputted Overwatch player. This allows users to issue commands to check various Overwatch stats of an Overwatch player and comes in two flavors for you to pick from. The multi-queue has been working great now though with SMM2 viewer level submissions and I’ve just been informing users that any levels have to be submitted via Twitch chat.Description: Yes this is quite a block of text, but read it thoroughly as the overall concept is rather easy to understand. In the chance that a cloud based bot can work in the future with SMM2 level submissions, I am planning on continuing to use Botisimo or Cloudbot (should the timeout threshold get increased) which is the main reason I was curious to see why I couldn’t get Cloudbot to work initially. ![]() The main reason I looked into both of these bots to use with Warp World, as opposed to Nightbot or the like, is because I typically multi-stream to Twitch, YouTube, and Mixer and both Botisimo and Cloudbot allow you to integrate all 3 streaming services and commands together, thus making it easier for myself and users to submit levels from any platform. I just recently learned of Cloudbot, and saw it offered some additional features that Botisimo didn’t have, namely the ability for users to not be able to issue commands without having a set amount of loyalty points, which is why I thought I would attempt to see if Warp World commands would work with it. ![]() I had previously been using Botisimo for Warp World commands, since you helped last fall to get the commands working with it, and it has been working great. I did reach out to StreamLabs support again to see if they can up that timeout value, which I doubt they will do just for me, but I figured I might as well ask. ![]() I appreciate all of the help and fast replies on this! Thanks you! Outside of seeing the response after invoking certain commands, everything seems to be functioning normally. Commands such as !clears, !current, !list, !queue, !remove, and !stats. Other commands that users can invoke, always seem to get an immediate response with no “bad server response / too slow” message. This seems to be hit or miss where the !add, !replace, and !submit all seem to happen consistently with the “bad server response / too slow” message. However, I also have been able to run !close and the bot will reply with “Submissions are now closed!”. There are times where I will see “bad server response / too slow” response from the bot, even thought the queue did actually close. I’ve also noticed the same message, a few times, when I test the !close command. Streamlabs: That level was previously submitted! already beat it! Streamlabs: Sorry that level doesn’t seem to exist! Check your code again! It does also appear that if a user attempts to add a level that doesn’t exist or was previously submitted, that a typical response does happen: Wait until one of your levels is completed! Streamlabs: looks like you have reached the max amount of submissions. The user can also see this if they attempt re-enter their level code right after they see the bad server response / too slow message.) (However the level did go through and is in the actual queue. When a command is used to invoke a level code, commands such as !add, !replace, !submit, Cloudbot/Streamlabs replies with, however, when I check on the Warp World site, the command did actually execute successfully. I’m trying to use the following syntax for the !add command with Cloudbot:įrom my testing, all Warp World commands are executing correctly via Cloudbot/Streamlabs, however I am still noticing one issue. I was wondering if Warp World bot commands are compatible with Streamlabs Cloudbot ( )? ![]()
0 Comments
Leave a Reply. |