To learn more about the different types of packages and requesting keys, please see [doclink=store/application/packages][/doclink]. [subsection]Dev Comp Packages - Important Configuration Note[/subsection] As a Steamworks developer, you have a special type of packages attached to your publisher group. …

Being able to determine if input comes from a real mouse vs a controller is an important part of good UX practices. [*] You should [i]either[/i] rely on the configurator to provide sensitivity (ie you don't filter incoming Steam Input data), [i]or[/i] you should use a dedicated sensitivity option for Steam Input that's distinct from the system mouse. …

For more information on action set layers see: [doclink=features/steam_controller/action_set_layers]Action set layers[/doclink] [callout=red] [h3][b]Limits on the number of actions [/b][/h3] Currently the maximum number of actions is 16 analog and 128 digital actions. It is very important to note that actions can be shared between action sets so in most cases you will only need a fraction of the maximum number of actions. …

[h4]Based on the Official SDK[/h4] We provide SDKs for many of our games, and these are the approved tools for modding. It’s important to note that shipping a mod based on leaked or stolen source code is not permitted. [h4]Clear Communication[/h4] Your mod should have a distinct identity, and should not suggest that it was created or endorsed by Valve. …

[h4]Q: How do Wishlists affect my game’s visibility on Steam?[/h4] [b]A:[/b] Wishlists can be an important factor in determining where your game appears on Steam. After a user has wishlisted your game, your game may appear in different featured sections, with a visual reminder that the game is on their wishlist. …

[/td][/tr] [/table] Retrieves the list of assets from another game to import. [b]NOTE:[/b] This call requires a publisher API key to use this method. As such this API [b]MUST[/b] be called from a secure server, and can never be used directly by clients! …

[subsection]Timing[/subsection] While not required, we generally see partners choosing to run these at approximately the same time during the year. Many like to anchor against an anniversary event, or an important milestone date. We ask that you keep these at least six months apart if possible. [subsection]Discounts[/subsection] As implied by the label of "sale", these events should be focused around your portfolio discounts. …

Where tags are applicable, the top 20 tags applied to your game will impact which games Steam thinks are similar to yours. Here the order is less important than the overlap between multiple tags. So if your game has "Open World" and "Fantasy", Steam will be more likely to recommend your game to players that have previously played games tagged with "Open World" and "Fantasy". …

That would limit potential invites to 15,000 total, as only users who had access as of today can send new invites. [subsection]Important notes about Friend Invites[/subsection] [callout][b]Prerequisite: [/b]Users can only invite friends they have been friends with for at least 30 days.…

Resetting a playtest removes all participants and can be accomplished from your Steam Playtest dashboard. [callout][b]Important:[/b] Resetting a Steam Playtest is not reversible. Make sure you are ready to remove all playtest participants before initiating the reset.…

The Additional Revenue Share system has no way of knowing which app is more important in this case. If your app has recorded significant revenue since October 1st, 2018 (>$1,000,000 USD) please reach out to the Steam Finance team and we will update the reporting relationship for this package manually. …

[h4]Track Numbering[/h4] The Steam Music Player determines play order from the filenames, not the metadata. If your soundtrack's play order is important, the track number should be included at the start of the filename. If your soundtrack has 10 or more songs, the files 1-9 should begin with a leading 0 (e.g. …

See [doclink=#requirement_os]OS Specific Requirements[/doclink] for more details. [*] [b]AsCurrentUser[/b] - Optional flag, set it to 1 if it's important for that program to run as the current user. Otherwise, the Steam client might run it as Administrator to avoid elevation prompts in Big Picture or VR environments. …

You can ignore the code in the Engine folder - it supports basic 2D rendering via D3D and basic keyboard input. All of the important code documenting Steamworks API usage is files in the Game folder. The most interesting areas to begin looking at the code are described briefly below: [list] [*] [b][code-inline]Main.cpp[/code-inline] -- Main entry point for the example game.…

If Valve has requested an additional opt-in for marketing materials inclusion consideration, the deadline to opt in (to the event and the marketing materials permissions) as well as enter your discount is typically 6 weeks prior to event start. Exact deadlines are provided in the Important Dates section of the event-specific documentation. For more information about marketing materials inclusion, see the [doclink=#permissions]Marketing Materials Permissions[/doclink] section below. …

[subsection]Responding To Reviews[/subsection] There may be cases where the reviewer is missing important information, or may have encountered a bug that has since been resolved. To help keep the community on-track, we have provided tools for developers to respond directly to such reviews. …

Make sure that what you put out there is high quality and measures up to the real experience. [*] Timing – When you release your demo is also important. We generally recommend waiting until launch, but there are circumstances where putting a demo out prior to release is effective. …

issueid=915]support form here[/url] to contact us to change from a Free to Play game to a paid package. Treating customers fairly is the most important thing to us, so we ask that you give your customers at least one week notice via a [doclink=marketing/event_tools]News Event[/doclink] before removing any in-game purchasing (if applicable) and switching your app from free to paid. …

This is to help ensure consistency and to avoid making it possible for a malicious game server to set anyone's stats at any time. Given the restriction, it is important not to wait until the end of a round to set stats. Set them continuously so you can store them as a user quits. Clients will get automatic updates when a game server changes their stats. …

Learn more: [doclink=store/localization]Localization & Languages[/doclink] [*][h3]Alpha and Beta testing[/h3] It can feel hard to share your game with others before you really feel that it's 'done' or polished enough. But gathering feedback is important to making sure you understand your audience and is great practice for communicating about your game. Through Steam you can run various kinds of testing with external groups of players. …

. [*] Client B must pass the SteamID of client A to [api]ISteamUser::EndAuthSession[/api]. [/list] [/list] A few important notes about Session Tickets: [list] [*] Session Tickets must only be used once. [api]ISteamUser::GetAuthSessionTicket[/api] must be called for every client in the mulitplayer session who requests a ticket. [*] When used to authenticate players within a peer-to-peer multiplayer session, each game client should verify the identity of every other game client in the multiplayer session. [*] When finished with a Session Ticket, [api]ISteamUser::CancelAuthTicket[/api] must be called for every handle returned by [api]ISteamUser::GetAuthSessionTicket[/api]. [*] When client A calls [api]ISteamUser::CancelAuthTicket[/api], client B will receive a [api]ISteamUser::ValidateAuthTicketResponse_t[/api] callback stating that client A's ticket is no longer valid. [*] When client A leaves a game with client B, if client A's call of [api]ISteamUser::CancelAuthTicket[/api] is processed before client B call's of [api]ISteamUser::EndAuthSession[/api], then client B may receive a [api]ISteamUser::ValidateAuthTicketResponse_t[/api] callback stating that the ticket was cancelled. …

. [*][b]The landing page[/b] - The sale event page itself that features the games, broadcasts, and/or events that you configure. [/olist] [section]Important Reminders[/section] The documentation below provides instructions, templates and guidelines, but before you start working on your sale page, please review these best practice suggestions: [b]Do:[/b] [list] [*]Make sure the purpose of your event is clear from all of the artwork (see "Banner& Templates" below), so that any user who sees the artwork or lands on the page immediately understands what they’re looking at. [*]Use the page layout tools to categorize your games and content in a way that will make browsing easy for players. [*]Localize any text or calls to action (or reach out to Valve in advance to get localization assistance). [*]Preview your page and ‘playtest’ it with friends or colleagues before the event begins, to proofread and gather feedback. [*]Use the current sale page Photoshop [url=https://www.dropbox.com/scl/fo/mhf604o6bdbcfr1scq7bx/h?…