Closed MihalicMarko closed 1 year ago
We dont support selfbots.
To the above, bearer does not imply self-botting, this is an irrelevant comment.
Could you go further into your use case, so I can attempt to repro?
May be related to #2381
Please follow up on the question above.
Hi, sorry, for the late reply, I was on vacation and forgot about it...
Regarding use-case: I was using it as an alternative to SignalR and developing the additional application (e.g. Guest comes to a Restaurant, joins Discord channel over QR code provided on that table, and calls waiter to his table...waiter can easily reply and owner can have some statistics regarding efficiency, favorite orders etc.) In the meantime, I've switched to TokenType.Bot and managed to solve my problem. I've used Bearer out of laziness (It's Standard and I didn't give too much thought about it + I didn't want to create and Setup a Bot Application) Didn't even know about selfbots before @Pusheon mentioned it so thx for the heads-up!
Regarding #2381 : It could be related, but mine was failing at Login, not at Calling other methods afterward (I'm not calling any except StartAsync) You should be able to reproduce the Bug with the Sample code I've provided above (You can remove logging to the file, shouldn't make any difference).
As I've mentioned v3.1.0 was working fine (except UserMessage didn't contain Content which was the reason why I've updated to v3.7.2), but all later versions were throwing the exception.
Hope that helps, be free to ask if you need any more information.
Ran into this as well. My use case is to register as applications rather than a bot and read from the gateway. Logging in as an application is only possible using a bearer token.
Check The Docs
Verify Issue Source
Check your intents
Description
After upgrading from v3.1.0. I've started receiving Exception when using the Bearer token to Login.
Version
3.7.2
Working Version
3.1.0
Logs
Sample
Packages
Discord.Net V3.7.2