Use your current game values. Numeric cases below are illustrative; exact game rates and prices have not been independently tested.
Identify the exposure first
The official game description says players can attack others and steal cash. It does not specify how much can be stolen or give public banking fee and interest rules. Read those rules in your current client before transferring a large balance.
Separate cash you need for an immediate purchase from cash you are holding for later. Then check whether any storage option changes availability, fees or exposure.
Compare a known fee with an estimated loss
Illustration: protecting 10,000 cash for a confirmed 2% fee costs 200. If you estimate a 10% chance of losing 3,000 while exposed, the expected loss is 300. In that simplified scenario protection has a lower expected cost. The fee, probability and loss are hypothetical, not game rules.
Expected loss is not a guarantee. Repeated attacks, withdrawal fees, timing and limits can change the result. If you cannot estimate the risk, keep it marked unknown rather than presenting a precise percentage.
Before a long absence
- Check your current wallet and planned near-term purchase.
- Read any deposit and withdrawal fee shown by the game.
- Confirm whether protected cash remains usable and whether there is a limit.
- Check crew equipment and visible defense information.
- Record balances so you can investigate changes after returning.
A purchase also changes cash exposure, but that alone does not make it a good investment. Compare the investment’s return independently.
Review the outcome
On return, distinguish attack losses, fees, spending and collectible income. Check a history or log if the client provides one. An unexplained balance change is not proof of a particular hidden rule.
Use the session checklist for your routine, offline measurements for earnings, and family coordination for shared objectives.
What attack risk would make a fee worthwhile?
For a simplified one-loss scenario, let F be the total known protection cost, L the cash loss in the event you are comparing, and p its probability over your planned absence. The expected unprotected loss is p × L. The break-even probability is F ÷ L, provided L is positive. This comparison assumes protection actually prevents that loss and excludes liquidity value and other fees.
| Hypothetical total fee | Hypothetical loss if attacked | Break-even probability |
|---|---|---|
| 200 | 1,000 | 20% |
| 200 | 3,000 | 6.67% |
| 200 | 10,000 | 2% |
If your risk estimate is unknown, this table does not make it known. It tells you which uncertainty matters. A threshold above 100% means that fee is larger than the one loss considered even if it happens; multiple losses would require a different model. A zero loss gives no meaningful threshold.
Read whether a fee applies on deposit, withdrawal or both. If a hypothetical deposit removes 10%, depositing 10,000 produces 9,000 protected cash. Returning that same amount through another 10% deposit later leaves 8,100, before other changes. Avoid counting repeated transfers as a single fee. This example is arithmetic, not a claim about today’s Bank rules.
Keep a necessary purchase reserve separate and compare combat costs over the same time window as the fee. A lower expected loss does not guarantee an outcome in your next session.
Apply this to your next decision
A planned attack needs a spending limit and a clear objective as well as a cash-protection decision. Compare PvP rewards with possible losses →
Sources & scope
Core systems are described by the developer. Strategy is editorial guidance unless a specific test is cited. Exact prices, unlocks and rewards should be checked in your current game.
Report a discrepancy