youys
/
Discord.Net
Not watched
1
0
Fork 0
Code
Releases 34 Wiki Activity
Issues 0 Pull Requests 0 Datasets Model Cloudbrain
You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree: 34361fa64a
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '34361fa64a'
${ noResults }
Discord.Net/docs/guides/intro.md

2.0 kB
Raw Blame History

Getting Started

Requirements

Discord.Net supports logging in with all variations of Discord Accounts, however the Discord API reccomends using a Bot Account.

You may register a bot account here.

Bot accounts must be added to a server, you must use the OAuth 2 Flow to add them to servers.

Installation

You can install Discord.Net 1.0 from our MyGet Feed.

For most users writing bots, install only Discord.Net.WebSocket.

You may add the MyGet feed to Visual Studio directly from https://www.myget.org/F/discord-net/api/v3/index.json.

You can also pull the latest source from GitHub.

[!WARNING]
The versions of Discord.Net on NuGet are behind the versions this
documentation is written for.
You MUST install from MyGet or Source!

Async

Discord.Net uses C# tasks extensiely - nearly all operations return
one.

It is highly reccomended these tasks be awaited whenever possible.
To do so requires the calling method to be marked as async, which
can be problematic in a console application. An example of how to
get around this is provided below.

For more information, go to MSDN's Async-Await section.

First Steps

[!code-csharpMain]

[!NOTE]
In previous versions of Discord.Net, you had to hook into the Ready and GuildAvailable events to determine when your client was ready for use.
In 1.0, the ConnectAsync method will automatically wait for the Ready event, and for all guilds to stream. To avoid this, pass false into ConnectAsync.