Account Server Transfer Feature Announcement
This feature will be officially launched after the update on July 1, 2026.
I. Operation Process
1. Take Screenshots: Take screenshots of your original server account assets (especially collectibles) for verification after the transfer is complete.
2. Bind Email: Log in to your original server account first. Go to Menu (top right) → Settings → Account to confirm that an email address has been bound.
3. Initiate Transfer: Provided you meet the transfer conditions, click the "Account Server Transfer" button on the account page, select a target server (, , ), and submit the transfer application.
4. Wait for Processing: After submission, you need to wait 48–72 hours. During this period, neither the original nor the target server account can be logged into. Upon successful transfer, the account on the original server will be deleted.
5. Complete Transfer: Once processing is finished, log into the target server to view your migrated assets and game records.
Note: There is a special case where the target server and original server have accounts bound to the same email address; such an account will also be frozen and deleted.
Important: Players from the server who plan to migrate to the Mainland China server must use the "Data Inheritance" function. Do not use this server transfer function, otherwise subsequent "Data Inheritance" will become unavailable.
II. Transfer Application Requirements
Users applying for the server transfer service must meet all of the following conditions:
1. Asset Status: The diamonds in the applicant's account must not be negative.
2. Cooldown Period: At least 180 days must have passed since the last server transfer operation on the account.
3. Server Restriction: Only transfers to , , and servers are supported.
III. Data Processing and Operational Rules
1. Scope of Data Migration: After a successful transfer, the player's assets and game records (except rankings, player nickname, and tournament Hall of Fame data; free name change attempts will be reset) will be migrated to the new server.
2. Irreversible Operation: Once submitted, the transfer cannot be undone. The system will delete the old data on the target server as well as any account on the target or original server bound to the same email address (it is recommended to unbind and rebind to a different email in advance), then transfer and clear the original server data.
3. Rollback on Failure: If the transfer fails, all accounts will be restored to their state before the transfer.
4. Processing Time: The transfer will be completed within 48–72 hours after initiation. During this time, both the original and target servers cannot be accessed due to data processing.
IV. Risk Notification and Player Obligations
1. Diamond Status: Players are obligated to ensure that the original server account does not fall into a negative diamond status during the transfer period (including the 48–72 hour processing window).
2. Consequences of Breach: If the transfer fails due to negative diamonds, any resulting data loss, asset reset, etc., shall be borne by the player, and no refund or compensation will be provided.
3. Data Deletion: Once the transfer process succeeds, the original server data, target server data, and any account bound to the same email will be permanently deleted. The platform is under no obligation to retain data backups.
V. Platform Disclaimer and Technical Services
1. Technical Failures: If the transfer fails or data errors occur due to platform server failure, network interruption, or technical vulnerabilities, the platform undertakes to make reasonable efforts to restore the data to its pre-transfer state or provide equivalent virtual asset compensation.
2. Force Majeure: The platform shall not be liable for delays or failures caused by force majeure events (including but not limited to natural disasters, government regulations, basic telecommunications network paralysis, etc.).
VI. Final Interpretation and Dispute Resolution
Rule Modifications: The platform reserves the right to adjust, modify, or terminate the rules of this feature. If a user objects to modified rules, they should cease using the service; continued use constitutes acceptance of the modifications.