Add guides to Concord about concord HOT 11 OPEN

I'll get most of these done, in addition to guides covering

• Concord on a VAX (with native SSL)
• Concord on Solaris 9
• SSL certificate pinning with libcurl and Concord
• Using Concord natively on Windows
• Windows SSL API

from concord.

You can do that with discord_update_presence(), here is an example for reference!

from concord.

Yeah then forget about that trick.. I assumed just filling up all uint64_t bits with 1 would work. Concord automatically sets the intent for you based on the events you want to listen to, but in case you still want to set the intents manually you can use an Intents Calculator and then enter that value to discord_add_intents().

from concord.

A question about a feature: how do I set a bot's status to do not disturb then back to online in C?

from concord.

Thanks. And, is there a way to enable all intents?

from concord.

discord_add_intents() will do the trick, you can find some of the predefined intents here. If you want to enable all intents you may simply pass it a UINT64_MAX flag from stdint.h (doesn't work)

from concord.

discord_add_intents() will do the trick, you can find some of the predefined intents here. If you want to enable all intents you may simply pass it a UINT64_MAX flag from stdint.h

It immediately fails with that trick for some reason.

All intents should be good on the website-end of things:

from concord.

It immediately fails with that trick for some reason.

You got some logs? (make sure to enable logging at your config.json)

from concord.

It immediately fails with that trick for some reason.

You got some logs? (make sure to enable logging at your config.json)

Logging does not seem to be working with running clang main.c -o myBot -pthread -ldiscord -lcurl; ./myBot. "quiet" is also set to false in the log.

Though, at least using strerror, I get Policy not found.

from concord.

It immediately fails with that trick for some reason.

You got some logs? (make sure to enable logging at your config.json)

Sorry, my bad; works differently than I thought.

23:06:06 WARN  discord-gateway.c:358: [DISCORD_GATEWAY] CLOSE DISCORD_GATEWAY_CLOSE_REASON_INVALID_INTENTS (code: 4013, 18 bytes): 'Invalid intent(s).'
23:06:06 WARN  discord-gateway.c:394: [DISCORD_GATEWAY] Gateway will not attempt to reconnect
23:06:06 WARN  discord-gateway.c:792: [DISCORD_GATEWAY] Discord Gateway Shutdown

from concord.

Yeah then forget about that trick.. I assumed just filling up all uint64_t bits with 1 would work. Concord automatically sets the intent for you based on the events you want to listen to, but in case you still want to set the intents manually you can use an Intents Calculator and then enter that value to discord_add_intents().

That seems to work; thank you. I also just found the Discord server link lol to ask there in the future.

from concord.