Glossary

Terminology

Quick, alphabetical definitions for terminology used across LootLocker's features and documentation. Follow the links below for an in-depth look at any specific feature.

Admin API: Provides direct access to LootLocker's features and can also be used by your game editor.
Assets: LootLocker's core concept for anything a Player can earn, purchase, possess, or equip — items of property that store both LootLocker-specific and game-specific data.
Authentication: Verifies a Player using a specific identifier or third-party service and registers a session on login, through Guest Login, Platform Login, or White Label Login.
Broadcasts: Schedules and delivers localized messages to players across one or more of your games.
Catalogs: Creates and manages a collection of purchasable items and assets within your in-game store.
Character Class: A defined player archetype, such as Wizard or Warrior, built from a Base Class and specifying which Assets it can equip and its default loadout.
Claimable Rewards: Delivers in-game rewards directly through Discord, built on Triggers.
Complexity: Additional functionality assigned to an Asset's Context, such as Loot Box, Rental, or Drop Table behavior.
Context: A way to group and describe Assets, telling your game what type of Asset it is and what special relationships it should have, such as with Character Classes.
Currencies: Defines and manages in-game currencies that players can earn, purchase, and spend within the game economy.
Discord Broadcasts: Sends announcements, updates, and messages to your Discord server, built on Broadcasts.
Discord Commerce: Sells in-game content directly through Discord, built on Catalog Listings.
DLC Management: Manages downloadable content (DLC) across various platforms.
Domain Key: A unique key identifying your game, used by LootLocker Support to look up your game's configuration when diagnosing issues.
Drop Table: An Asset Complexity that lets LootLocker randomly select an Asset from a predefined table for a Player to choose from.
Entitlements: Tracks content entitlements for players, providing a record of purchased items.
Game API: Integrated into your game client so that your game can talk to the LootLocker backend.
Hero Class: A specialized version of a Base Class with its own default loadout and refined equip rules, used to create advanced player roles.
Inventory: Tracks and manages the Assets a Player owns.
Leaderboards: Tracks player or generic rankings, with options for time-based resets and rewards.
Loot Box: An Asset Complexity that lets an Asset be randomly selected from a predefined group of Assets.
Metadata: Lets you store additional, custom information in different formats and attach it across LootLocker systems.
Platform Keys: Creates and manages game keys that can be distributed to players through other LootLocker systems.
Player Segments: Lets you target certain systems to specific groups of players based on their behavior, activity, platform usage, or play history.
Player ULID: LootLocker's standard player identifier — see LootLocker Player Identifiers below for this and the other identifier types used across LootLocker.
Presence: Provides real-time visibility into player sessions (CCU), in-game states, and playtime across all platforms.
Progressions: Sets up point-based progression systems with customizable tiers and rewards.
Real Money Purchases: Integrates direct real-money transactions, letting players buy in-game items or currency with real-world currency.
Rewards: Lets you reward players with content, currencies, progression changes, and more across multiple LootLocker systems.
Server API: Integrated into your hosted game server so that your game server can talk to the LootLocker backend securely.
Session: A verified, active login for a Player established through Authentication, required before you can use any other LootLocker feature.
Squire: A Discord bot powered by LootLocker that connects your Discord community to your game, enabling game key distribution, synchronized communication, and deeper player engagement.
Triggers: Grants rewards dynamically based on player actions.
Twitch Drops: Rewards your players with in-game items for watching your game on Twitch.
UGC (User Generated Content): Lets players create, share, and interact with user-generated content, with moderation and curation tools in the Web Console.
Unified Player Accounts: Enables a seamless player experience by connecting multiple platform authentication methods for unified cross-platform functionality.
Virtual Purchases: Enables in-game purchases using virtual currencies, giving players a range of non-monetary transaction options.
Wallets: Manages and stores in-game currency balances for players or characters.
Web Console: A browser-based interface that provides access to all LootLocker features and the tools needed to manage your games.
White Label Login: Authenticates players using a username and password account created specifically for your game.

Game Version

To distinguish and order the versions of your game LootLocker requires that you utilize a numeric version of the Semantic Versioning standard. This is used in different API calls when using the REST API, and in the SDKs it is a required setting to use the SDK.

A numeric semver string consists of between 2 and 4 numbers separated by periods: X.Y(.Z.B). Some valid numeric semver strings would be 1.0, 0.0.2.6, 23.6.13. According to semver standard the position of the numbers is significant and can greatly help you in showing what a version "means". The positions are named MAJOR.MINOR.PATCH.BUILD. For LootLocker, the Patch and Build numbers are optional.

MAJOR - Increment this number when you make incompatible and/or very significant changes. This could for example be a complete re-balance of classes, a re-engineering of a crucial system, or a change that makes previous save files unreadable.

MINOR - Increment this number when you change something that isn't crucial, or add stuff to previous systems. This could be for example adding an achievement, moving assets within a level, or making internal tech changes only.

PATCH - This is optional for LootLocker. Increment this number when you make a small change that is very unlikely to have a significant impact on your users. This could be for example a bug fix, some localization changes, or changing the color of UI items.

BUILD - This is optional for LootLocker. Increment this number when you produce a new build for an existing version. If you for some reason need to distribute a rebuild of version 1.2.3 without additional changes then use this number to make a version 1.2.3.1.

Identity Provider

Identity provider is the term we use to describe the service used to authenticate the player. This could be a 1st party platform like Steam, Google and Apple, but also White Login or even Guest Login.

This term is an umbrella term for all the different ways a player can authenticate with your game.

LootLocker Player Identifiers

There are a few different ways to identify a player that permeates the LootLocker systems. This is due to our service evolving over time. While we aim to remove usages of legacy identifiers, you are likely to run into methods using a few of these.

Player ULID

This is the standard identifier for players across LootLocker's systems. ULID stands for Universally Unique Lexicographically Sortable Identifier and is an industry standard identifying method that is practical for many applications.

The player ulid can in different endpoints be referred to as player_ulid, player_id, ulid, or simply id. Regardless, you can recognize it by its string representation format which is a long string (usually 26 characters) of alphanumeric characters. Example: 01BX5ZZKBKACTAV9WEVGEMMVRZ.

You can find it in all game api session responses (in both api and SDKs), in the server Get Player Info by Game Session Token endpoint (in both api and SDKs), or get it from another player identifier using the Game or Server Lookup Player Names by IDs endpoint (in both api and SDKs), and in the LootLocker console player view.

Player UID

This is a shorter identifier mainly to be used for public player display. The purpose is to have a shorter identifier that players can write down and share. UID simply stands for Unique Identifier.

The player uid can in different endpoints be referred to as player_uid, player_public_uid, or uid. Regardless, you can recognize it by its string representation format which is a shorter string (usually 12 characters) of alphanumeric characters. Example: AG5SG99GAJ5R.

You can find it in all game api session responses (in both api and SDKs), or get it from another player identifier using the Game or Server Lookup Player Names by IDs endpoint (in both api and SDKs), and in the LootLocker console player view.

Player ID (Legacy)

This is a numerical identifier of the player. This identifier, although still used in many endpoints, is deprecated and LootLocker is phasing it out.

The player id can in different endpoints be referred to as player_id, player_legacy_id, legacy_id, or id. Regardless, you can recognize it by that it's the only integer identifier of a player. Example: 9698530.

Player Identifier

This one is strictly related to guest login. The player identifier is the unique id that "authenticates" a guest user. As such, this is supposed to be a secret for the player that uses it. Any user with access to a player identifier can start a session as that guest user.

The player identifier can in different endpoints be referred to as player_identifier, player_guest_login_id, or identifier. Regardless, you can recognize it by its string representation format. Example: eefecf08-3b6c-4eec-82f6-322d41d1f2fd.

You can find it in the game api guest session response (in both api and SDKs), and in the LootLocker console player view.

Player Platform Identifier

This varies a lot, because there are a few. But you can also identify a player by their external id with another platform or authentication. This can be for example their White Label Email, their Steam ID, or their xbox id.

The player platform identifier can in different endpoints be referred to as player_platform_identifier, platform_identifier, or by their platform such as steam_id or psn_id.

You can find it in the Game Lookup Player Names by IDs endpoint (in both api and SDKs), or in the LootLocker console player view on the right side. Here's an example of how it looks for a Steam player (note that there can be many identifers here for unified player accounts).

Player Name

This is a lot more decorative than other identifiers. But can be uniquely identifying players if you enable Use Unique Player Names in your game.

The player platform identifier can in different endpoints be referred to as player_name, or simply as name.

This is the only "identifier" that the player can change, using the Game Set Player Name endpoint (in both api and SDKs). You as an admin can also change this value for a player in the console player view.

You can find it in all game api session responses (in both api and SDKs), or get it from another player identifier using the Game Lookup Player Names by IDs endpoint (in both api and SDKs), and in the LootLocker console player view.