-
-
Notifications
You must be signed in to change notification settings - Fork 286
Twitch Integration
Lusamine edited this page Jul 4, 2020
·
17 revisions
Get a bot token from Twitch, fill out the twitch configuration fields, then start. You will need to define:
- Channel: The channel you will be streaming on; this is to tell your bot which channel to join & interact with.
- Username: The username of the bot account that will be interacting with your channel.
- Token: The login token for the bot account.
WARNING: Do not run the bot with credentials that are your own user (streaming) account.
- Twitch will warn you and suspend your main account if you are found to be self-botting.
- Create a separate bot account, and generate your login token for that bot.
In the Stream
settings, you will see the option to generate multiple files to be used as overlays:
- Trade Code Blocking Image: Creates a
block_{ip}.png
to be used as an overlay.- Without using these generated assets, you should consider putting a delay on your stream so that trade codes are not sniped. We recommend that you use these so that your viewers do not have a delayed viewing experience.
- Example: An IP address of
192.168.000.012
will beblock_192.168.0.12.png
, as leading zeroes are discarded. - The file is created when beginning to enter a trade code.
- The file is deleted when the trade code is no longer visible on the screen (either as a menu or dialog).
- You can provide a separate file to be copied (path), otherwise, the program will generate a black image for the overlay.
- To set up your overlay for each bot, create a temporary
png
at the expected path (listed above), and size it appropriately in OBS.
- On Deck: Users next in line
- On Deck 2: Users next in line (if you want two columns)
- User List: Users in queue (for scrolling text) -- not useful when running multiple bots.
- Queue Count: Count of how many users in queue.
- Bot Currently Handling text: Text to indicate which bot is handling which trainer.
The Twitch bot maintains a list of users waiting for a code. If a user requests twice before sending a bot the code, they can receive previously-requested Pokémon.