Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot run "editor" level commands via chat. #446

Closed
BarryCarlyon opened this issue Jul 15, 2021 · 4 comments
Closed

Cannot run "editor" level commands via chat. #446

BarryCarlyon opened this issue Jul 15, 2021 · 4 comments
Labels
product: chat ticketed Has been given an internal tracking ticket

Comments

@BarryCarlyon
Copy link
Contributor

Brief description

I cannot run host/unhost/raid/unraid/commercial commands as a chat bot

This occurs if the authenticating user is the broadcaster or an editor of the channel.

It does work if you use the "old" channel_editor scope as I'm using this currently with some of my bots.

How to reproduce

  • Generate a user Token that has every helix API/"new" Chat scope on it
  • Connect a chat bot to chat
  • Try to run unhost in a channel;
  • recv "@msg-id=no_permission :tmi.twitch.tv NOTICE #flightsimtrack :You don't have permission to perform that action.\r"

test was done with every new scope to just test

Expected behavior

It unhost/host/raid/unraids

Additional context or questions

Sure /commercial has an API endpoint to call but host/raid does not.

@PalmettoBling
Copy link

Further confirmation that the old scope does resolve the issue, and current/modern scopes do not cover this situation.

@jbulava jbulava added the ticketed Has been given an internal tracking ticket label Jan 19, 2022
@jbulava
Copy link
Member

jbulava commented Jan 19, 2022

Updates have been deployed for the newer, equivalent scopes. I'll leave this ticket open until we add the scope definitions to the Scopes for IRC Commands section of the docs.

@BarryCarlyon
Copy link
Contributor Author

The "new chat docs" at https://dev.twitch.tv/docs/irc/chat-commands have the old scope. so not sure which scope is the true scope :-P

@BarryCarlyon
Copy link
Contributor Author

BarryCarlyon commented Nov 4, 2022

Issue no longer relevant since commands are no longer in chat. (Or soon enough won't be in chat)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product: chat ticketed Has been given an internal tracking ticket
Projects
None yet
Development

No branches or pull requests

3 participants