Changelog.

🎉 Unity SDK v8.0.0 is released 🎉 🛡️ The package is now signed for Open UPM supply-chain security! Remote sessions support a provider parameter for smoother account linking, asset listing can be filtered by context, and full API reference docs are live on ref.lootlocker.com. Bug fixes improve path handling and error reporting. ⚠️ Missions & Collectables have been removed.

Find it here

🎉 Unreal SDK v10.4.0 is released 🎉 🚀 Brand-new HTTP execution queue for rock-solid request handling, remote-session QR codes rendered straight to texture, provider-targeted account linking, and full API reference docs on ref.lootlocker.com. Plus: Google Play Games connected accounts, context filtering for assets, and important stability fixes. ⚠️ Missions & Collectables have been removed.

Find it here

🎉 Unreal Server SDK v6.5.0 is released 🎉 🏆 Increment leaderboard scores without reading them first, filter assets by context, and browse shiny new API reference docs live on ref.lootlocker.com — all in one update.

Find it here

Segments now support targeting players using Metadata values attached to their player profile.

New Segment conditions include:

• Have String Metadata
• Have Number Metadata
• Have Boolean Metadata

Each Metadata type supports different qualifier operations, including exact matches, ranges, inclusion/exclusion checks, and boolean value checks depending on the selected Metadata type.

These new conditions can be used in both Triggers and Broadcasts to create more dynamic player targeting and personalized experiences.

Learn more about Segments in our documentation.

Platform Key campaigns can now be used as a reward type across LootLocker systems.

In addition to distributing keys through Squire, you can now reward platform keys directly through Progressions, Leaderboards, Catalogs, and Triggers. This makes it possible to automate key distribution as part of gameplay progression, events, campaigns, promotions, or community activities.

Rewarded keys can be surfaced directly in-game through the Game API or through the Squire Discord bot, creating a much more seamless player redemption flow across both games and community platforms.

LootLocker now supports Stripe as a third-party payment option, allowing you to sell assets, currencies, and progressions directly to players using your existing LootLocker Economy setup as one-time purchases or subscriptions.

Using Stripe Connect, you can connect your Stripe account to LootLocker and start offering purchases through Stripe while LootLocker handles the game-side commerce layer, including entitlements, transaction tracking, and support tooling.

This makes it easy to extend your existing economy beyond first-party platforms and virtual currency flows without building your own custom payment backend.

Learn more about Stripe support in our announcement blog post.

You can now selectively delete specific sections of a player profile directly from the Web Console.

Previously, player deletion actions were limited to removing an entire player profile. With this update, it’s now possible to remove individual categories of player data independently, including inventory, metadata, progressions, files, storage, currencies, characters, and heroes.

This provides significantly more flexibility for customer support, GDPR-related workflows, testing, and live operations management.

If you need similar deletion actions performed across your entire player base, please contact us directly.

All White Label Login emails are now sent from Auth.game instead of LootLocker.io.

This update applies to all authentication-related emails including account verification, password reset, and other White Label Login communication. The change helps further separate game-facing authentication flows from the LootLocker platform while providing a cleaner and more consistent player-facing authentication experience.

Asset Instances now support Metadata.

This means every unique instance of an asset can now store its own custom information using LootLocker’s shared Metadata framework. Metadata can be attached directly to individual asset instances and supports multiple data types including booleans, strings, numbers, JSON objects, and files.

Asset Instance Metadata can be updated dynamically through both the Game API and Server API, enabling more advanced inventory systems, persistent item state, procedurally generated items, durability systems, player customization data, and much more.