Knowledge Base
HomeProductsCommunityReviewsSocial
Toolkit for Steamworks
Toolkit for Steamworks
  • Welcome
  • Register with Valve
  • Install
    • Unity Install
    • Unreal Install
  • Configuration
    • Unity Configuration
    • Unreal Configuration
  • Initialization
    • Unity Initialization
    • Unreal Initialization
  • Multiplayer
    • Unity Multiplayer
    • Unreal Multiplayer
  • Build Testing
  • Deploy
  • Launch
  • Features
    • Achievements
      • Unity Achievement Tools
    • Authentication
    • Branches
    • Community Hub
    • Cloud Save
    • CSteamID
    • Discovery Queue
    • Downloadable Content
    • Early Access
    • Friends
    • Input
    • Inventory
    • Leaderboards
    • Lobby
      • Unity Lobby Tools
    • Overlay
    • Party
    • Playtest
    • Remote Play
    • Reviews
    • Rich Presence
    • Stats
    • Steam Game Server
    • Store Page
    • Workshop
    • Voice
Powered by GitBook
On this page
  1. Features

Playtest

PreviousPartyNextRemote Play

Last updated 1 month ago

Contrary to the name, a playtest is a separate app; the concept comes from "playtesting" meaning to playtest an idea or small slice/section of the game. The idea here is that you would create a separate build containing a "vertical slice" of your game, something specific you wanted people to playtest. It is NOT (usually) your full game. It is a small bespoke (for this purpose) section of the game content so that you can "Playtest" that idea in isolation without modifying the main app. For example, you might want to "Playtest" a boss fight, or a specific dungeon, or a game mode. But you wouldn't playtest the entire game at once (usually).

If you want to "test" your game, as in your whole app with people outside of your dev team, you would (usually) use a "" to do that. Often called a "Beta", you can then issue "Release Override Keys" to allow people to play that branch for some limited period or indefinitely, your choice. A branch is a version of your main app, so it uses the same exact configuration and settings as the main app it's just a different version with optionally different key/access such as a Press Build, Alpha or Beta Build, etc.

A Steam Playtest appID has access to the same Steamworks technical features as your main game - but with reduced store and community setup. Instead of having its own separate store page, your Steam Playtest signup will live right on your main game, so that customers can sign up and access the playtest but still Wishlist or Follow the main game.

You can set up a playtest for your game at any time once your game has a store page. You can then let players "sign up" for the playtest via a button that will appear on the main app's store page.

This is most useful when you want to test a specific part of your game. For example, testing a game mode, a boss fight or some other focused application. it is NOT the way to go to test the entire game.

Set-Up

  1. Configure the app ... At minimum, you will need to provide a Library capsule image and update the visible name of the Playtest App, for example Túatha: Legends - Playtest

  2. Complete the "Release Process" Your dashboard will walk you through this

Once that is complete your Playtest is up and ready to work with. You can then make its signup button visible or hidden at will and manage signups by region.

Create the Playtest app from the Associated Packages & DLC page for your game app

Branch
Steam Playtest (Steamworks Documentation)
Valve's documentaiton ... please read it
Logo
Steam Playtest (Steamworks Documentation)
Valve's litteral step by step guid for doing this ... we will repeate it here
Logo
As seen in Valve's documentaiton ... please read it 😉