Changelog.

We've updated our Connected Accounts feature to better support link flows in more complex scenarios.

• You can now use auth.game to link accounts to the player, without needing to use the old connect endpoints.
• When linking, we will hide the login buttons for providers already linked for the player.
• The ability to move multiple providers between player accounts.

With this new functionality it's now possible to better link providers directly from the game client. We've also greatly improved the experience for games that wants to implement merging of accounts.

We've also added support for the following providers:

• Steam
• Epic Games

To read more, check out our updated documentation.

Today we've released reference documentation for the API we use to power auth.game. You can use this API to for Player Impersonation, to create your own alternative to auth.game or to set up a complex account merging flow when used in conjunction with the Server and Game APIs.

This documentation brings all the same benefits mentioned in New Reference Documentation last week.

You can find this reference documentation here: ref.lootlocker.com/auth-client.

Today we're launching an update to our reference documentation, which brings multiple improvements:

• Use it directly from the browser: You can now call endpoints directly from the browser, making it easier to test and explore the API.
• Improved Navigation: The new documentation has a more intuitive structure, making it easier to find the information you need.
• Enhanced Search Functionality: The search feature has been improved to provide more relevant results and faster access to the information you need.

These docs are for people who want to explore the API's directly or does not use one of the already supported Game Engines. The documentation for our engine SDKs can be found here.

The new reference documentation is available for all our APIs:

• Game API
• Server API
• Admin API
• Auth Client API

Twitch drops support have landed in LootLocker!

• Players can link their Twitch account to their LootLocker account.
• Players can claim drops from Twitch streams and receive them in game.
• Easy to set up and configure.

You can read our announcement here.

🎉 Unity SDK v4.0.0 is released 🎉 New features include player name lookup, the ability of getting progressions from another player, and a convenience lookup method for twitch drops. This version of the SDK also contains a spring cleaning of previously deprecated methods and symbols. See the release notes below for more information.

Find it here

The Game API have been updated so you can now list assets in the order that best suit your game using the /game/v1/assets/list endpoint.

There are two new query parameters that can be sent.

order_by which is the field you want to use for ordering your assets. Valid options are name, created_at, updated_at, and id.

order_direction is the direction you want to order your assets. Valid options are ASC and DESC.

🎉 Unreal SDK v7.0.0 and Unreal Server SDK v5.0.0 are released bringing major capability improvements 🎉 Exciting updates! We've released a major capability upgrade to our Unreal SDKs adding Multi user support to the Game SDK and Token exchange & Impersonation support to the server SDK.

Multi User Support

This version of the Game SDK sees a major and central feature update in giving the SDK support for multiple users 🎉👥. This enables a few advanced use cases such as:

• LootLocker supported local multiplayer. Build your couch co-op adventure, your fighting game, or your turn based board game with each player connected to their LootLocker user.
• User Profiles. Support a user selection screen remembering all players that have played on the device and allow for seemless switching between them.
• In depth account linking. When linking account, this will allow you in a client setting to display data from all the accounts involved in the linking. Or even moving data between them. All as you envision it.

Token Exchange and Impersonation

This version of the Server SDK turbo charges your game servers. Together with the multi user support update in the Game SDK this is a major capability boost for the SDKs. Token Exchange lets you exchange an active game session token for a new one (keeping the old one active as well). Impersonation lets you get an active game session token for any player using their ulid. This means that you can now in a server context keep game api sessions for all active players and lets the server access the full power of the game api. Use this to for example:

• Call security. Move code for things like purchasing, progression point submits, invoking triggers, or submitting scores out of the client context and let the server execute that functionality on the players behalf.
• Expanded features. Use methods in a server context that don't yet exist in the server api.
• Responsibility Distribution. Offload code from your clients to a server context.

Find the Unreal SDK here

Find the Unreal Server SDK here

While Game merging has been an integral part of LootLocker since it's inception, over time it's proven error prone and hard to use.

We've made the hard decision to deprecate the feature and hide it for all new games. If you have an existing game that uses the feature it will continue to work as before, until we can replace it with a better solution.

This also means new games only have 1 environment available.

So how will you be able to run a development and live version of your game?

The recommended approach is to create 2 games in LootLocker, one for development and one for live. While this solution is not perfect, our experience is that it works better than the game merging feature.

We know this is not ideal, but we believe it is the best solution for the time being. We are working on a better solution that will allow you to have multiple environments for your game, and we will keep you updated on our progress.

We have expanded the information shown in the Console for Player Inventories. The inventory is now ordered by the date the player received the asset instance, and a source field has been added to indicate how the player received the asset instance.