Commands cannot be added to User Token based auth
Closed this issue · 3 comments
Nivroc commented
Sorry for a stupid question - haskell beginner here)
Is this the intended behaviour?
I cannot pinpoint anywhere in the control flow when this gets turned on/off. The received messages are the same that means same Context could be built from them.
simmsb commented
Userbots are against Discord's ToS so I have no motivation to support the
slight differences between user and bot accounts (sharding, etc).
…On Fri, 3 Jul 2020, 09:15 Nivroc, ***@***.***> wrote:
Is this the intended behaviour?
I cannot pinpoint anywhere in the control flow when this gets turned
on/off. The received messages are the same that means same Context could be
built from them.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#26>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIVMDGSJB2QGB5IRFJX7GLRZWHQDANCNFSM4OPSZWNA>
.
simmsb commented
There's some code that has since been deleted that might work for using a
user token, but I have no idea if it works (and can't test it).
…On Fri, 3 Jul 2020, 13:50 Ben Simms, ***@***.***> wrote:
Userbots are against Discord's ToS so I have no motivation to support the
slight differences between user and bot accounts (sharding, etc).
On Fri, 3 Jul 2020, 09:15 Nivroc, ***@***.***> wrote:
> Is this the intended behaviour?
> I cannot pinpoint anywhere in the control flow when this gets turned
> on/off. The received messages are the same that means same Context could be
> built from them.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#26>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABIVMDGSJB2QGB5IRFJX7GLRZWHQDANCNFSM4OPSZWNA>
> .
>
Nivroc commented
Thanks for quick reply, thought so.