dc8e0e329d
* [Docs] Get docs working on latest docfx version. Removed light-dark-theme as it didn't work with modern docfx, and Material provides the features it provided anyways. Gotta figure out how to get the description generator and "last modified" plugins to work. * [Docs] Get docs working on latest docfx version. Removed light-dark-theme as it didn't work with modern docfx, and Material provides the features it provided anyways. Gotta figure out how to get the description generator and "last modified" plugins to work. * [Docs] Re-add search index extractor. * [Docs] Use material theme and override derived tree style. Also adds a tiny GitHub icon on the navbar. * [Docs] Exclude DebugTools project. * [Docs] Use better method for overriding things. Totally not because DocFX won't allow me to have an override template. * [Docs] Improve styling overrides. * [Docs] Fix links in FAQs and guides. * [Docs] Use new xref service. The old xref service is being deprecated by the end of the year. See https://github.com/dotnet/docfx/issues/8958 * [Docs] Replace (c) with proper copyright symbol. * [Docs] Fix formatting in docfx.json file. Thanks, VSCode. * [Docs] Remove non-working post processors. They don't work, and *personally* I feel like they're unnecessary considering you can check the last modification date in the (linked) GitHub page. I honestly have no idea what the other post processor does and honestly the code doesn't help much either. * [Docs] Fix "in this article" being too thin. Fixes https://github.com/discord-net/Discord.Net/pull/2778#issuecomment-1748812077 * [Docs] Get examples working again. * [Docs] Make properties be separated more clearly. * [Docs] Change docs index to reflect the new nightly MyGet feed. * [Docs] Get docs working on latest docfx version. Removed light-dark-theme as it didn't work with modern docfx, and Material provides the features it provided anyways. Gotta figure out how to get the description generator and "last modified" plugins to work. * [Docs] Get docs working on latest docfx version. Removed light-dark-theme as it didn't work with modern docfx, and Material provides the features it provided anyways. Gotta figure out how to get the description generator and "last modified" plugins to work. * [Docs] Re-add search index extractor. * [Docs] Use material theme and override derived tree style. Also adds a tiny GitHub icon on the navbar. * [Docs] Exclude DebugTools project. * [Docs] Use better method for overriding things. Totally not because DocFX won't allow me to have an override template. * [Docs] Improve styling overrides. * [Docs] Fix links in FAQs and guides. * [Docs] Use new xref service. The old xref service is being deprecated by the end of the year. See https://github.com/dotnet/docfx/issues/8958 * [Docs] Replace (c) with proper copyright symbol. * [Docs] Fix formatting in docfx.json file. Thanks, VSCode. * [Docs] Remove non-working post processors. They don't work, and *personally* I feel like they're unnecessary considering you can check the last modification date in the (linked) GitHub page. I honestly have no idea what the other post processor does and honestly the code doesn't help much either. * [Docs] Fix "in this article" being too thin. Fixes https://github.com/discord-net/Discord.Net/pull/2778#issuecomment-1748812077 * [Docs] Get examples working again. * [Docs] Make properties be separated more clearly. * [Docs] Change docs index to reflect the new nightly MyGet feed. * [Docs] Fix index image not switching when changing themes. Co-Authored-By: exsersewo <25526843+exsersewo@users.noreply.github.com> * add updated description generator postprocessor * update postprocessor * got it working * downgrade postprocessor docfx * [Docs] Add left margin to side navigation links. * remove dup docs cuz `<inheritdoc />` --------- Co-authored-by: exsersewo <25526843+exsersewo@users.noreply.github.com> Co-authored-by: Misha133 <mihagribkov133@gmail.com> Co-authored-by: Mihail Gribkov <61027276+Misha-133@users.noreply.github.com>
3.5 KiB
uid, title
| uid | title |
|---|---|
| Root.Landing | Home |
Discord.NET Documentation
What is Discord.NET?
Discord.Net is an asynchronous, multi-platform .NET Library used to interface with the Discord API.
Where to begin?
If this is your first time using Discord.Net, you should refer to the Intro for tutorials.
If you're coming from Discord.Net V2, you should refer to the V2 -> V3 guides.
More experienced users might want to refer to the API Documentation for a breakdown of the individual objects in the library.
Nightlies
Nightlies are builds of Discord.NET that are still in an experimental phase, and have not been released.
They are available through Discord.NET's MyGet feed.
Questions?
Frequently asked questions are covered in the FAQ. Read it thoroughly because most common questions are already answered there.
If you still have unanswered questions after reading the FAQ, further support is available on Discord.
Supporting Discord.Net
Discord.Net is an MIT-licensed open source project with its development made possible entirely by volunteers. If you'd like to support our efforts financially, please consider:
New in V3
Interaction Framework
A counterpart to the well-known command service of Discord.Net, the Interaction Framework implements the same feature-rich structure to register & handle interactions like application commands & buttons.
- Read about the Interaction Framework here
Slash Commands
Slash commands are purposed to take over the normal prefixed commands in Discord and comes with good functionality to serve as a replacement. Being interactions, they are handled as SocketInteractions. Creating and receiving slash commands is covered below.
- Find out more about slash commands in the Slash Command Guides
Context Message & User Commands
These commands can be pointed at messages and users, in custom application tabs. Being interactions as well, they are able to be handled just like slash commands. They do not have options however.
- Learn how to create and handle these commands in the Context Command Guides
Message Components
Components of a message such as buttons and dropdowns, which can be interacted with and responded to. Message components can be set in rows and multiple can exist on a single message!
- Explanation on how to add & respond to message components can be found in the Message Component Guides