The Siege of the Old Court: Three Days and Nights Against the Moyu Protocol, the Complete Breaking of the XXTEA Incantation, and an Arsenal of 2,926 Replay Frames

An old court that has reigned for twenty years — its palace keys have circulated among the people for years. Yet the leaked blueprints are not a pass to this campaign: the project bound itself by iron rule to run no finished binaries of unknown provenance and never start the game client. And so a purely technical siege began: one shift every two hours, each shift doing one small archivable thing, dozens of shifts across three days.

I. The Military Order: A Philosophy of Small Things and a Journal Passed Down

The expedition’s order of battle lives in AGENTS.md and journal.md: each shift opens by reading the charter and the journal, and closes by leaving the record of what was completed, discovered, blocked and next. The hard constraints are copied down line by line — local ports only in the 33x00 range, no registering system services, no touching global environment variables, no new automations, no questions, and each shift limited to one small task that can be written to disk. The terror of this military order is its patience: the contribution of any single shift is almost beneath notice, yet looking back after three days, half the banners on the wall have changed hands.

II. The Cryptographic Campaign: From Streaming Cipher to XXTEA

The brightest engagements in the dispatches: the two hops of the heartbeat chain precisely located and the true heartbeat assembly function confirmed by hard evidence, after which the streaming cipher lay fully exposed; the luaU_undump entry pinned, the .dat decryption loader in place, and overnight the case cracked — XXTEA, with the key 666sjmy666. Static disassembly completed the delta and the two-layer structure, the decryption timing was characterized (the triple-empty countermeasure), and finally 41 plaintext-ciphertext pairs were decrypted offline to disk with outputs verified; the key-derivation function fully decoded, the variant analysis pushed to the limit of precision. The Lua asset layer fell the same way: the UIScript virtual path system confirmed, the component system inventoried, the decryption function located within the AES-CBC system, and the master asset index written to disk. The old court guarded its vault with two locks; the besiegers now carry both keys at their belts.

III. The Replay Arsenal: From 72 Frames to 2,926

The protocol front produced equally formed victories: the message-name dispatch system exposed, the complete set of 44 debug and GM commands archived; five generations of probes from spy10 through spy14 iterated, injection saturation characterized, the heartbeat slot captured in stability; MsgSendBuffer.log identified as a full-volume outbound plaintext channel — the court’s own chronicler keeping records for the besiegers. After the recv-side precise call chain and the inbound protocol stack were decoded in full, the RECVFRAME full hook was merged into the packet logger, and the frame dictionary grew from 72 message IDs to 2,926 frames across 32 classes; the plaintext-frame replay stub v4 stands fully ready — the stub server evolving through three generations from v2 to v4, with the direction correction of the login timeout and the three-factor analysis of redirect timing all recorded in the campaign history.

IV. The Accounting of a Siege

Dozens of shifts across three days, not one of them a grand victory, yet not one of them idle: eight minutes of net work per shift, multiplied by dozens of shifts, multiplied by a journal passed from shift to shift — that is the full breakthrough of two fronts, cryptography and protocol. The siege reaffirmed the ancient law: a wall is not taken by one day’s storm-wave but by every shift nailing one small thing into the masonry. The court’s treasure remains unopened (playable single-player still lies ahead), but the keys to the warehouse are complete.