Changelog.

🎉 Unity SDK v3.6.1 is released 🎉 New features include GetCurrencyDetails for specific currency info and enhanced leaderboard data returning ULIDs for better metadata handling. Bug fixes: UnEquipIdAsset methods now function correctly. Note: Transition from full player storage to Player Metadata is recommended.

Find it here

Squashed a bug in the Admin API which would in some circumstances result in drop table grants not saving correctly.

You can now equip multiple Asset Instances in a single Context. This is great if your game requires players to have for example 2 active abilities at the same time.

While there are API changes associated with this, you can use it without updating the SDK or changing your implementation. The only downside is that you will not be able to programatically see how many instances you can equip in a context.

A new feature has been added to the Web Console that allows you to change player names in the web interface. This is useful for moderation purposes or while testing your game.

To change a players name, head to the Players Page, select a player and click their name in the top of the page.

We've released a new Steam authentication endpoint with improvements to both flow and stability.

The improvements feature 2 changes:

• A simplified authentication flow, combining verification with starting a session into a single endpoint.
• New internal retry logic, which will automatically retry failed requests to the Steam Servers.

If you're using the Unity or Unreal SDKs, you do not need to make any changes, if you're using VerifyPlayerAndStartSteamSession to start sessions.

For people doing verification and session separately, the old endpoints will keep working, but we recommend switching to the new endpoint for better performance.

The new endpoint is available at POST /game/session/steam.

LootLocker now has a Notifications system to help your game track and deliver important updates from features like Rewards, Triggers, Leaderboards, and Progressions. Notifications are queued and can be consumed by the game, ensuring players never miss a critical message.

Learn how to make use of Notifications with our documentation.

We have re-released the Triggers feature with a complete overhaul, now built with improved performance, stabiliity and integrated with the Rewards system. The updated Triggers support both limited and unlimited activations, enabling more flexible reward scenarios.

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

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.
• The define symbol LOOTLOCKER_DISABLE_EDITOR_EXTENSION has been added so that it is possible to disable the LootLocker editor extension.

Bug Fixes

• The LootLocker editor extension no longer logs out on compiles and builds.

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.
• Group leaderboard rewards no longer contain the metadata field as it's no longer returned from the backend.

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.