dfx 0.0.1

package/discord-api-docs/docs/dispatch/Error_Codes.md

@@ -0,0 +1,26 @@
+# Error Codes
+
+> info
+> Need help with Dispatch? Talk to us in the [Discord Developers Server](https://discord.gg/discord-developers)!
+
+This page outlines some of the common errors codes that may be encountered when using Dispatch.
+
+| Code | Name                       | Possible Solution                                                                                                                              |
+| ---- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| 2020 | Request Signing Failed     | Check user entitlement                                                                                                                         |
+| 2022 | Disk Space Low             | Free up disk space                                                                                                                             |
+| 2023 | Disk Permission Denied     | Choose a new location, or change write permissions on desired location                                                                         |
+| 2024 | Uninstall Failed           | Attempt to manually remove game files from disk                                                                                                |
+| 2025 | Install Script Failed      | Restart Discord, attempt to uninstall/reinstall the game, ensure script is correct                                                             |
+| 2029 | Build Not Found            | Completely close and re-open Discord                                                                                                           |
+| 2051 | Panic!                     | Escalate in the dev server in #dispatch                                                                                                        |
+| 2058 | Too Many API Retries       | Escalate in the #dispatch channel of the [Discord Developers server](https://discord.gg/discord-developers)                                    |
+| 2059 | Failed to set Registry Key | User most likely denied Windows administrator permissions prompt. Try again, and accept the prompt                                             |
+| 2064 | Failed to Patch File       | Attempted to patch the game while running: ensure the game process is entirely ended, try restarting Discord, try disabling antivirus          |
+| 2065 | No Manifests               | Ensure that your manifests are properly selected in the Developer Portal for your SKU                                                          |
+| 2069 | API Error                  | Intermittent API issues. Wait, escalate to #dispatch in the dev server if it persists                                                          |
+| 2070 | Bad Response               | Intermittent API issues. Wait, escalate to #dispatch in the dev server if it persists                                                          |
+| 2073 | Not Entitled               | Check that your manifests are properly configured in the Developer Portal. Have the user install the game from the Library, not the store page |
+| 2076 | Two Clients Patching       | User has multiple Discords open trying to patch the same game; only use one                                                                    |
+| 9001 | Unknown                    | Catch-all error code. Escalate to #dispatch in dev server with repro steps/as much info as possible                                            |
+

package/discord-api-docs/docs/dispatch/Field_Values.md

@@ -0,0 +1,48 @@
+# Predefined Field Values
+
+> info
+> Need help with Dispatch? Talk to us in the [Discord Developers Server](https://discord.gg/discord-developers)!
+
+## Manifests
+
+###### Platform Values
+
+| Platform |
+| -------- |
+| macos    |
+| win32    |
+| win64    |
+| linux    |
+
+###### Redistributable values
+
+| Redistributable            |
+| -------------------------- |
+| directx_june_2010          |
+| vcredist_2005_x86          |
+| vcredist_2008_sp1_x86      |
+| vcredist_2010_x64          |
+| vcredist_2010_x86          |
+| vcredist_2012_update_4_x64 |
+| vcredist_2012_update_4_x86 |
+| vcredist_2013_x64          |
+| vcredist_2013_x86          |
+| vcredist_2015_x64          |
+| vcredist_2015_x86          |
+| vcredist_2017_x64          |
+| vcredist_2017_x86          |
+| xnafx_40                   |
+
+###### Cloud Save Path Replacements
+
+| value            | Windows path                                                                        | macOS path                    | linux path          |
+| ---------------- | ----------------------------------------------------------------------------------- | ----------------------------- | ------------------- |
+| \${HOME}         | %USERPROFILE%                                                                       | ~/                            | ~/                  |
+| \${DOCUMENTS}    | %USERPROFILE%\Documents                                                             | ~/Documents                   | \$XDG_DOCUMENTS_DIR |
+| \${DATA}         | %USERPROFILE%\AppData\Roaming                                                       | ~/Library/Application Support | \$XDG_DATA_HOME     |
+| \${DATALOCAL}    | %USERPROFILE%\AppData\Local                                                         | ~/Library/Application Support | \$XDG_DATA_HOME     |
+| \${DATALOCALLOW} | %USERPROFILE%\AppData\LocalLow                                                      | ~/Library/Application Support | \$XDG_DATA_HOME     |
+| \${SAVEDGAMES}   | %USERPROFILE%\Saved Games                                                           | (not supported)               | (not supported)     |
+| \${INSTALLDIR}   | the game's install directory                                                        | (same)                        | (same)              |
+| \${USERID}       | the user's id - use within a path to define saves for multiple users                | (same)                        | (same)              |
+| \${BRANCHID}     | the id of the game branch - use within a path to define saves for multiple branches | (same)                        | (same)              |

package/discord-api-docs/docs/dispatch/List_of_Commands.md

@@ -0,0 +1,315 @@
+# List of Commands
+
+> info
+> Need help with Dispatch? Talk to us in the [Discord Developers Server](https://discord.gg/discord-developers)!
+
+Some people don't like to read full pages of documentation. Personally, I think those people are missing out. But we want to make sure that we cater to everyone, so here's a list of every Dispatch command and what it does. No frills, no jokes. Okay, maybe some jokes.
+
+## login
+
+Authorizes you to do these things!
+
+###### Arguments
+
+None
+
+###### Example
+
+```
+-> dispatch login
+[2018-09-17][15:26:15][INFO] Already logged in
+```
+
+## branch create
+
+Creates a new branch. If you have not yet made a master branch, this command will also automatically create a master branch.
+
+###### Arguments
+
+| name           | values | description                   |
+| -------------- | ------ | ----------------------------- |
+| application_id | int    | your application ID/client ID |
+| branch_name    | string | the name for your new branch  |
+
+###### Example
+
+```
+-> dispatch branch create 290926444748734465 "test"
+Branch created with id 491362538965958686
+```
+
+## branch delete
+
+Deletes a branch.
+
+###### Arguments
+
+| name           | values | description                    |
+| -------------- | ------ | ------------------------------ |
+| application_id | int    | your application ID/client ID  |
+| branch_id      | int    | the id of the branch to delete |
+
+###### Example
+
+```
+-> dispatch branch delete 290926444748734465 491362538965958686
+```
+
+## branch list
+
+Lists all branches for an application.
+
+###### Arguments
+
+| name           | values | description                   |
+| -------------- | ------ | ----------------------------- |
+| application_id | int    | your application ID/client ID |
+
+###### Example
+
+```
+-> dispatch branch list 290926444748734465
+|    APPLICATION ID    |      BRANCH ID       |         NAME         |    LIVE_BUILD_ID     |           CREATED AT           |
+| -------------------- | -------------------- | -------------------- | -------------------- | ------------------------------ |
+|  290926444748734465  |  471164707759996234  |  master              |                      |  2018-07-24 04:00:20.146588Z   |
+```
+
+## branch promote
+
+Promotes the live build of one branch to another.
+
+###### Arguments
+
+| name             | values | description                       |
+| ---------------- | ------ | --------------------------------- |
+| application_id   | int    | your application ID/client ID     |
+| branch_id        | int    | the id of the branch to promote   |
+| target_branch_id | int    | the id of the branch to overwrite |
+
+###### Example
+
+```
+-> dispatch branch promote 290926444748734465 471164707759996234 491362538965958686
+```
+
+## build delete
+
+Deletes a build from a branch.
+
+###### Arguments
+
+| name           | values | description                   |
+| -------------- | ------ | ----------------------------- |
+| application_id | int    | your application ID/client ID |
+| build_id       | int    | the id of the build to delete |
+
+###### Example
+
+```
+-> dispatch build delete 290926444748734465 491362538965958686
+```
+
+## build drm-wrap
+
+Wraps your executable in Discord's DRM. This only works for Windows executables. If you want to DRM wrap a unix executable, you'll need to instead use [ValidateOrExit](#DOCS_GAME_SDK_APPLICATIONS/validateorexit).
+
+> danger
+> This action is destructive and overwrites the executable. Make sure you've got a backup handy if needed!
+
+###### Arguments
+
+| name               | values    | description                                                                        |
+| ------------------ | --------- | ---------------------------------------------------------------------------------- |
+| application_id     | int       | your application ID/client ID                                                      |
+| path_to_executable | file path | the path to the executable, either explicit or relative to the dispatch executable |
+
+###### Example
+
+```
+-> dispatch build drm-wrap 290926444748734465 C:\my-game\my-game.exe
+```
+
+## build list
+
+Lists the builds available on the given branch.
+
+###### Arguments
+
+| name           | values | description                   |
+| -------------- | ------ | ----------------------------- |
+| application_id | int    | your application ID/client ID |
+| branch_id      | int    | the id of the branch to check |
+
+###### Example
+
+```
+-> dispatch build list 290926444748734465 491362538965958686
+|    APPLICATION ID    |       BUILD ID       |        STATUS        |   CREATION BRANCH    |           CREATED AT           |
+| -------------------- | -------------------- | -------------------- | -------------------- | ------------------------------ |
+|  290926444748734465  |  489230031839821824  |        READY         |        master        |  2018-09-12 00:25:29.045554Z   |
+|  290926444748734465  |  479469321974841354  |        READY         |        master        |  2018-08-16 01:59:54.481336Z   |
+```
+
+## build publish
+
+Marks a given build as the live build for a given branch.
+
+###### Arguments
+
+| name           | values | description                    |
+| -------------- | ------ | ------------------------------ |
+| application_id | int    | your application ID/client ID  |
+| branch_id      | int    | the id of the branch to check  |
+| build_id       | int    | the id of the build to publish |
+
+###### Example
+
+```
+-> dispatch build publish 290926444748734465 491362538965958686 489230031839821824
+```
+
+## build push
+
+Pushes a new build to the given branch. The JSON config file tells Dispatch how to organize the files and which to push relative to the `application_root`.
+
+###### Arguments
+
+| name             | values    | description                                                                                           |
+| ---------------- | --------- | ----------------------------------------------------------------------------------------------------- |
+| branch_id        | int       | the id of the branch to check                                                                         |
+| config_file      | filename  | the [JSON config file](#DOCS_DISPATCH_BRANCHES_AND_BUILDS/setting-up-our-first-build) for the build   |
+| application_root | file path | the directory that dispatch will treat as the local root for operations—`.` for the current directory |
+| -c               | flag      | forces a re-chunk of files even if the edited file timestamp hasn't changed                           |
+| -p               | flag      | automatically publishes the build if push is successful                                               |
+
+###### Example
+
+```
+-> dispatch build push 491362538965958686 config.json . -c -p
+```
+
+## build update
+
+Downloads the build for the given application id and branch id to the given install path, for the given platform and locale.
+
+`install_path` can be any file path on your machine to download the build to.
+
+###### Arguments
+
+| name           | values                                                            | description                    |
+| -------------- | ----------------------------------------------------------------- | ------------------------------ |
+| application_id | int                                                               | your application ID/client ID  |
+| branch_id      | int                                                               | the id of the branch to check  |
+| install_path   | file path                                                         | the path to install to         |
+| --platform     | [platform](#DOCS_DISPATCH_FIELD_VALUES/manifests-platform-values) | the build platform to download |
+| --locale       | [locale](#DOCS_REFERENCE/locales)                                 | the build locale to download   |
+
+###### Example
+
+```
+-> dispatch build update 290926444748734465 491362538965958686 C:\my-game --platform win64 --locale en-US
+```
+
+## build corrupt
+
+Mark a build as corrupted.
+
+###### Arguments
+
+| name           | values | description                    |
+| -------------- | ------ | ------------------------------ |
+| application_id | int    | your application ID/client ID  |
+| build_id       | int    | the id of the build to corrupt |
+
+###### Example
+
+```
+-> dispatch build corrupt 290926444748734465 491362538965958686
+Corrupted build "491362538965958686"
+```
+
+## build preview-files
+
+Displays a preview of the install paths that a build will put files in, for a given platform/locale. Additionally, will show which files are considered user data.
+
+###### Arguments
+
+| name             | values                                                            | description                                                                                           |
+| ---------------- | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| config_file      | filename                                                          | the [JSON config file](#DOCS_DISPATCH_BRANCHES_AND_BUILDS/setting-up-our-first-build) for the build   |
+| application_root | file path                                                         | the directory that dispatch will treat as the local root for operations—`.` for the current directory |
+| --locale         | [locale](#DOCS_REFERENCE/locales)                                 | the build locale to preview                                                                           |
+| --platform       | [platform](#DOCS_DISPATCH_FIELD_VALUES/manifests-platform-values) | the build platform to preview                                                                         |
+
+###### Example
+
+```
+-> build preview-files config.json . --locale en-US --platform win64
+```
+
+## build repair
+
+Repairs an application build.
+
+###### Arguments
+
+| name             | values                                                           | description                                                                                           |
+| ---------------- | ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| application_id   | int                                                              | your application ID/client ID                                                                         |
+| branch_id        | int                                                              | the id of the branch to check                                                                         |
+| build_id         | int                                                              | the id of the build to repair                                                                         |
+| application_root | file path                                                        | the directory that dispatch will treat as the local root for operations—`.` for the current directory |
+| --platform       | [platform](#DOCS_DISPATCH_FIELD_VALUES/manifests-platform-values) | the build platform to repair                                                                          |
+
+###### Example
+
+```
+-> build repair 290926444748734465 491362538965958686 489230031839821824 . --platform win64
+```
+
+## build run-launch-setup
+
+Runs the launch setup for an application.
+
+###### Arguments
+
+| name             | values                                                           | description                                                                                           |
+| ---------------- | ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| application_root | file path                                                        | the directory that dispatch will treat as the local root for operations—`.` for the current directory |
+| --platform       | [platform](#DOCS_DISPATCH_FIELD_VALUES/manifests-platform-values) | the build platform to do the launch setup                                                             |
+
+###### Example
+
+```
+-> build run-launch-setup . --platform win64
+```
+
+## completions generate
+
+Generations shell command completions; run `dispatch completions --help` for more info, as it varies by shell
+
+###### Example
+
+```
+-> dispatch completions generate --help
+```
+
+## manifest-label list
+
+Lists created manifest labels. These labels are created from the JSON config file when pushing builds.
+
+###### Arguments
+
+| name           | values | description                   |
+| -------------- | ------ | ----------------------------- |
+| application_id | int    | your application ID/client ID |
+
+###### Example
+
+```
+-> dispatch manifest-label list 290926444748734465
+|    APPLICATION ID    |          ID          |         NAME         |
+| -------------------- | -------------------- | -------------------- |
+|  290926444748734465  |  471165178650999608  |        my-game       |
+|  290926444748734465  |  471169990397324288  |      my-game-dlc     |
+```

package/discord-api-docs/docs/game_and_server_management/Alpha_and_Beta_Testing.md

@@ -0,0 +1,52 @@
+# Alpha and Beta Testing
+
+Alphas and betas are a critical part of a game's development lifecycle. We understand the value of getting feedback early and often and involving your community early on. That's why we've built some awesome alpha and beta testing functionality for you!
+
+## Beta Entitlements
+
+As you develop your game, you'll constantly be making improvements. You want real-time feedback from players, and there's no better place for that than Discord. In the past, players would need to dig through menus to find out how to unlock test branches, as well as remembering secret passwords _and_ typing them in correctly. Was that an `I` or an `l`? `O` or `0`?
+
+One of the cool features of [Store Channels](#DOCS_GAME_AND_SERVER_MANAGEMENT_SPECIAL_CHANNELS/) is their ability to grant a Beta Entitlement for your game. That means that while you keep your master branch safe and sound, users can test on `beta-branch-please-ignore-bugs` in an isolated test environment.
+
+> info
+> To learn more about creating branches, start with [Dispatch and You](#DOCS_DISPATCH_DISPATCH_AND_YOU/).
+
+When you create a store channel in your server, you'll be prompted with a choice to make it a Beta channel. That will allow you to grant users entitlement to the non-master branch of your game when visiting the store page. When your beta period is over and your game is ready for release and purchase, you can brick/delete these branches if you choose, and prompt users to get the full game by putting up a new store channel that's not Beta.
+
+> warn
+> Beta branches cannot be sold. If a user has access to a store channel for a beta entitlement, they will be able to claim it for free.
+
+## Role-Based Entitlement
+
+So, you've started getting a bunch of fans into your server. Hundreds, thousands, millions! Uh, if you hit millions, let us know. Within your hordes of adoring fans lies your Trusted Testing Group (tm), the best of the best when it comes to feedback. Maybe you want to give them access to a special `insider-only-private-beta` branch of your game. You can, with role-based entitlement!
+
+Store channels in Discord are just like any other channel in that they can have a set of permissions applied to them. What is special about them is that if they are set as a Beta branch, entitlement to that branch is tied to having permissions to view the channel. So, all your testers with a `Beta Tester` role, for example, will be able to get entitlement to the `insider-only-private-beta` branch. And, if they are later removed from that role, entitlement from that branch will be removed.
+
+A scenario might look like this: you create a Beta store channel. Only users with role `Awesome Tester` can view it. Player A is an `Awesome Tester`. They can view the channel and get entitlement to the beta branch. Player A becomes inactive; you remove them from the `Awesome Tester` role. Player A loses entitlement to `insider-only-private-beta`
+
+> danger
+> Role-based entitlement will only work if you use Discord's DRM, which is a simple entitlement check. You can do that with the Dispatch command [`dispatch build drm-wrap`](#DOCS_DISPATCH_LIST_OF_COMMANDS/build-drmwrap) or by calling [`ApplicationManager.ValidateOrExit()`](#DOCS_GAME_SDK_APPLICATIONS/validateorexit). Otherwise, Discord will not check the user's entitlement when the game starts.
+
+Role-based entitlements help keep your beta community active and interactive, while also providing a way to reward your biggest fans with secret access to special things.
+
+## Gift Codes
+
+> warn
+> Note that only Approved Games can generate gift codes.
+
+If you want to push out access to your game at scale, rather than inviting people into your server and giving them a role, you can create gift codes in the Developer Portal! Gift codes are like game keys on other platforms that you might be familiar with, with an added bonus: the ability to specify the entitlement time window. That means that you can create codes for your game to give to everyone, but they won't be able to play until the `VALID FROM` date. Similarly, you can set a `VALID UNTIL` date on all your gift codes if you want the entitlements to expire after a certain time, removing access from players.
+
+Note that the `VALID UNTIL` date will not remove the game from the user's library, but they will no longer be able to launch it.
+
+Up to 25,000 gift codes can be created at a time. When you go to create gift codes, you'll notice there are a few fields for you to fill out. Here's what they mean:
+
+![Screenshot of the modal to create gift codes with on the developer dashboard](gift-code-creation.png)
+
+- SKU: the SKU that you want the user to get
+- Branch: the branch of your game you want the user to get
+- Valid From: the start date at which the entitlement is valid
+- Valid Until: the date at which the entitlement is no longer valid
+- Amount: the number of codes you want to create (up to 25,000 per batch)
+- Description: a short description of why you made the codes, so you remember!
+
+Once you've made your codes, you can download the `.csv` that has them all in it, and distribute them however you'd like!

package/discord-api-docs/docs/game_and_server_management/How_to_Get_Your_Game_on_Discord.md

@@ -0,0 +1,110 @@
+# How to Get Your Game on Discord
+
+> danger
+> Selling SKUs on Discord is now deprecated, and will be discontinued on March 1, 2022. [Read here for more info.](https://support-dev.discord.com/hc/en-us/articles/4414590563479)
+
+Welcome, adventurer! If you're here, you want to find out how to get your game up and running on Discord and learn about our awesome Server Commerce features. You've come to the right place, so let's get started.
+
+## Get the Band Back Together
+
+First things first: it's time to make a Team. Your dream team of artists, writers, engineers, designers, all working on the beautiful creation of Your Game. Build your dream team with these steps:
+
+1. Create a new Team at [https://discord.com/developers/teams](https://discord.com/developers/teams)
+2. Invite people!
+
+You've now passed the first test with flying colors!
+
+## Apps and Games
+
+Throughout this process, we'll reference your "app". An app, or application, is an entity on Discord that represents something you've built: a bot, an OAuth2 app, or in this case your game. We need to make an app for your game:
+
+1. Create a new app at [https://discord.com/developers/applications](https://discord.com/developers/applications)
+2. When doing so, make sure you select your team from the `Team` dropdown
+
+> info
+> All apps on Discord for games must be owned by a team. If you accidentally made a personal app, you can transfer it to a team at any time by hitting the `Transfer App to Team` button within the app.
+
+You're now looking at a blank slate of creativity. Give your game a pretty icon and exciting description here. Next, click on `Server Commerce Checklist` in the sidebar, and we'll get to the good stuff.
+
+## Join the Club
+
+From here on forward, we'll be managing settings that tie directly to your game and its presence on Discord. We want to make sure that we're laser-focused on making the best experience possible for game developers, so we ask that you pay our Application License Fee in order to get access to our store tools, which let you:
+
+- make store pages for your game directly in your server
+- run alpha and beta tests for your game, using the magic of channel permissions to create role-based page access
+- apply for approval, letting you start making money (if you want to)
+
+Now that we've weeded out the trolls, let's get your server up and running with some fancy new features!
+
+## Your Server - Your Kingdom
+
+You're now looking at a checklist with a bunch of items and a prompt to select a server. Your Application License Fee entitles you to the following features in your server:
+
+- store channel creation
+- alpha and beta testing
+
+Select the server that you wish to grant these features, confirm to be double-extra-super-sure, and poof! You can now create channels for both news and store pages in your server. To learn more about store page channels, read [Store Channels](#DOCS_GAME_AND_SERVER_MANAGEMENT_SPECIAL_CHANNELS/store-channels). To learn more about Announcement Channels, read [Announcement Channels](#DOCS_GAME_AND_SERVER_MANAGEMENT_SPECIAL_CHANNELS/announcement-channels). To learn about alpha and beta testing, read [Alpha and Beta Testing](#DOCS_GAME_AND_SERVER_MANAGEMENT_ALPHA_AND_BETA_TESTING/)
+(you get the gist).
+
+Now, what do you do next? You start building! Build your community, make your game, invite testers into your server to get hype! Now is a great time to get familiar with all the tools at your disposal like:
+
+- [Discord's Developer Portal](https://discord.com/developers/applications), your one-stop-game-management-shop
+- [The Discord Game SDK](#DOCS_GAME_SDK_SDK_STARTER_GUIDE/), a spellbook full of useful game dev incantations including Discord's crystal-clear voice chat
+- [Dispatch](#DOCS_DISPATCH_DISPATCH_AND_YOU/), Discord's game patcher and downloader that's so fast, you'll swear it's magic
+
+To guide you through this process to success, you can follow that handy checklist. It'll tell you the steps you need to complete, show you where and how to do them, and give you a blissful sense of satisfaction as the green check marks pile up.
+
+The next and final step in your on-boarding journey is getting approved. Once approved, you'll be able to start making money (or karma), and you'll unlock a ton of cool server customization features to make your kingdom cozy for your players.
+
+## Testing Your Game
+
+As you go through the process of building your game and getting it ready for release on Discord, you'll want to be able to test it! One way to do so is to utilize Beta Store channels, which you can learn more about here: [Alpha and Beta Testing](#DOCS_GAME_AND_SERVER_MANAGEMENT_ALPHA_AND_BETA_TESTING/).
+
+If you are on the Team that owns the game, you can also use another special system for testing that we call Application Test Mode. Test Mode allows you to purchase unavailable, unlisted SKUs for free, making it helpful for testing IAP flows. It also automatically makes every branch of your game show up in your Library when Test Mode is turned on. You can read more here: [Application Test Mode](#DOCS_GAME_SDK_STORE/application-test-mode).
+
+## Getting Approved
+
+Your game looks wonderful. You've got a beautiful store page, and awesome game, and an eager community. It's time to get approved and plant your flag. Note that if your game is in an alpha or beta state, or you're interesting in Early Access, you are welcome to apply for approval whenever you are ready. Your game doesn't need to be the finished 1.0 version; give us something you'd feel comfortable giving to your players.
+
+Once you've completed all the items on your checklist, the `Get Approved` button will unlock. Once you submit for approval, Discord will take a look at the following things:
+
+- your game, to ensure that it runs properly and follows our [Game Submission Guidelines](https://support-dev.discord.com/hc/en-us/articles/360025028592-Game-Submission-Guidelines)
+- your store pages, to provide helpful guidance in putting your best foot forward
+- your server, to make sure you're abiding by our [Community Guidelines](https://discord.com/guidelines)
+
+If we need to see some changes, you'll receive an email directing you on your steps to success. Otherwise, you'll get **APPROVED!!!!!!!!!!** What's that mean? It means you can start charging for your game and making money! Don't spend it all in one place. Or do. Treat yourself. Or maybe you want your game to be **free!** Live your best life. We support you!
+
+## Available vs Store Page Published
+
+Now that you've been approved, there's a couple new toggles to flip in the Developer Portal: `Available`, and `Store Page Published`.
+
+![Screenshot of the SKU information page with the "available" and "store page published" switches highlighted](available-published.png)
+
+`Available` means that your game is now available for normal purchase/distribution; your non-beta store channel will no longer say `Coming soon!` when this is toggled, and users will be able to get your game.
+
+> danger
+> Toggling your SKU as `Available` will make it available for purchase; make sure your price is set properly!
+
+If you no longer wish to make your SKU available for sale, you can again mark it unavailable. This will not remove it from users' libraries; it just stops new users from purchasing it.
+
+`Store Page Published` will do...well, what it says! Though your store page is always visible from within the channel in your server, there are other things that require you to explicitly mark your page viewable from outside that context, like gift code embeds for your game, or from in-game store fronts!
+
+TL;DR - When you're ready to distribute your game after getting approved, turn those two toggles on.
+
+## Getting Verified and Discovered
+
+Apart from being approved, you can also get your server Verified. Getting verified means your server will get that oh-so-exclusive checkmark, to let people know you're the legit home for your game. 
+
+To get verified, head on over to our [Verification page](https://discord.com/verification) and fill out the form at the bottom.
+
+## Make Good Decisions
+
+Your game is off and running, and we couldn't be more proud. As it flourishes and your playerbase grows, keep an eye on your analytics, which you can find within your app. They'll give you important insight like revenue data, acquisitions funnels, and player retention to help you make informed decision about your game's lifecycle. Check out our [Analytics Help Article](https://support-dev.discord.com/hc/en-us/articles/360024852152) to learn more about how to read all those charts, and how to do things like [Conversion Tracking with UTM Links](https://support-dev.discord.com/hc/en-us/articles/360025153051-How-to-track-conversions-with-UTM-links).
+
+## What Comes Next
+
+Your game's success is in your own hands now. Continue to build your community and keep them informed with updates. Consider integrating more deeply with Discord to deliver cool features to your players; we recommend [Rich Presence Game Invites](#DOCS_GAME_SDK_ACTIVITIES/). They feel like magic. Drop new content by creating DLC and IAP for your game, run fun tournaments based on [HypeSquad Membership](#DOCS_GAME_SDK_USERS/currentuserhasflag), give something cool to [Discord Nitro Subscribers](#DOCS_GAME_SDK_USERS/getcurrentuserpremiumtype) because they're awesome. Or maybe, just maybe, think about your next upcoming game?
+
+We'd love to help you with that one, too.
+
+-- Discord <3

package/discord-api-docs/docs/game_and_server_management/Special_Channels.md

@@ -0,0 +1,38 @@
+# Store Channels
+
+> danger
+> Selling SKUs on Discord is now deprecated, and will be discontinued on March 1, 2022. [Read here for more info.](https://support-dev.discord.com/hc/en-us/articles/4414590563479)
+
+
+One of the new flagship features of Verified Servers and Game Servers are the ability to host your store pages directly in your server. We know that community is everything for games, and that your server is already the place where your community lives. Rather than the friction and impersonality of traditional storefronts, you can let your fans find your game in the cozy comfort of their home (your server!).
+
+In order to create a store channel for your game, you'll need to make sure you've followed [the Walkthrough](#DOCS_GAME_AND_SERVER_MANAGEMENT_HOW_TO_GET_YOUR_GAME_ON_DISCORD/) up to `Getting Approved`. If you've done that, you'll see in your server that you can create a new channel type: `Store`.
+
+![Screenshot of the modal to create a new Store Channel](create-store-channel.png)
+
+Along with entering a name for your new channel, you'll be prompted to select an application. This should be the app you created when you started; it's the one linked to your server. After selecting your app, you'll be prompted to select a SKU. What's a SKU? A SKU is simply a thing that a user can buy. This is most likely your game (a SKU of type `Game`), but could also be `IAP`, `DLC`, or a `Bundle`.
+
+You can create SKUs to put up for sale by going to your app and selecting `SKU Management`.
+
+![Screenshot of the SKU Management dashboard](sku-management.png)
+
+Once you select your SKU and create your channel...it's there! You now have a store channel in your server! If you want, you can set permissions on this channel like any channel in a server to restrict who can see it. Learn more about that by reading [Alpha and Beta Testing](#DOCS_GAME_AND_SERVER_MANAGEMENT_ALPHA_AND_BETA_TESTING/).
+
+## Lurker Mode
+
+Store channels also have a special property that we call `lurkability`. "Lurker Mode" is a feature that we've been experimenting with throughout Discord; it allows users to read public channels in a server without _actually_ joining the server. It also allows users to look at these channels without being logged in to Discord.
+
+> info
+> Users viewing channels in Lurker Mode will not be able to send messages in those channels. They'll be prompted to log in and join the server if they want to chat.
+
+Lurker Mode is automatically enabled for store channels in your server. When someone accepts a server invite that links to a store channel, they'll be viewing in "Lurker Mode".
+
+We know that your server and community are at the heart of your game's success on Discord. Having Discord users see your store pages in the context of your server will help drive more members to your community and help you grow that awesome fanbase for your game.
+
+# Announcement Channels
+
+As part of our ongoing effort to help you build your game community, all [Community servers](https://dis.gd/communityservers) have the ability to create Announcement Channels!
+
+Unlike a regular text channel, Announcement Channels comes with a “Follow” button that allows your superfans to hook and connect your channel into their own personal servers. Now, select messages in your Announcement Channels can be "published" in your players' friend servers as regular messages, allowing them to get the latest updates of their favorite game in the places they hang out most. Because these posts appear and function as messages, it means that everyone in your superfan’s server can find them, discuss them live, and receive them as mobile notifications, if they have this setting enabled.
+
+[Learn more here](https://support.discord.com/hc/en-us/articles/360032008192).