Setting up achievements

The Bulk Import/Export tab lets you manage achievements as files: export CSVs, edit them in a spreadsheet, and upload them back with your icons. For a game with dozens of achievements this is much faster than editing one at a time.

How a definitions upload is applied: rows with a new API name are added; existing achievements with changed values are modified; unchanged ones are left alone; and achievements missing from the file are kept unless you tick Delete these achievements. Be careful with that option, since you can't simply add a deleted achievement back. To rename an API name, change it in the editor first, or the old achievement's data will be removed. A progress stat must already exist and must have the same permission as the achievement.

If you upload a definitions CSV and a localization CSV together, localization for achievements missing from the definitions CSV isn't updated.

Deleting an achievement removes it for everyone, including players who already unlocked it. If players have earned it, the editor will suggest archiving instead.

Sets group achievements, track completion per group, and let you add or retire achievements without taking progress from players. They're configured entirely in Steamworks. Your game uses the same API names and calls as before, so there's no extra code.

Managing sets

• Edit: open the set's menu and choose Edit set to change its name, restrictions or developer-only status, or to archive it.
• Visibility: each set shows Visible, Hidden by restrictions (developer-only, or its DLC isn't released yet) or Will be visible upon publish.
• Reorder: click Reorder Sets and drag. The base game set can't be moved.
• Delete: move or delete every achievement in it first. To retire a set without taking anything from players, archive it instead.
• Move achievements: change one achievement's In Set field, or use Bulk Move in the table header. Tick the achievements (filtering by API name first helps), pick a destination or Create New Set..., and click Move. The editor warns you if a move would hide an achievement from players who earned it, or break completion for players with progress in the destination set.

• Archived achievements stay visible to players who unlocked them and can still be featured on profiles. Players who haven't unlocked one won't see it, and it doesn't count against their completion.
• Archived sets are visible only to players who unlocked something in them, and nothing in them can be unlocked.
• Completion is per set. A player completes a set by unlocking every available achievement in it. Once complete, it stays complete even if you add more later. DLC sets only count for DLC owners. Completing any set qualifies the game for the Completionist Showcase on a player's profile.
• Spoiler and archived achievements aren't shown in the achievements panel on your store page.

Archiving doesn't change your game. Make sure your code stops awarding an achievement once you archive it. Steam won't unlock an archived achievement, or a DLC achievement for a player who can't play that DLC, so only award DLC achievements to owners.

• Achievements page (Steam client and Community site): progress and completion per set, comparison with up to 3 friends, global unlock rates with rare ones highlighted, and search and filters by unlock state or set.
• Store page: an achievements panel, without spoiler or archived achievements. DLC store pages show that DLC's set.
• Profiles: the Achievement Showcase counts games and sets completed, and a game can go in the Completionist Showcase once any of its sets is complete.

You can link straight to your game's achievements, with no player's progress, whether or not the visitor owns the game: https://steamcommunity.com/achievements/<appid>

• Add new sets for new content. Adding achievements to a set players already completed shows it as completed with locked achievements, which is confusing. A new DLC, update or mode deserves its own set. Adding to a released set won't break completion, but it may not display naturally.
• Archive instead of deleting anything players have earned.
• Use DLC sets for DLC achievements, so players without the DLC can still complete your game.
• Keep set names short and descriptive. They show up in many places, including the Steam client. Localize them for every language you support.
• Test with developer-only sets before releasing new achievements.

Common questions

• Do I need a game or SDK update for sets? No. Same API names and calls.
• What happens to my existing achievements? They're all in the base game set and appear as one list unless you create other sets.
• Can I move an achievement after release? Yes, with the editor's warnings about hiding it or affecting completion.

With Steamworks.NET in Unity (Facepunch.Steamworks is similar), the pattern is request stats once, set the achievement, then store:

// After SteamAPI initialises (e.g. SteamManager in scene)
using Steamworks;

public static class Achievements
{
    public static void Unlock(string apiName)
    {
        if (!SteamManager.Initialized) return;
        SteamUserStats.SetAchievement(apiName);   // e.g. "ACH_FIRST_WIN"
        SteamUserStats.StoreStats();              // commits to Steam, shows the popup
    }
}

// Somewhere in gameplay:
Achievements.Unlock("ACH_FIRST_WIN");

Steam shows the overlay notification the moment StoreStats succeeds. Don't call StoreStats every frame; once per unlock or on save is enough.