Connect cross-platform accounts & identity management
Client-Side SDK Latest Version:
Server-Side SDK Latest Version:
Here’s a look at what’s new in AccelByte Cloud 3.32.0:
New Item Type: Extension
You can now use the item type extension when creating new items. Extension allows you to create and support custom services, giving you the ability to customize and enhance the types of purchases available to your players. The entitlements and fulfillment of your extension item will be automatically integrated into your custom service.
This feature is currently only able to be created using APIs.
Enhanced App Editor Configurations
We’ve made a whole host of new improvements to the App Editor, including:
Improve Accuracy in Store Category Search Results
We’ve improved our APIs to allow developers to choose to display items only from a particular category or include items from its all sub-categories’ as well
SDK to Support Multi-Platform Wallet
You can now use
FRegistry::Wallet.GetWalletInfoByCurrencyCodeV2 to manage multi-platform wallets using the SDKs.
Support for Option Boxes in Single Game Template Launcher Stores
You can now use Option Boxes in Launcher Stores that use the single game template by setting the Required Game value on your Option Box.
endDateon Ban event payload to comply RFC3339 format.
ABPresence.hwas renamed to
FAccelBytePresenceStatusdue to conflicting names with another class found in another plugins.
Telemetry events data are now cached, meaning that if the game crashes unexpectedly, any previous data will be sent automatically after the game has restarted and the player has successfully logged back in to the AccelByte Cloud.
Fixed functional issues in the App Editor, Player Portal, Launcher, E-Commerce, Multiplayer V2, Session History, Session Browser, IAM Input Validation, and Dedicated Server Manager.
Now you can view Player Records on the User Details page of the Admin Portal.
In the Player Portal, Option Box items will now show a message if a player already owns the content.
Fixed bulk user ban endpoint. This endpoint now retrieves correct responses and no longer times out when trying to ban 100+ users in bulk.
Reduced Session History’s data fetching runtime by shifting endpoints from the Matchmaking service to the Session Browser service. The old Matchmaking endpoints will be marked as deprecated. If you use any of these endpoints, make sure to switch to a substitute endpoint listed in the current endpoint.
You can now specify a session timeout limit for deployments and overridden deployments.
Fixed an issue where local server sessions were not being deleted once they shut down.
You can now update your player count dynamically in dedicated servers after the session has started matchmaking.