GDK downloadable content (DLC) packages

​

Set up your main package identity

1. Look up the Store ID (12 character alphanumeric string) of your main application package in the Game Setup page for your main game product. (Example: 9PNX12345AAA)
2. Add the StoreId element to your main package’s MicrosoftGame.config file.

<?xml version="1.0" encoding="utf-8"?>
<Game configVersion="1">
    <!-- Content omitted for brevity. -->
    <StoreId>**REPLACE WITH STOREID**</StoreId>
</Game>

​

Create a DLC package

1. Create your DLC package add-on within Partner Center from the Add-Ons menu under your main product.
2. Place all your DLC package content into a single directory.
3. Create a MicrosoftGame.config file in the same directory as your DLC package content by using the sample data as follows.
4. Specify the Target Device Family that this DLC package is being created for in the TargetDeviceFamilyForDLC field. Allowed values are XBOX One, XBOX Series X|S, or PC. It’s required to be specified for XBOX One and XBOX Series X|S, and is optional on PC as long as the /pc flag is used when generating the DLC .MSIXVC file by using makepkg.exe.
5. Look up the Package/Identity/Name field of your main application package in the Game Setup page of Partner Center, and then put the Identity Name in the MainPackageDependency field. For example, MyPackageName
6. Look up the Store ID (12-character alphanumeric string) of your Add-on/DLC package from Partner Center, and then place it in the StoreId field as follows.
7. Look up the Store ID (12-character alphanumeric string) of your main application package in the Game Setup page for your main game product. Place it into the AllowedProduct field as follows. For example, 9PNX12345AAA

<?xml version="1.0" encoding="utf-8"?>
<Game configVersion="1">
    <Identity Name="**REPLACE**"
        Publisher="**REPLACE**"
        Version="1.0.0.0"/>
    <ShellVisuals DefaultDisplayName="**REPLACE**"
                  PublisherDisplayName="**REPLACE**"
                  StoreLogo="Storelogo.png"
                  Square150x150Logo="Logo.png"
                  Square44x44Logo="SmallLog.png"
                  Description="**REPLACE**"
                  BackgroundColor="#000040"
                  SplashScreenImage="SplashScreen.png"/>
    <StoreId>**REPLACE WITH STOREID OF ADD-ON / DLC**</StoreId>
    <TargetDeviceFamilyForDLC>**REPLACE**</TargetDeviceFamilyForDLC>
    <AllowedProducts>
      <AllowedProduct>**REPLACE WITH STOREID OF BASE GAME**</AllowedProduct>
    </AllowedProducts>

<!-- The Desktop Registration section is for PC only. -->
    <DesktopRegistration>
      <MainPackageDependency Name="**REPLACE_WITH_IDENTITY_OF_PARENT_PRODUCT**" />
      <ProcessorArchitecture>x64</ProcessorArchitecture>
    </DesktopRegistration>
</Game>

8. Open a Microsoft Game Development Kit (GDK) command prompt in the folder that contains a single folder with all your game content, and then run the following command.

9. If you’re creating DLC for PC, use the following command.

10. If you’re creating DLC for console, use the following command.

​

Accessing DLC packages at runtime from your game

1. Enumerate the packages
2. Check for a valid user license for the target package
3. Take the packageIdentifier from the enumeration results and pass it to the XPackageMount API.

    <VirtualMachine>
        <DlcCompatibility>XboxOne</DlcCompatibility>
    </VirtualMachine>

​

Deploying and testing a DLC package

​

Reference API documentation

• XPackage (API contents)
  • Functions
    • xpackageenumeratepackages
    • XPackageMount