📢 PhantomBot v3.6.2.2 is now available as a stable build
✅ Added:
➡️ Nothing Added
🌀 Changed:
➡️ Nothing Changed
🛠️ Fixed:
➡️ Fixed clips API requests not working due to Twitch not following ISO and RFC standards (gmt2001)
➡️ Fixed WSClient/PubSub not handling fragmented frames that are sent when the data is large (gmt2001)
➡️ Fixed the PATH in the Docker images (gmt2001)
🗑️ Deprecated:
➡️ The OAuth page on https://phantombot.github.io now only provides a basic chat token for the bot account. After using this page to setup, please switch to automatically refreshing OAuth tokens from the bots built-in webserver http://localhost:25000/ (gmt2001)
➡️ com.gmt2001.HttpRequest is Deprecated and should not be used for new development. com.gmt2001.httpclient.HttpClient should be used instead
🛑 Removed:
➡️ Nothing Removed
🐞 Known Issues:
➡️ Due to the new Twitter API V2 not having some endpoints equivalent to the older V1 endpoints, some queries may use bot-side filtering, which could lead to the bot missing tweets if the target user sends/receives a high volume. This mostly affects retweet and mention detection
➡️ Autocomplete may still not work on some browsers when using the bot via localhost
🌐 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.
➡️ The Windows launch script supports the --nowt command line argument to force launching from Command prompt instead of switching to Windows Terminal