How maxbittker/rs-sdk works
RS-SDK combines a TypeScript bot-control SDK and MCP agent interface with a browser or headless game client and a RuneScape-style server emulator. The main workflow is an agent executing bot code: the MCP manager connects the SDK, the SDK sends actions through the gateway and client, and the emulator processes game traffic and updates the world. The README documents this topology; sampled source confirms the manager, SDK, headless client, engine startup, and market-search handler. Some gateway and bot-bridge implementations are not present in the supplied tree, so their internal wiring is not expanded.
Main entry points: sdk/index.ts Bot SDK · server.ts MCP tools · app.ts Engine runtime · api/index.ts Connection manager
Components 17
Agent interfaces
- MCP tools
mcp/server.ts - Connection manager
mcp/api/index.ts - Bot scripts
bots/_template/script.ts
Bot control
- Bot SDK
sdk/index.ts - Action API
sdk/actions.ts
Game client
- Web client
server/webclient/src/client/ClientBuild.ts - Headless client
server/webclient/src/lite/LiteClient.ts
Game emulator
- Game world
server/engine/src/engine/World.ts - Engine runtime
server/engine/src/app.ts - Client handlers
server/engine/src/network/game/client/handler/MarketSearchHandler.ts - Pathfinding
server/engine/src/engine/routefinder/index.ts - Database layer
server/engine/src/db/query.ts
Market
- Market SDK
sdk/market.ts - Grand Exchange
server/engine/src/engine/market/GrandExchange.ts - Market store
server/engine/src/engine/market/MarketStore.ts
Other components
- Bot agent
- Gateway
Connections 17
- Bot agent → MCP tools: requests tools
- MCP tools → Connection manager: manages connections
- MCP tools → Bot SDK: executes code with
- Bot agent → Bot scripts: starts bot
- Bot scripts → Bot SDK: runs with
- Connection manager → Bot SDK: connects
- Bot SDK → Gateway: sends actions
- Gateway → Web client: forwards messages
- Web client → Gateway: relays game state
- Gateway → Bot SDK: forwards state
- Bot SDK → Action API: exposes actions
- Headless client → Game world: exchanges game traffic
- Engine runtime → Game world: starts world
- Engine runtime → Database layer: initializes runtime
- Client handlers → Grand Exchange: dispatches search
- Bot SDK → Market SDK: reads market data
- Grand Exchange → Market store: uses market state