Announcement and thoughts about the future of InstructBot.
Here's a look at one of the changes coming in version 3.7 of InstructBot. It's an update to the UI to allow everything to scale correctly when your monitor isn’t set to scale everything to 100%. You can see that everything has sharpened up and the layout issues have been fixed.
Here is a first look at the new toggle profile command coming in version 3.7 of InstructBot. It's using the new workflow engine being designed for custom mini-games to handle potentially long running actions, e.g. the command could toggle a profile on or off for many minutes.
So whilst it's taken longer to complete than expected today version 3.6 has been released to the InstructBot testers. Below is an outline of what is coming in the new version, which has a target release date of the end of December.
Please note everything below is still subject to change based upon testing and feedback of my testers.
An update to allow you to assign the current value explicitly from within the UI, and a new setting to toggle if triggering amounts also increment the value.
Currently an application become active when a window with matching name is focused. This stops working when the window text changes as the game is play.
There has been added the ability to set a pattern so that if the application name changes in a predictable manor, it will still be detected.
E.g. if an application has a target window name of Game XX% where XX increments from 0 to 100 as you progress though the game, this could be handled as you could create a pattern to pick up Game 0%, Game 1%, Game 2% through to Game 100%.
There have been a number of changes including:
Adding alias, e.g. you could assign the identifier help, and then have alias of bot, bitbot etc... so a user in you chat can type !help or !bot or !bitbot.
Allow all key actions of an input command to use the generalised Alt, Ctrl and Shift keys, rather than specific Left Alt / Right Alt, Left Ctrl etc... as some game don't respond to the specific key and instead respond to the generalised one.
Allowing you to select a specific output device for individual play sound commands.
Being able to cancel a command which is running.
Keeping track of which keys and mouse buttons have been pressed in an input command, and then reversing them automatically when the command completes if not done explicitly by the command. For example if you have an input command with a Key Down W action, currently if that command completes without a corresponding Key Up W action, the key will remain pressed until you press it on your keyboard. The new tracker will now send a Key Up W action automatically when the input command finishes.
Letting the repeat action of an input command function over a given time period, e.g. 5 seconds / 10 seconds, as well as the ability to specify a delay between repetitions.
The ability to set the text output in the help command for the free, points and subscription triggers. For example you could change the default subscription output from Tier X Subscription to TX Sub.
Third Party Integrations
A re-work of how InstructBot connects to third parties has been implemented so that they are all independent, and can be connected / disconnected without affecting the other connections.
This means you'll no longer need to reconnect if, for example you enabled StreamElements whilst already connected. The connection to StreamElement will instead just happen.
It should also lead to an increase in visibility of when InstructBot is reconnecting, e.g. a new UI has been created to show when individual connection to Twitch Chat, Twitch PubSub, StreamElements etc... have been dropped and are reconnecting.
There have then been an update to some of the individual third parties.
Ability to take donations from TipeeeStream, e.g. as StreamElements / StreamLabs, has been added.
Migration from the V5 API which will be removed in February 2022 of the new Helix (V6) API.
I've uploaded a new tutorial video explaining how adding a points trigger works in InstructBot. It's the last in the series which has worked through all trigger types.
I've uploaded a new tutorial video explaining how adding a word trigger works in InstructBot. It's the eleventh in the series which will work through all trigger types.
I've uploaded a new tutorial video explaining how adding a timed trigger works in InstructBot. It's the tenth in the series which will work through all trigger types.
On the 8th of November at 9AM GMT I'm planning to upgrade the backend services of InstructBot.
The upgrade will be applied in two parts to keep the downtime to a minimum.
The first part will be an update to the core services and websites. This should be completed that morning and once done will enable InstructBot to run again with it's core functionality, e.g. login in, connecting to the various third parties, checking for updates, downloading installers etc... , meaning you'll be able to use the bot and websites again.
The second part will take significantly longer, a couple of days, as I clean the database. Whilst this is in progress you will not be able to share commands with other users or download commands you've previously created.
I've uploaded a new tutorial video explaining how adding a subscription trigger works in InstructBot. It's the ninth in the series which will work through all trigger types.
I've uploaded a new tutorial video explaining how adding a unban trigger works in InstructBot. It's the eighth in the series which will work through all trigger types.