Deep Bot - Twitch Streamer Assistant
Deep Bot => Bug Reports => Topic started by: EvilSqueegee on July 12, 2015, 07:41:10 PM
-
Bug: Before this recent patch which fixed up bot/admin permissions in command chains, the @user@ variable from latter commands in a command chain was passed to them by the former commands in that command chain.
If a user triggered !command1, and command1 triggered command2 either through the text output field or through the command-chain box, then the bot would set off !command2 with the initial user as the @user@ variable.
Since this most recent patch, however, all 2ndary commands in the command chain are treating the bot as if it was the @user@.
I noticed this because I have several minigames I run in my channel, where !commands trigger random lists fo other !commands which then alter currencies and/or timeout users:
!dungeon triggers !dunwin1, !dunlose1. Dunwin1 outputs a random flavor text and then chains to a command which gives the user bonus currency. Dunlose1 posts a message, then chains to a command which posts a death message and costs them currency.
However, these chat games now always treat the bot as the player: When someone !dungeons, the !dunwin1 or !dunlose1 (which have always used @user@) now target the bot.
I asked in Streamer Chat and was told that this is actually a bug and not the intended functionality. Therefore I am posting here!
-
still works as it should
(http://puu.sh/iWhCS/c07a8fedc1.png)
-
If you want, you can pm me screenshots of your commands so i can take a look at them.
-
I know why you and I are getting different results. It's because I'm using the randomized line output for commands.
!command1 has the following lines:
!subcom1
!subcom2
!subcom3
!subcom4
That way it randomly selects the !command and executes it. Previous to patch, @user@ propogated like this. THAT may have been the bug, all I know is that it's not functioning now the way it was before this update.
Screenshots: i.imgur.com/SJqVUK4.png // i.imgur.com/1jPuBcG.png
-
That's because you are running one of the commands as the bot.
-
You are correct, I did have some of the commands to run as bot. I have set these commands to run as User, however, and this did not alter the @user@ propogation behavior I am experiencing.
-
Mind taking a screenshot of one of your commands like all the way thru?