Translated from the original Japanese article
Tech 3 min read

Steam DLC Depot Configuration Troubleshooting

Steam Game Development Troubleshooting Experiment

Overview

After releasing the DLC “Design Document Collection” for “Juu-byo Dasshutsu!”, purchasers reported they couldn’t download it (the DLC appeared empty). This is a record of investigating and resolving the issue.

The Problem

  • The DLC “Design Document Collection” (App ID: 4233300) was reported as “empty”
  • No depots were showing in the DLC’s admin panel

Root Cause

Steam’s default configuration is that “DLC depots are managed under the base game’s App ID.” That means:

  1. The DLC admin panel (4233300) has no depot management functionality
  2. Depots must be created, managed, and uploaded from the base game (3322940)
  3. The package screen showing “No depots” is just an admin UI display issue

Trial and Error

I first consulted Gemini (AI), which kept giving irrelevant answers and couldn’t resolve the issue. I then consulted Claude and got it sorted.

Gemini repeatedly pointed at:

  • “Aren’t the depots missing from the package?”
  • “Isn’t the build set to the default branch?”
  • “Check the base game’s admin panel”

But looking at the base game also showed “No depots,” so it went in circles.

What Gemini missed: Even if I wanted to “add a depot to the package,” the DLC depot hadn’t been created on the base game side yet. Of course it didn’t appear as an option — it didn’t exist.

Resolution Steps

1. Create the DLC Depot from the Base Game

  • Base game (3322940) → SteamPipe → Manage Depots
  • Click “Add DLC (Associate the DLC’s main depot)”
  • Select Design Document Collection (4233300)
  • Click “Save Depot Changes”

2. Upload Content to the Correct Depot

Important: When uploading with SteamPipe, specify the DLC’s depot ID (4233300).

The initial problem was that the artbook content had been uploaded to the base game depot (3322941).

Correct build configuration:

  • Included depots: 3322941 (base game content)
  • Included depots: 4233300 (Design Document Collection) ← this was missing

3. Set the Build as the Default Branch

Set the build containing both depots as the default branch.

Correct Workflow

ItemWhere to Manage
Depot management, build uploads, SteamPipeBase game (3322940)
Store page, pricing, metadataDLC (4233300)

Confusing Points

”No Depots” Display on the Package Screen

  • Opening the DLC’s package (e.g., 1481997) shows “This package has no depots”
  • Clicking “Add Depot” shows no options
  • This is only a display issue in the admin UI — it does not affect actual distribution

Two Ways to Manage DLC Depots

  1. Managed centrally under the base game (default)

    • DLC depots are managed from the base game side
    • The DLC admin panel has no depot-related items
    • This is what was set up here

  2. Each DLC manages its own depots separately

    • Each DLC creates and uploads depots independently
    • Useful when you have many DLCs

Verification

Checking the Build

Base game (3322940) → SteamPipe → Your Builds

Correct state:

Build ID: 21278884
Included depots: 3322941, 4233300  ← both included

Checking the Package

In the package list, “1 app | 1 depot” means the depot is linked. “1 app” only shows no depot in the UI, but with the above configuration that’s fine.

Conclusion

Confirmed with a purchaser that the DLC downloads correctly.

The “No depots” message on the package screen is just a UI display artifact. Once you correctly set a build containing the DLC depot as the default branch on the base game side, distribution works.

Putting this here as a note for myself, though I’m pretty sure I’ll do this again…