Unfortunately, I didn’t start from the chat, but from the classic “users” API (I guess everybody does the same) and I read the documentation and I realized that “New Twitch API” scopes are in the format “xxx:xxx:xxx” and “Twitch API v5” scopes are in the format “xxx_xxx”. So when I decided to implement the chat feature, of course I read that the only scope was “chat_login”, but I thought something was missing, because in my mind “xxx_xxx” scopes were for “Twitch API v5” API and I was using “New Twitch API”. So I looked at the scope tables and there was no “chat_login” scope for Helix API and I was pretty confused and here I am.
I read so many posts about people don’t uderstanding Kraken is the only “engine” for the authorization and I can tell you those table don’t help to clarify that. This is my feedback and I hope Twitch will improve the authorization documentation adding this precious information that IMHO could help other developers.