The Honest Ledger Toward Playability: The Moyu Completion Audit, the fdeb Attack Plan, and a Four-to-Eight-Week Exchange Rate

The master on the throne asked the plainest and hardest question: when can I play the single-player version, and what is still missing? The answer of shift 279 was not a military dispatch but a balance sheet in the accountant’s sense.

I. Three Lines of the Completion Ledger

The books were kept honestly: protocol reverse engineering 95 percent (heartbeat formula, handshake, dispatch, protobuf all broken); bot automation 80 percent (mission chains, leveling, monster-finding and movement all verified, kill counting awaiting final confirmation); memory injection 70 percent (the chain open, active-session verification pending). And protocol-layer single-player — the former main channel — is proven dead (the VM plus RNG double lock). The ranking of viable routes settled accordingly: A. bot substitution on official servers (most mature, run at night); B. memory-injection dummies (skeleton through); C. world-stream replay (a research direction).

II. The Three Mountain Passes to Playable

The gap list was pinned in order: the fdeb verification bypass (the largest choke, one to two weeks) — one must learn what the client’s VM emits after processing fdeb (a key? a flag?); basic server logic (two to four weeks) — maps and pathfinding, monster spawning and AI, experience, levels and equipment, NPC dialogue and missions, all written from zero, the heaviest labor; protocol completion (one to two weeks) — only part of the C2S commands (movement, attack, heartbeat) are broken; the C2S of NPC, missions, items and skills and the S2C of missions, NPCs and items remain unanalyzed. In total: four to eight weeks of full-time work if all goes well. And if fdeb cannot be bypassed, the single-player version is not feasible — the fallback was written into the list itself.

III. The fdeb Plan: Watch the Doorway, Not the Room

The plan ranks by feasibility, and its first item is the most engineering-minded: hook the entry and exit parameters of the VM function (0x31a4090 at entry, 0x2b33cc9 after return) and compare the input-output correspondence across multiple fdeb samples — no need to understand the VM’s interior, only to know whether the output is a simple function of the input: if so, the stub can reproduce it; if an internal key is mixed in, then go dig for the key. Three auxiliary probes follow: parse the 960-byte answer for a verification field; probe with an all-zero fdeb to distinguish format error from security check; and differential analysis across samples for the mathematical relation. The old ambiguity — replaying fdeb to the stub leaves the client silent — now has three hypotheses (failed verification, malformed packet, missing prior initialization) and a discriminating experiment for each.

IV. The Two-Track Exchange Rate

The recommended path runs on two tracks: mature the bot substitution first (one to two weeks: auto leveling, missions, combat, overnight play), while fdeb research continues — if it breaks through, the single-player revives; if not, the bot is the final form. This is the forward exchange rate table: four to eight weeks at the optimistic price, fdeb as the lever, the bot as the floor. To translate can I play it into what is missing, how many weeks each costs, and which segment can go to zero — that translation is the most expensive deliverable of the day.