backend-reversinglisted

# Backend Reversing Reconstruct a server from a client. The client is a deterministic state machine that must parse, validate, and serialize everything the server understands — so the compiled client already contains the complete shape of the protocol. This skill walks that shape out of the binary and turns it into a running emulator, and it pairs each step with the hardening that would have stopped it. ## Before anything: scope and footing This pipeline only makes sense — and is only appropriate — against a target you are allowed to analyze. Confirm one of these holds before you start, and say which in your report: - **Preservation** — a defunct or offline game whose official servers are gone, or a game with an offline/single-player mode you are studying locally. - **Ownership** — software you wrote or own. - **Authorization** — a sanctioned engagement, bug-bounty scope, or written permission to test. - **CTF / research** — a challenge target or a lab environment built for this. Two things this skill deliberately does **not** do, because they move the work out of that scope: circumventing live-service anti-cheat or DRM to force a protected client into an analyzable state, and defeating certificate pinning or instrumentation-detection on a production service. Analyze a target that is already in a state you may study — an offline build, a local instance, a defunct client — rather than breaking an active protection to get there. If the user needs the protection gone fi