Scenario 1 - New install from a user who has never had the build before – player starts from the beginning of game as expected
Scenario 2 – player has had previous version and has accepted the data transfer prompt – when new build is installed the player continues progress as expected
Scenario 3 – player has had previous version and has NOT accepted the data transfer prompt – in the current version when updating this player can also continue with their current game save despite not having accepted the data transfer. How are you going to handle players in this scenario? Technically this player should have to start again as their data should be deleted from your servers on the transfer day, could you outline the process for data handling on your side?
Regarding the transfer we will need some details from your account.
1. Developer Name – Available on your developer console
2. Email address associated with the account – The target account needs to have an active Google Wallet Merchant account.
3. Transaction ID for the accounts console registration – your Developer registration transaction ID is available on your Google account at payments.google.com
With Google transfers they are auctioned by google rather than automated process:
Party A fill in a form with the details requesting the transfer, Google then action the request and send Party B a mail to confirm. Google say this can take up to 3 days but we have never seen it take longer than 12 hours.
Once transferred Party B will need to make it available for sale again when it have processed the data.
Before Party A start the transfer Party A will need to release the update will Party B process the data on release of the new build rather than wait for the transfer?
Regarding the transaction ID, google say there transaction ID’s will be in one of the following formats.
· 01234567890123456789.token.0123456789012345
· 0.G.123456789012345
· registration-1234ab56-7c89-12d3-4567-8e91234567f8
网友评论