Otukan protects your game’s economy from the device it runs on. It detects memory editing, speed manipulation, modded builds and emulator farms while the game runs, and attaches that evidence to every purchase, reward and result your server receives, so your backend keeps authority over the economy. Evaluate it by separating what a cheater can change on the device from what your server still decides. Otukan protects Android and iOS games, including Unity titles, with each signal scoped per platform. It makes cheating slower, costlier and visible, and it is tuned so honest players keep playing without friction.
Client exposure
A mobile game runs on hardware the player owns. Anything held on that device can be read, changed or replayed by a determined player, and the tools to do it are shared freely in cheat communities. Four targets carry most of the loss.
| Target | How it is manipulated | What Otukan detects |
|---|---|---|
| Game state | Currency, health, ammunition or cooldowns rewritten in memory | Memory scanners and editors attached to the game process |
| Execution | The game clock sped up, functions hooked, mod menus injected | Clock tampering, hooking, injected code and altered builds |
| Rewards | Daily rewards, ad rewards and events farmed at scale | Emulators, automation and scripted sessions |
| Purchases | Fake receipts, replayed transactions, patched store callbacks | Hooked or modified clients making purchase claims |
Each row hurts differently. State edits and execution tricks damage fairness, and in competitive games unfair matches push honest players away. Reward farming inflates your economy and drains your ad revenue. Purchase forgery takes money directly.
The two platforms are exposed in different ways, and Otukan treats them separately. On Android, modified game packages spread easily outside Google Play, and emulators make farming cheap to scale. On iOS, cheats more often arrive through jailbroken devices and tweak injection, while sideloaded copies need extra steps. Each detection on this page is scoped to the platform where it applies, and your evaluation should test both if you ship both. For cheat detection in depth, see mobile game anti-cheat.
Server authority
Some decisions must never rest on the client, however well it is protected. Your game server should own them.
- Outcomes. Match results, rank changes and leaderboard entries are accepted only after server-side plausibility checks.
- Purchases. Items are granted only after your server verifies the transaction with the store’s server-side APIs.
- Inventories and ledgers. Currency balances and owned items live on the server, and the client displays them.
- Rates. Progression speed, reward frequency and ad credits are capped by server rules.
Otukan strengthens each of these with a signal the server cannot produce on its own. A reward claim arrives with evidence on whether the client was modified, whether a memory editor is attached and whether the session runs on an emulator. A result from a flagged session can be held, reviewed or discounted instead of accepted at face value. The same pattern protects the requests themselves; see mobile API protection.
That split gives each side a clear job. Otukan raises the cost of cheating on the device and reports what it sees. Your server enforces the rules of the economy.
Player experience
Performance
Players notice a stutter long before they notice a cheater. Protection has to fit your frame budget, so Otukan lets you place checks at natural pauses: launch, match start, reward claim and purchase. Continuous checks are kept for the signals that justify them. Measure a protected build on the lowest devices you support before rollout.
False positives
Honest players run emulators to stream, use accessibility tools, play on older devices and sometimes install software that looks suspicious. Start in observe mode and compare detections with player reports and support tickets before any signal leads to a penalty. Graded responses help: record, then separate matchmaking, then hold rewards, with bans kept for strong and repeated evidence.
Appeal and recovery
Every enforcement path needs a way back. Give flagged players a clear message, a route to support and a review that looks at the evidence your server recorded. Otukan’s detections carry the check, build and platform behind each decision, so your support team can explain it or reverse it with confidence. Sector context is covered on mobile game security, and engine specifics are on Unity app security.