We suggest to use Cloud Script to implement this feature.
For example, you are implementing an exchange mechanism that VC_1 can be exchanged for any other VC, such as VC_2, and things you need to do:
Normally, a player’s profile data, including inventory and VC information will be stored locally in the client. Before initiating the exchange process, you can process another check in the client(for example you can add a slider bar which will show the maximum number of target VC that the player can exchange). But be aware that there should always be verification steps in the Cloud Script in case of abusive uses or cheats.
After the discussion with our team, there is an interesting thing we want to share with you. On step 5, you may reverse the order of granting VC operation (add VC_2 first, then subtract VC_1) because there is a rare chance that the second operation may fail. if the players are granted with target VC first but the original VC isn't subtracted, they are unlikely to report for bonus VC and since it is very rare case, you won't worry about abusive uses. These will also help to reduce the custom service pressure:)
3 People are following this question.
