Changelog.

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.

Finding specific player operations in the Player Manager just got much easier.

You can now filter Player Operations in the Web Console by both event code and date range, making it significantly faster to track down the exact operations you're looking for. Whether you're investigating player issues, reviewing economy changes, or auditing backend activity, the new filtering tools provide a much clearer view into player activity over time.

Squire now supports Claimable Rewards, allowing you to launch reward campaigns directly inside your Discord server.

Players can click Claim Reward directly from a Discord post to receive in-game rewards powered by LootLocker Triggers. By default, rewards can be claimed using a player’s Discord ID, with optional platform account linking through Unified Player Accounts (UPA) to connect rewards directly to in-game profiles.

Claimable Rewards can also be used before your game is live, with no LootLocker SDK integration required to start running campaigns.

🎉 Unreal SDK v10.3.0 is released 🎉 🛒 Major release introducing asynchronous purchases, Stripe Checkout sessions, refund capabilities, platform-specific friends filtering, inventory metadata support, and enhanced request tracing for improved purchasing and social features.

Find it here

🎉 Unreal Server SDK v6.4.0 is released 🎉 🔧 Major release adding context listing, connected account management, enhanced request ID tracking with enriched response context data, plus comprehensive internal refactoring for improved stability and request tracing capabilities.

Find it here

You can now view the status of player notifications sent from the Web Console directly on the player’s profile page.

Under the Notifications tab in Player Manager, all notifications sent to the player via the Web Console are listed along with their read status, making it easy to verify whether a notification has been retrieved by the player’s game client.

Learn more about sending and viewing Notifications in our User Documentation.