Skip to main content
Everything outside the game protocol: permissions, third-party SDK wiring, and the Java↔native↔C# bridge. None of it duplicates or gates the SFS2X/HTTP game protocol; this layer is platform shell, cleanly separable from the client a Go reimplementation needs.

Why the permissions you wouldn’t expect

A war-strategy game asking for CAMERA/RECORD_AUDIO/calendar access looks suspicious until traced to real, named features:

Third-party SDK inventory

Cleartext HTTP is allowed, but the two cleartext endpoints are dead in 1.0.364. usesCleartextTraffic="true" is set at the manifest level, and the network security config permits cleartext with system CAs only. The app still contains two FunPlus-owned plain-HTTP endpoints, but neither is called by this build (static-analysis-only):
  • analyse-aps.readygo.tech/{postback,clientevent}.php, push-analytics beacons, lives in RecordHttpUtil, which has no callers, and the PushRecordManager.RecordToHttp* methods have empty bodies.
  • upload-img-aps.readygo.tech/get_apk_ver.php, a side-loaded self-update check, runs only for the package com.readygo.aps.gp, not com.fun.lastwar.gp.
Neither gates gameplay; a Go client can ignore both. Earlier versions of this page said both were called.

Remote kill switch

At startup, libil2cpp.so calls into the Java class ConfigFetch, which fetches a remote flag over a raw SSLSocket with a spoofed okhttp/3.12.1 User-Agent (static-analysis-only; the call site is inferred from class, method, and base64 URL strings in the .so):
The integer body goes to the native Java_com_common_ConfigFetch_setConfig, which calls exit(0) when the value is 1 on a release build (2 on a debug build), confirmed by arm64 disassembly. It’s a vendor kill switch for the app process, not part of the game protocol, and a Go client never needs it. Whether the request even resolves is open: Base64.DEFAULT appends a newline to the encoded package name.

The JNI split for anti-cheat is worth knowing

libanogs.so (Tencent ACE) has a full Java wrapper class (com.gamesafe.ano.AnoSdk) that turns out to be dead code. C# calls into the native library directly via [DllImport("anogs")] P/Invoke, bypassing Java entirely. Its detection/report data appears to travel over a local Unix pipe to Tencent’s own backend, not the FunPlus game server’s wire protocol.