Changelog.

The Server API has been updated to allow you to create players using the new /server/player endpoint.

This is useful if you want to create players in your game server and then use the LootLocker API to manage their inventories, rewards, and other features.

You can now use the numeric Asset IDs as input when searching for assets in the LootLocker Console.

It is now possible to remove promoted UGC from the Game API. Calling the delete endpoint even for promoted UGC will no longer return an error.

The players pages have received the following updates:

• Greatly improved loading times for the players list page.
• Moved all/recent + pagination to the URL, making it easier to share links.
• Fixed an issue where the player page would load the wrong data when switching between all and recent players.

🎉 Unreal SDK v5.3.0 is released 🎉 Exciting updates! Introduced new Player Info endpoints, enhanced Player and Asset Metadata, and streamlined UGC creation. Get specific currency details easily now. Steam auth is smoother, and asset contexts can handle multi-equip. Note deprecations for cleaner integration. Check the full changelog!

Find it here

🎉 Unreal Server SDK v3.3.0 is released 🎉 Exciting updates! You can now schedule leaderboards via the Server SDK, access leaderboard ULIDs for enhanced interactions, and leverage versatile metadata for both players and assets. Dive into the full details in our changelog!

Find it here

🎉 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.