182 lines
11 KiB
Markdown
182 lines
11 KiB
Markdown
# Supplied APK: static analysis and reconstruction boundary
|
|
|
|
[CLIENT_CHECKS.md](CLIENT_CHECKS.md) records the focused detection audit:
|
|
active battle anomaly checks/reporting are present; the retained `roboCheck`
|
|
entry returns unconditionally, and server-side script identification remains unknown.
|
|
[BATTLE_RULES.md](BATTLE_RULES.md) details the battle conditions and verifies
|
|
the existing V4 cap/check placement against the APK's packaged bytecode.
|
|
|
|
Native Qt companion: [RANCH_HELPER.md](RANCH_HELPER.md) documents incubation
|
|
monitoring, configurable ranch actions, the recovered 749-monster catalog,
|
|
password login with official server selection, recurring tasks, unlocked maps,
|
|
and ADB farming. The new page-screenshot tab saves user-triggered samples for
|
|
assistant-generated button configurations; no manual cropping is required.
|
|
The helper now provides multiple independent account tabs, DPAPI-encrypted
|
|
password/token persistence, role-specific policies, right-click refresh and a
|
|
decoded request/response debug dialog with an automatic redacted log. Launch
|
|
`Start_Ranch_Helper.cmd`. 88 local tests pass. The user confirmed live login and
|
|
role retrieval; actual multi-account automation and inventory writes remain
|
|
unverified. See the helper report for exact limits.
|
|
|
|
[API_INVENTORY.md](API_INVENTORY.md) lists 116 game-side paths (115 with send
|
|
call sites, one declaration-only) and 13 SDK call variants, with purposes,
|
|
request fields, callback fields and source locations; CSV and JSON are included.
|
|
The actual login log's two complete servers plus two `$ref` aliases now normalize
|
|
to two region options with matched role names; offline replay of that log passed.
|
|
The later `enterGame` 990 rejection led to two verified client corrections:
|
|
the signature date uses the full four-digit year, and the APK tracking channel
|
|
is `taptap` while the game channel is `DYD`. The user's subsequent successful
|
|
snapshot exposed `vipInfo=null`, which blocked rendering; that is fixed, and
|
|
offline Qt replay shows the received incubation, eggs, monsters and pasture.
|
|
|
|
V4 follow-up: [BATTLE_V4.md](BATTLE_V4.md) identifies the unchanged AIR
|
|
extraction-cache ID as an omitted build input. The new damage-only package
|
|
refreshes that cache through AIR's normal versioned extraction path. The
|
|
installed V3 package was inspected read-only. The user subsequently confirmed
|
|
that the V4 damage multiplier works; no new combat APK was built for the helper.
|
|
|
|
Battle-patch follow-up: see [BATTLE_V3.md](BATTLE_V3.md) for the two confirmed
|
|
bytecode defects in the previous modifications, the V3 builds and their
|
|
visible runtime checks. V3 gameplay has not yet been verified on the device.
|
|
|
|
Date: 2026-11-07 (Asia/Shanghai)
|
|
|
|
## Scope and evidence
|
|
|
|
Target: `牧羊人之心_1.9.68.apk`, 1,700,248,417 bytes, SHA-256
|
|
`01678ee3a8465d818d32cbbd94baa0d8253b04b4c57b70ebc5544ed341f1015d`.
|
|
All ZIP member CRC checks passed. This does not verify provenance or signature
|
|
validity. The APK was not executed and no game server was contacted.
|
|
|
|
The connected REA Android provider was unavailable initially because
|
|
`REA_JADX_MCP_JAR` was not configured. The required JAR was downloaded from
|
|
its official release and its SHA-256 matched `jadx-headless-mcp.sha256`, but
|
|
the already-running REA server did not inherit the new environment variable.
|
|
Consequently, the observations below about ActionScript come from local
|
|
JPEXS FFDec 26.4.0 decompilation, not REA Evidence records. Both downloaded
|
|
tool archives matched their published SHA-256 values.
|
|
|
|
`MYRMain.app` is an uncompressed FWS SWF (version 46). JPEXS exported 1,273
|
|
classes under `net.pixvi.myr` and the selected framework/network classes to
|
|
`analysis/as3/scripts`. Decompiled output is reconstructed source, not the
|
|
developers' original source files or the server implementation.
|
|
|
|
## Direct static observations
|
|
|
|
- AIR application ID: `air.net.pixvi.myrzx`; version `1.9.68`; entry
|
|
`MYRDyd.swf`; AIR namespace 50.2; portrait, GPU rendering.
|
|
- AIR additions request `minSdkVersion=16`, `targetSdkVersion=29`.
|
|
These are client declarations, not a runtime compatibility guarantee.
|
|
- Archive: 22,340 entries, including 11,713 hashed files in `assets/codes`,
|
|
8,398 JSON files, 1,876 MP3s and 204 PNGs. The two root
|
|
`assets/data/table` files do not prove that all game configuration is local.
|
|
- Main logic uses ActionScript/Starling and preserves package/class names and
|
|
original developer filesystem paths in debug metadata.
|
|
- Default center URL: `http://120.132.6.157:9099/`; resource URL:
|
|
`http://resource.myrzx.cn/updateserver1/verFfcs/`. Runtime configuration
|
|
can replace the center address. No claim is made that either is operational.
|
|
- Platform Java/DEX strings include `gameapi.diyidan.net` account/payment
|
|
endpoints. Those are separate platform services, not the ActionScript game
|
|
API's proof of behavior.
|
|
|
|
## Recovered game protocol
|
|
|
|
See `analysis/endpoints.json` for 111 unique path strings extracted from 31
|
|
network classes. Their presence does not prove reachability or behavior.
|
|
|
|
- `HttpRemote` sends a POST whose body is a single encoded string. Normal
|
|
requests declare `application/x-www-form-urlencoded`; selected payment
|
|
calls use `application/json;charset=UTF-8`.
|
|
- `NetCenter.send` adds `token`, `reqid`, and retry counter `reqsid` before
|
|
JSON serialization. `GameMath` enables normal/payment encryption by default.
|
|
- `Crypter` performs AES-ECB with PKCS#5/7 padding and Base64 input/output.
|
|
The default client key is embedded in `NetCenter`; resource table
|
|
`game_setting.xyz1` may replace it. This is obfuscation, not transport
|
|
secrecy. No key was used to contact any external system.
|
|
- Successful JSON uses `resCode: 0`, commonly with `resMsg`. `NetCenter`
|
|
aliases `resCode` to `re`. `408` is a login-expiry path; some other codes
|
|
force exit. Unknown semantics should not be guessed from code numbers.
|
|
- Login response readers require `playerInfo`, `servers`, and `masterInfos`.
|
|
`ServerVo` reads server id/name/status, platform/channel and game/pay URLs.
|
|
- `masterService/masterQueryDetail` returns the main role snapshot;
|
|
`queryMasterSecondDetail` optionally supplies `data` or legacy code `997`.
|
|
The main reader expects `master`, `history`, `activityHistory`, `stacks`,
|
|
`alchemyStacks`, `monsters`, `items`, `exploreTeams`, `currentTasks`,
|
|
`rooms`, `teams` and other nested structures.
|
|
|
|
Primary client evidence files: `analysis/as3/scripts/net/pixvi/myr/net`,
|
|
`analysis/as3/scripts/com/hurlant/crypto/Crypter.as`,
|
|
`analysis/as3/scripts/net/pixvi/myr/center/AccountCenter.as`, and
|
|
`analysis/as3/scripts/net/pixvi/myr/center/MasterCenter.as`.
|
|
|
|
## What was built
|
|
|
|
`backend` contains an independent local Python/SQLite prototype implementing
|
|
the codec and a small account/role lifecycle. Tests cover a FIPS-197 AES
|
|
vector, Unicode codec round trip, and an encrypted HTTP account-to-snapshot
|
|
flow. See `backend/README.md` for exact scope and limitations.
|
|
|
|
## Unresolved / not claimed
|
|
|
|
- No bit-identical APK, original build project, backend source, or complete
|
|
playable clone was produced. Rebuilding byte-for-byte from this artifact is
|
|
not a meaningful goal: signing, compiler/runtime versions, original sources
|
|
and build inputs are unavailable. Repacking the same files would copy the
|
|
artifact, not reproduce its development project.
|
|
- The prototype has not been connected to the original client. It still lacks
|
|
verified resource manifests, client redirect configuration, and complete
|
|
nested response schemas. Empty snapshot arrays can fail client assumptions.
|
|
- Reflection, dynamically loaded code, patched/update resources and runtime
|
|
server responses remain outside this static search boundary.
|
|
- The client contains developer-login and plaintext HTTP remnants. They are
|
|
security observations only; no bypass or production endpoint was attempted.
|
|
|
|
Any redistribution, public service, or reuse of copyrighted art, music and
|
|
code requires permission from the respective rights holders.
|
|
|
|
## Ranch automation update — 2026-11-07
|
|
|
|
The Qt helper now has an explicit 自动孵蛋 page with independent market-buy,
|
|
hatch, dispatch, collect and feed switches, preview, monitor-only, start and stop.
|
|
The coin preset selects the Lilitos coin market and only green-slime incubation,
|
|
priority 1, dispatch, reorder below 1 to 10, retains 4+ stars/A+ grades and
|
|
disables feeding. The backpack table now holds explicit per-species rules;
|
|
unchecked eggs cannot hatch or trigger buying. Market draws
|
|
remain random; the shipped Lilitos price is 100 coins per egg, not a guarantee
|
|
of green-slime-only purchases or a fixed net profit.
|
|
|
|
Purchases use the normal `gachaService/gachaGetEggs` payload, zero vouchers,
|
|
unlocked-city checks, a target inventory, batch size, reserved coin balance and
|
|
restart-persistent per-role daily spending records. The real response's city-ID
|
|
array form is supported alongside boolean maps. Feeding uses the smaller of
|
|
the configured target and the current breakthrough cap (`potentialLevel * 10`);
|
|
unknown caps stop feeding. Yield rows have star filters, and quest rows show
|
|
coin and premium-currency rewards. See `RANCH_HELPER.md` and the helper README.
|
|
|
|
88 tests pass, including an encrypted-HTTP ten-draw -> returned bonus eggs ->
|
|
hatch -> maturity -> dispatch -> refreshed-balance cycle, timeout accounting,
|
|
per-species priority/reorder rules, multiple capped feeding recipients,
|
|
confirmed manual inventory actions and price-checked slot/pasture expansion.
|
|
The retained real response's empty-slot sentinel is -1; this previously blocked
|
|
hatching, and is now treated as empty along with zero. Offline replay now plans
|
|
three non-VIP hatches. Expansion prices derive from actual facility openType
|
|
counts, matching HistoryVo, and stale quotes require a new confirmation.
|
|
|
|
The compact login tab hides protocol fields and no longer opens the debug dialog
|
|
automatically. Monster rows show breakthrough, reference stats, affection and
|
|
gift preferences. Equipment, entanglement and global bonuses are excluded from
|
|
the labeled reference stats. Right-click management supports lock/unlock,
|
|
confirmed dispatch and feeding. Slot and pasture pages support confirmed normal
|
|
coin/premium expansion; VIP status is separate.
|
|
The bottom log is resizable via a vertical splitter and can be hidden without
|
|
stopping capture; size and visibility restore with account/role settings.
|
|
Growth handling follows both phase transitions and applies the settlement
|
|
response's modes/qualities before inventory planning. Pending values are no
|
|
longer labeled C/C/C/C, and stale role queries cannot overwrite unsettled cached
|
|
growth. Explicit sync remains separate from dispatch/feeding, and exact
|
|
protection reasons are visible. Capacity planning also handles roomId=null for
|
|
incubator monsters; replay of the retained mature response now yields the two
|
|
protected collections and two dispatches expected by the user's saved rules.
|
|
The native multi-account UI was rendered with synthetic data. No live account
|
|
inventory operations or device actions were performed during this update.
|