📢 PhantomBot v3.6.5.2 is now available as a stable build
⚠️ Due to upcoming changes by Twitch, IRC slash/dot commands are now moved to the Helix Twitch API. These new endpoints require new OAuth scopes by Twitch to function. Both the Bot and Broadcaster OAuths must be re-done after updating to v3.6.5.1 or later. This is also required for Purge/Timeout/Ban!
⚠️ The URL for the OAuth page has been normalized. If you are getting Parameter redirect_uri does not match registered URI, then you need to update the URI in your Twitch Developer Console. This is in step 1.6 of the OAuth instructions
✅ Added:
➡️ Nothing Added
🌀 Changed:
➡️ Updated the Rollbar filters to block sending some non-actionable errors (gmt2001)
🛠️ Fixed:
➡️ Fixed warning messages from chatModerator not being sent due to the method int TwitchSession.getWrites() not existing (gmt2001)
🗑️ Deprecated:
➡️ com.gmt2001.HttpRequest is Deprecated and should not be used for new development. com.gmt2001.httpclient.HttpClient should be used instead
➡️ tv.phantombot.PhantomBot.getProperties() is deprecated and should not be used for new development. tv.phantombot.CaselessProperties.instance() should be used instead
➡️ com.gmt2001.TwitchAPIv5 is Deprecated and should not be used for new development. tv.phantombot.twitch.api.Helix should be used instead
🛑 Removed:
➡️ Nothing Removed
🐞 Known Issues:
➡️ Twitter is Broken
🌐 Download It:
➡️ Downloads attached to the bottom of this release notice
❗ Remember to install to a separate folder, then copy over the config dir, as well as any custom scripts or files in addons
➡️ PhantomBot official builds are available on GitHub Container Registry at ghcr.io/phantombot/phantombot and ghcr.io/phantombot/nightly-build
➡️ PhantomBot official builds are available on DockerHub at gmt2001/phantombot-stable and gmt2001/phantombot-nightly. See the readme text on the appropriate Docker Hub pages for Docker Compose files
🗒️ Notes:
➡️ We have guides on PhantomBot. You can contribute by submitting a Pull Request adding or editing .md files in the /docs/guides/content folder of the repo. See the guides for info about formatting.
➡️ $.inidb.executeSql is designed for personal, custom script use where the DataStore backend being used is known and will not change. Issues can, and will, occur if the SQL is written for one DataStore backend and the statement is then executed on a different backend.