Candy Crush Saga and Proxies: Offline Gameplay, Online Account

Region, the server side and behaviour recorded to the account

In this game the word "region" describes two separate things, and the two get confused. The first is the infrastructure side: your requests are routed to a server region close to you, and that selection is mostly made according to the address the request comes from. This routing is a performance decision; it does not determine which content you see.

The second is the account side. Your progress, the items you have purchased and your event participation are kept tied to your account; these do not change because the server region changes. Connecting from another country does not move, reset or unlock a different catalogue for your progress. Routing only changes the point the request goes out from; it touches nothing recorded to your account.

There is a simple way to see the difference: a publicly available page opened in a browser may show a different language or a different campaign depending on the exit country, while the in-game progress screen stays the same. The first behaviour looks at the network address, the second at the account record. If you are doing verification work, these two layers need to be checked separately.

Device and account settings enter the picture too. In most setups the interface language depends on the device's language setting and regional formats on the operating system's region setting. These do not change when you change the network exit; if you see an unexpected language, looking for the cause in the device settings first gives faster results.

What does your rule cover, depending on where you write it?

Scope equals where the rule is written. On mobile, a proxy written into a wireless network profile applies only on that network; when you switch to another network or fall back to cellular data, it is silently disabled. This behaviour is not a bug, but it is the most common scenario in which traffic leaves over the normal line while you believe the setup is working.

A configuration written into the router covers every device on that network and does not depend on the app's preference; in return, it affects the other users at home as well. An application-based rule gives the narrowest scope and has the fewest side effects: only the process you select leaves through the tunnel. For the steps involved in device settings, the Android and iPhone proxy settings guides are sufficient.

After setup, verify three things in order. Confirm that your exit address is in the country you expect, test where domain resolution is performed with DNS leak test , then make sure the app still opens and syncing works. On dual-stack setups, also check that the IPv6 path does not bypass the rule: if your exit carries IPv4 only, the operating system can prefer IPv6 and effectively disable the proxy.

What does latency actually affect in this game?

Routing adds a hop to the connection, and total path time lengthens in most setups. But the area where the effect shows in this game is narrow: because level gameplay runs on the device, moves are not affected by latency. The difference appears at transitions between screens and at moments that wait for data from the server — saving the end of a level, opening the events screen, loading the leaderboard.

What bothers the user at those moments is usually not average latency but variance. The average can look fine while a single slow request keeps the screen waiting and the experience suffers. That is why, when evaluating an exit, you should compare several measurements taken at different times of day rather than a single one; on shared pools, peak-hour variation is the variable a single measurement hides.

There is a rare exception: if your default route is circuitous, a backbone that connects more directly to the target can produce a shorter path overall. This is not a rule and can only be confirmed by measurement. For the definition of the concept, see the proxy latency article; to test whether an exit is alive, the proxy checker tool is the starting point.

There are two simple rules for setting up a measurement correctly. First, make the comparison against the same target: two figures taken from different servers are not interchangeable. Second, measure back to back with the rule on and off and note the difference; the absolute figure says nothing on its own, what matters is the difference between the two states. If that difference changes noticeably within the hour, the problem is not the exit itself but how busy that exit is at that hour.

Use cases where routing pays off

For an individual player, most of these setups are unnecessary. The scenarios that pay off belong to users doing verification work around the game rather than playing it. Testing whether the app opens from behind a corporate network, reproducing a support ticket with a different exit, and seeing how a campaign page looks in another country are chief among them.

The second group is measurement work. Monitoring the volume transferred on update day from a single point, distinguishing whether a network fault originates from the line or the app, and determining which port is closed on a restricted network are technically meaningful and rule-compliant jobs. What these jobs have in common is that they change only the network path without touching the account itself.

The question to ask when deciding is this: is what you want to change the network path, or the content your account sees? The first is the domain of routing. The second is tied to the account record and does not change with network configuration; trying to force it neither works nor complies with the terms of service. For verification needs on the marketing side, the price comparison proxy page offers a separate framework.

If you work as part of a team, one recordkeeping habit makes these jobs easier: writing down which verification was done with which exit label keeps the picture readable when you have to repeat the same test weeks later. Otherwise you end up with two different results and cannot tell whether the difference comes from the app, the exit, or the time of measurement.

Symptoms, responsibility and cases where it is not needed

Most rows in the table trace back to a single root cause: the scope being narrower or broader than assumed. The first step in diagnosis is always the same — turn the rule off temporarily and repeat the same operation. If the symptom persists with the rule off, it has nothing to do with routing.

The responsibility side should be clear too: this page was not written for account duplication, automation, working around store rules, or interfering with the game's progression mechanics. Compliance with the terms of use of the game and the device store is the user's responsibility.

And finally, the most honest answer: if you are playing on your own line with your own account, you need none of the setups described here. Routing does not make you faster; it only adds a quota line item, a latency margin and one more layer to diagnose. It pays off only in the verification and measurement jobs listed above.