Changelog.

Find it here

Features

• Triggers 2.0 🕹️ - We’re excited to announce the re-release of one of LootLocker’s most versatile features—Triggers! This feature has undergone a complete overhaul and is now fully integrated with the same cross-feature rewards system that powers all our latest features. Triggers let you create and manage in-game actions tied to specific rewards, opening up countless opportunities to engage your players. Read more here
• Notifications 💬 - Notifications serve as a shared system that integrates seamlessly with multiple features, including Rewards, Catalogs, Progressions, and Triggers. Acting as a central hub, Notifications track and communicate important player-related updates to the game, ensuring players stay informed about significant events and changes. Read more here
• .com - The LootLocker api has transitioned to .com instead of .io in preparation for an eventual potential phase out of the TLD.
• The version of the LootLocker SDK is now logged at start up time to help when reaching out to the team for support.
• All session responses now contain the wallet_id of the player.

Bugfixes

• Hero loadout now correctly contains an array of loadout items instead of a single loadout

Deprecations

• With the introduction of Triggers 2.0, the old triggers system is deprecated. Adressing this will require you to re-configure your triggers in the new triggers configuration. To do this, please refer to our documentation. Once you have done this, simply call the new InvokeTriggersByKey method in place of the ExecuteTrigger method. For a deeper understanding of using triggers in game, refer to our documentation.

Find it here

Features

• Leaderboard Archives - LootLocker leaderboard archives are now supported by the Server SDK.
• SDK Version logging - The version of the LootLocker Server SDK is now logged at start up time to help when reaching out to the team for support.
• Add player session token lookup - You can now look up a player using their session token. Use this to verify that a client token is indeed for the player that the client says they are.
• Succesful request logging - When configured as very verbose and in the editor, the SDK will now log successful requst data as well.
• .com - The LootLocker api has transitioned to .com instead of .io in preparation for an eventual potential phase out of the TLD.

Bug Fixes

• The array in Universal Inventory response is now correctly named, handling json parsing correctly
• The Asset Instance Storage operation responses are now single items making json parsing function correctly
• The character inventory and hero inventory requests now work, the endpoints were incorrectly named

Today we launched a brand new cross-system feature, Metadata. Metadata allows you to store additional, custom information related to various LootLocker features, such as Progressions, Leaderboards, and Catalogs.

This data lets you add context or functionality to these features, going beyond the default settings. For example, you might use Metadata to store map details for a leaderboard or to attach an image to an item in your in-game store.

Check out our documentation to learn how to implement Metadata in your game.

Today we launched a brand new feature, Feedback. The Feedback feature allows you to create and manage reports across three different core LootLocker systems: Players, UGC, and the Game itself. Learn more about this feature in our announcement post.

Check out our documentation to learn how to implement Feedback in your game.

We have updated how errors in the LootLocker web console are displayed.

When recieving an error you now are provided with plain-text information about what went wrong as well as a Trace ID that you can copy and share in Discord so that we can help fix the problem.

A new feature has been added to the API that allows you to specify a list of domains that are allowed to make requests to the API. This is useful if you want to restrict access to the API to only your own domains.

Documentation can be found here.

We have exposed a new setting in the LootLocker Console to allow you to configure whether or not the player name should be updated from the Identity Provider (eg. steam) when a session starts.

This is useful for games that do not want to update the player name on every session start, but only when the player explicitly changes their name in the game.

This setting is available in the Console under in "Game Settings", under the "Misc" tab. Look for "Preserve Player Names on Session Start".

It's now possible to create reward groups in LootLocker.

• Reward groups allows multiple rewards to be awarded to a player at once.
• This is currently available for catalogs and leaderboards rewards.

To learn more you can read our announcement post.

🎉 Unreal SDK v9.0.0 is released 🎉 This version introduces support for reading and filtering custom notifications, allowing you to notify players of in-game rewards, news, and more. This release also includes a crucial bug fix for Epic Games account connecting/disconnecting, updating the platform string to epic_games for proper functionality.

Find it here