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 kommentar(er)
