AGS 3.33.0 リリースノート

注意

This is an unsupported AGS version. AccelByte no longer provides any updates, bug fixes, security patches, or technical support for these versions. Please refer to the AGS Version Support Lifecycle document for more information.

Last updated on July 3, 2025

Release Date: October 10th, 2022

Client-Side SDK Latest Version:

• AccelByte Cloud SDK Unreal Engine: 18.0.0
• AccelByte Cloud SDK Unity: 15.3.0
• AccelByte Cloud Network-Utilities: 2.5.2
• AccelByte P2P Unity: 0.2.2
• AccelByte Cloud OSS: 0.6.5

Server-Side SDK Latest Version:

• AccelByte Cloud C#: 0.19.0
• AccelByte Cloud Go: 0.29.0
• AccelByte Cloud Java: 0.21.0
• AccelByte Cloud Python: 0.25.0

Here's a look at what's new in AccelByte Cloud 3.33.0:

Highlights

• Login Protection Improvements

  We've implemented a lockout feature to prevent brute force logins. This feature is configurable and works by locking the affected account if the number of failed login attempts exceeds a certain count within a set time period on the same client. In such cases, the account owner will be notified of the failed login attempts via email.

  :::details Related Endpoints

  • POST /iam/v3/authenticate
  • POST /iam/v3/authenticateWithLink
  • POST /iam/v3/oauth/token :::

• Change Activation Status of Two-Factor Authentication for Individual OAuth Clients

  Developers can now activate or deactivate two-factor authentication (2FA) by individual OAuth client in the Admin Portal.

Quality of Life Changes

• Ban Player by Device ID in PlayStation and Xbox

  You can now ban players by device ID in PlayStation and Xbox. This means that, once banned on a device, a player will be unable to login with any headless accounts on that same device.

  :::details Related Endpoints

  • POST /iam/v4/admin/namespaces/{namespace}/devices/bans
  • GET /iam/v4/admin/namespaces/{namespace}/devices
  • GET /iam/v4/admin/namespaces/{namespace}/devices/bans
  • GET /iam/v4/admin/namespaces/{namespace}/devices/{deviceId}/bans
  • PUT /iam/v4/admin/namespaces/{namespace}/devices/{deviceId}/unban
  • GET /iam/v4/admin/namespaces/{namespace}/devices/{deviceId}/users
  • PUT /iam/v4/admin/namespaces/{namespace}/devices/bans/{banId}
  • GET /iam/v4/admin/namespaces/{namespace}/devices/bans/{banId}
  • GET /v4/admin/namespaces/{namespace}/devices/banned
  • GET /v4/admin/namespaces/{namespace}/devices/types
  • GET /v4/admin/namespaces/{namespace}/devices/report :::

• Improved Third-party Entitlement Consumption Sync Reliability

  Our third-party entitlement consumption sync reliability now also records transaction logs with UUID, making it easier to track transactions.

• Import and Export Items from a Store

  When switching between testing environments, you can now import and export selected items from a published store, rather than the entire store each time.

  :::details Related Endpoints

  • POST /v2/admin/namespaces/{namespace}/stores/{storeId}/export
  • PUT /v2/admin/namespaces/{namespace}/stores/{storeId}/import :::

• Role-Based Matchmaking for Flexing Roles

  You can now use role-based matchmaking when configuring flexing roles, giving you greater control over how your game handles matchmaking between players.

  :::details Related Endpoint

  • GET /matchmaking/namespaces/{namespace}/channels :::

• Update the Default Value of Statistics Configurations in the Admin Portal

  You can now update the default value of statistics configurations in the Admin Portal, giving you greater control over how your players interact with and increase their game stats.

  :::details Related Endpoint:

  • PATCH /v1/admin/namespaces/{namespace}/stats/{statCode} :::

• Enhanced App Editor Configurations

  We've made a range of new improvements to the App Editor:

  • All game states are now viewable on the Launcher page.
  • General settings, social links, and feature flags are now accessible in the Configurations page.

• Use the SDKs to Create Lobby partyNotif and Matchmaking Reject Requests

  We've improved our SDKs so you can now use sendPartyNotifResponse and partyNotif to send and receive party notifications amongst party members. You can also send matchmaking reject requests to players through the lobby if there is a player with an empty role attribute trying to enter a role-based game mode.

Breaking Changes

• Golang: Changes in the AccelByte Cloud OpenAPI Specification

  • Model OauthmodelTokenResponseV3 is replaced with OauthmodelTokenWithDeviceCookieResponseV3.
  • Model EntitlementInfo is replaced with TrackedEntitlementInfo.

  For the implementation details, please refer to the migration guide.

Bug Fixes and Minor Changes

• Fixed functional issues in the App Editor, Player Portal, E-Commerce, Armada, Matchmaking, and Lobby.
• Fixed payment issues with PayPal in the Player Portal.
• Added ticketID and createdAt payloads in all events in the Lobby and Matchmaking services.
• Added the Roles parameter to the startMatchmaking function to enable role-based game mode matchmaking.
• 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 AccelByte Cloud.
• You can now delete statistics configuration with tied status.