The Steamworks API allows your game to take full advantage of Steam by accessing all of the underlying systems provided through the API. This includes things such as pausing your game when the user opens the Steam Overlay, inviting friends to play, allowing players to unlock Steam Achievements, letting players compete on the Steam Leaderboards and much more.
The Steamworks API Reference catalogs and documents every interface, function, callback, and type supported in the API.
Integration with the Steamworks API is never required to ship your product on Steam, but it is highly recommended as it allows you to accomplish many interactions that Steam users expect.
Initialization and Shutdown
After you have the Steamworks API set up within your project you can start using it by calling SteamInit function to initialize the API. This will set up the global state and populate the interface pointers which are accessible via the global functions which match the name of the interface. This MUST be called and return successfully prior to accessing any of the Steamworks Interfaces!
The Steamworks API will not initialize if it does not know the App ID of your game. When you launch your app from Steam itself then it will automatically have the App ID available.
While developing you will need to hint this to Steam with a text file. Create the a text file called
steam_appid.txt next to your executable containing just the App ID and nothing else.
This overrides the value that Steam provides. You should not ship this with your builds. Example:
A return of False indicates one of the following conditions:
- The Steam client isn't running. A running Steam client is required to provide implementations of the various Steamworks interfaces.
- The Steam client couldn't determine the App ID of game. If you're running your application from the executable or debugger directly then you must have a steam_appid.txt in your game directory next to the executable, with your app ID in it and nothing else. Steam will look for this file in the current working directory. If you are running your executable from a different directory you may need to relocate the
- Your application is not running under the same OS user context as the Steam client, such as a different user or administration access level.
- Ensure that you own a license for the App ID on the currently active Steam account. Your game must show up in your Steam library.
- Your App ID is not completely set up, i.e. in
Release State: Unavailable, or it's missing default packages.
- If you're running into initialization issues then see the Debugging the Steamworks API documentation to learn about the various methods of debugging the Steamworks API.
SteamRestartAppIfNecessary checks if your executable was launched through Steam and relaunches it through Steam if it wasn't.
This is optional but highly recommended as the Steam context associated with your application (including your App ID) will not be set up if the user launches the executable directly. If this occurs then SteamInit will fail and you will be unable to use the Steamworks API. If you choose to use this then it should be the first Steamworks function call you make, right before SteamInit.
If this returns true then it starts the Steam client if required and launches your game again through it, and you should quit your process as soon as possible. This effectively
steam://run/<AppID> so it may not relaunch the exact executable that called this function (for example, if you were running from your debugger). It will always relaunch from
the version installed in your Steam library folder.
Otherwise, if it returns False, then your game was launched by the Steam client and no action needs to be taken. One exception is if a
steam_appid.txt file is present then this will
return False regardless. This allows you to develop and test without launching your game through the Steam client. Make sure to remove the steam_appid.txt file when uploading the game
to your Steam depot!
NOTE: If you use the Steam DRM wrapper on your primary executable file, this check is unnecessary as the DRM wrapper will perform this internally.
When you are done using the Steamworks API you should call SteamShutdown to release the resources used by your application internally within Steam. You should call this during process shutdown if possible.
This will not unhook the Steam Overlay from your game as there's no guarantee that your rendering API is done using it.
|Provides an interface to a steam instance.
|Provides access to a range of miscellaneous utility functions.
|Provides methods for accessing and submitting stats, achievements, and leaderboards.
|Steam UGC API
|Interface to access information about individual users and interact with the Steam Overlay.
|Utils listener interface
|Steam User Stats listener interface
|Steam UGC listener interface
|Steam Friends listener interface
|List of states a Steam friend can be in.
|User restriction flags.
|Used in OnPersonaStateChanged, changeFlags to describe what's changed about a user.
|Possible visibility states that a Workshop item can be in.
|The way that a shared file will be shared with the community.
|Specifies the types of UGC to obtain from a call to CreateQueryUserUGCRequest or CreateQueryAllUGCRequest.
|Used with CreateQueryUserUGCRequest to obtain different lists of published UGC for a user.
|Used with CreateQueryAllUGCRequest to specify the sorting and filtering for queries across all available UGC.
|Flags that specify the type of preview an item has.
Function SteamInit:Int(autoRunCallbacks:Int = True)
Checks if your executable was launched through Steam and relaunches it through Steam if it wasn't.
If this returns True then it starts the Steam client if required and launches your game again through it, and you should quit your process as soon as possible.
This effectively runs
steam://run/<AppId> so it may not relaunch the exact executable that called it, as it will always relaunch from the version installed
in your Steam library folder.
If it returns False, then your game was launched by the Steam client and no action needs to be taken. One exception is if a
steam_appid.txt file is present
then this will return False regardless. This allows you to develop and test without launching your game through the Steam client.
Make sure to remove the
steam_appid.txt file when uploading the game to your Steam depot!
Shuts down Steam.
Dispatches callbacks and call results.
It's best to call this at >10Hz, the more time between calls, the more potential latency between receiving events or results from the Steamworks API. Most games call this once per render-frame. All registered listener functions will be invoked during this call, in the callers thread context.
Const k_UGCQueryHandleInvalid:ULong = $ffffffffffffffff:ULong
Used to specify an invalid query handle.
This is frequently returned if a call fails.
Const k_UGCUpdateHandleInvalid:ULong = $ffffffffffffffff:ULong
Used to specify an invalid item update handle.
This is frequently returned if a call fails.
Const k_cchPublishedDocumentDescriptionMax:UInt = 8000
The maximum size in bytes that a Workshop item description can be.
Const k_cchDeveloperMetadataMax:UInt = 5000
The maximum amount of bytes you can set with SetItemMetadata.
Const k_cchPublishedDocumentTitleMax:UInt = 128 + 1
The maximum size in bytes that a Workshop item title can be.
Const k_cchMaxRichPresenceKeys:Int = 20
The maximum amount of rich presence keys that can be set.
Const k_cchMaxRichPresenceValueLength:Int = 256
The maximum length that a rich presence value can be.
Const k_cchMaxRichPresenceKeyLength:Int = 64
The maximum length that a rich presence key can be.