create-analyzer

The create-analyzer skill provides a robust framework for developers working with mineflayer-bedrock to build custom domain-specific packet analyzers. By streamlining the creation of new analysis modules, it enables researchers and automation engineers to decode complex interactions such as inventory management, player movement, entity synchronization, and crafting sequences. This tool is designed for developers who need to bridge the gap between raw binary packet logs and actionable state representation.

The skill functions as a generator that creates modular typescript classes extending a centralized BaseAnalyzer. It enforces a strict workflow that begins with packet identification via protocol definitions, moves through structural code generation, and concludes with practical validation using captured logs. By standardizing the analyzer lifecycle, it ensures that telemetry data extracted from Bedrock servers remains consistent, debuggable, and extensible for future protocol updates or new game features.

• Automatically generates TypeScript boilerplate for packet analysis using domain-specific templates.

• Provides deep integration with project-standard protocols defined in protocol.d.ts.

• Includes pre-built logic for common domains: Inventory, Movement, Entities, Chat, Blocks, and Combat.

• Supports the full development lifecycle from raw .bin capture and .jsonl filtering to output validation with jq.

• Facilitates the use of Replay Clients to simulate network traffic for unit testing analyzers.

• Users should start by identifying the specific packet domain and performing packet captures using the integrated recorder before writing logic.

• The tool encourages a 'log-everything-first' approach within the shouldLog override to ensure no critical edge-case data is dropped during initial debugging.

• Required inputs include the desired domain name and the relevant packets to monitor, while outputs include structured TypeScript files and JSONL telemetry logs.

• Always consult the provided documentation mapping to find existing plugins in packages/mineflayer/lib/bedrockPlugins/ to understand current handler implementations.

• Constraints include manual registration in the main index.ts file and the need for a working Minecraft Bedrock environment to generate authentic packet samples.