Changelog.

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.

It is now possible to Ban Players permanently or temporarily from starting sessions in your game. This can be done through the Web Console by navigating to the player page, selecting Actions and then selecting Ban Player. It is possible to leave an optional note attached to the action, for example providing a reason for the ban.

A banned player’s player page will clearly display that the player has been banned, and provide buttons to view notes or to unban the player.

You can now prevent specific players from starting new game sessions directly from the LootLocker Web Console.

To ban a player:

1. Navigate to the player’s profile.
2. Open the Actions dropdown in Player Information
3. Select Ban Player and select the optional ban duration.
4. Add an optional internal note, such as the reason for the ban.

Once banned:

• The player will be blocked from starting new sessions.
• The player profile will clearly display their banned status.
• You can view associated notes or reverse the action using Unban Player.

This provides a straightforward and immediate moderation tool for customer support or community managers for managing disruptive or cheating players. More information can be found in our User Documentation.

You can now apply Segments directly to Triggers, ensuring that only players who qualify for a specific segment are able to execute a trigger.

This gives you precise control over who can activate rewards, content, or game logic, unlocking powerful new use cases, such as:

• Platform-specific rewards (using a Played On segment)
• Playtime-based rewards (using a Playtime segment)
• Re-engagement rewards for lapsed players (using a Last Seen segment)

And far more.

With Segments and Triggers working together, you can tailor live operations and reward logic to exactly the players you want to reach.

Explore the updated Triggers in the Web Console today.