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_EXTENSIONhas 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
InvokeTriggersByKeymethod in place of theExecuteTriggermethod. 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.