Media
5 items
Description
A Chrome extension to capture and analyze WebSocket traffic for Goodgame Empire. GGE WebSocket Studio is a Chrome extension that captures, decodes and explains the WebSocket traffic exchanged between the browser version of Goodgame Empire (EP) and its servers. It turns a stream of raw frames into something readable: named commands, annotated payloads, searchable history, and for those who want it, a full scripting environment for automating request/response sequences It is built by the gge-tracker.com community and is aimed at players, tinkerers and developers who want to understand how the game actually talks to its servers ──────────────────────────────────────── CAPTURE AND ANALYSIS • Live capture of every WebSocket frame, in both directions, as the game runs • A dedicated DevTools panel, plus a standalone Studio window if you prefer to keep the traffic on a second monitor • A single on/off toggle in the toolbar popup • No Chrome Debugger API is used and no debugging permission is requested ──────────────────────────────────────── READABLE OUTPUT, NOT JUST RAW FRAMES • Full decoding of the game's %xt% protocol: server ID, command code, status code, version and JSON payload are split out and displayed as separate fields • Over 1,000 command codes are mapped to human-readable names, covering both directions (client-to-server and server-to-client) • Payload inspection with syntax-highlighted, pretty-printed JSON • An "Explain" mode that annotates individual payload keys with what they mean, key by key, for more than 500 known commands • One-click copy of any payload, auto-scroll toggle, and a Player Info view built from the game's own boot-data packet (player ID, account creation date, account flags, and more...) ──────────────────────────────────────── SENDING AND SIMULATING • Send a crafted frame to the server exactly as the game client would send it, and watch the reply arrive in the log • Simulate a server response: a synthetic frame is delivered to the game client so you can observe how the interface reacts. Nothing leaves your browser and the server never sees it - useful for studying client-side behaviour in isolation ──────────────────────────────────────── COMMUNITY WORKSHOP • A built-in Workshop lists scripts shared by other players, read from a public, open community catalog • When a shared script is updated, Studio shows a line-by-line diff between your copy and the new version, and applying an update switches the script off again so nothing new starts running behind your back ──────────────────────────────────────── SCRIPTING FOR DEVELOPERS Studio includes a complete scripting layer for anyone who wants to go beyond reading traffic Two kinds of script: • Listeners react. The body runs once for every incoming frame, and only while the script is switched on. Ideal for "whenever X happens, do Y" • Actions are sequences. The body runs from top to bottom when you trigger it from the Actions menu or with a keyboard shortcut (Alt+1 to Alt+9). Ideal for "send this, wait for that, then send this" What a script can use: • message - the raw frame as received • packet - the same frame already parsed: .cmd, .json, .status, .raw, .dir, .valid • send(payload) - send a frame to the server • simulate(payload) - deliver a synthetic frame to the game client • await request(payload, { expect, timeout }) - send and wait for the matching reply in a single step, avoiding the race you get from sending and then listening • await waitFor(matcher, timeout) - pause until a matching frame arrives. Matchers can be a command name, a regular expression, a predicate function, or a combination • await sleep(ms), await runAction(name) - compose long flows out of smaller named ones • log(...) - print to the built-in console • setInterval / setTimeout - cleared automatically when a script is stopped, edited, disabled or deleted, so duplicates can never pile up • await prompt / alert / confirm - panel-rendered dialogs, awaited for you • A "Globals" block that runs once at start-up, for values that must survive between frames (counters, caches, configuration) The editor: • Syntax highlighting, line numbers, indentation guides and bracket matching • Context-aware autocompletion for the script API, packet fields, JavaScript keywords and command codes, with inline documentation and signature hints as you type • Live syntax checking, with errors reported before you save and located in either the globals block or the body • A searchable reference section documenting every function with examples, common pitfalls, and starter templates for the usual patterns • A cheat-sheet rail beside the editor showing what is available in the current mode ──────────────────────────────────────── PRIVACY • All capture, decoding, storage and script execution happen locally, in your browser • Captured traffic is never transmitted anywhere. There is no analytics, no telemetry and no account • Your scripts are stored locally in the browser • The only network request the extension makes on its own is a read-only fetch of the public community script catalog, and only when you open the Workshop tab • The extension is active only on 'empire.goodgamestudios.com' and 'empire-html5.goodgamestudios.com'. It requests no permission to read or modify any other site • User scripts execute inside a sandboxed iframe with no extension privileges ──────────────────────────────────────── INTENDED USE GGE WebSocket Studio is intended for debugging, research and education: understanding real-time client-server architectures and studying a live WebSocket protocol Sending crafted messages to a live server can have effects you did not intend, up to and including consequences for your account. Use it deliberately and at your own risk ──────────────────────────────────────── LEGAL GGE WebSocket Studio is an independent project and is not affiliated with, endorsed by, or associated with Goodgame Studios. Goodgame Empire is a trademark of Goodgame Studios Users are responsible for ensuring that their use of this extension complies with applicable laws, the Chrome Web Store policies, and the Terms of Service of any third-party services they access