[Twitch] API Error: Bad Request; No client id... - 23/03/17 07:35 PM
EDIT: I'm an idiot, and forgot about the "search" feature...
Thanks anyway to anyone that was thinking about helping
It's been awhile since I've had to come on here. Mostly because once I got things going with my bot I was fine with what I had. And anything that "broke" was usually easily fixable. However, I recently decided to mess around with some old scripts I had and found this...
Now, if you don't know... It USED to show the username with the capital letters that the user had chosen using $twitchname($nick) etc...
(i.e.: username -> UserName rather than just all lowercase)
However, apparently something changed and now the link is leading to -> API Error: Bad Request; No client id specified
Any help would be greatly appreciated. This is the last thing I would like to fix up to make the command responses seem cleaner when the bot addresses the user that requested something. Thanks
Quote:
$msgtags(display-name).key
Thanks anyway to anyone that was thinking about helping
It's been awhile since I've had to come on here. Mostly because once I got things going with my bot I was fine with what I had. And anything that "broke" was usually easily fixable. However, I recently decided to mess around with some old scripts I had and found this...
Code:
alias twitchname { if ($hget(nickformat) == $null) { hmake nickformat } if ($hget(nickformat,$1)) { return $iif($hget(nickformat,$1) == $null,$1,$hget(nickformat,$1)) } var %json https://api.twitch.tv/kraken/users/ $+ $1 JSONOpen -ud nicename %json hadd nickformat $1 $json(nicename,display_name) return $iif($hget(nickformat,$1) == $null,$1,$hget(nickformat,$1)) }
Now, if you don't know... It USED to show the username with the capital letters that the user had chosen using $twitchname($nick) etc...
(i.e.: username -> UserName rather than just all lowercase)
However, apparently something changed and now the link is leading to -> API Error: Bad Request; No client id specified
Any help would be greatly appreciated. This is the last thing I would like to fix up to make the command responses seem cleaner when the bot addresses the user that requested something. Thanks