go-service-guide

To register a Go service component in MaaFramework, apply the provided registration templates that enforce a clean separation between pipeline-driven logic and service orchestration. This guide ensures your registration complies with compile-time interface checks and naming conventions across agent/go-service sub-packages.

A correct MaaFramework Go service structure separates pipeline-driven logic from service orchestration across sub-packages and shared utilities. This guide provides the standard project directory structure, registration mechanisms, and compile-time interface check templates to maintain consistency and enable multi-package collaboration.

Implement CustomAction and CustomRecognition templates in Go by following the MaaFramework integration patterns provided in this guide. It ensures interface compatibility across shared utilities and enforces compile-time checks, along with specific 720p coordinate assumptions for your agent/go-service codebase.

Yes, the Go service guide requires 720p coordinate assumptions for interface compatibility. Following these coordinate assumptions alongside the provided templates for CustomAction, CustomRecognition, and EventSink ensures your agent/go-service components compile and operate correctly within MaaEnd.

Compile-time interface checks in a MaaFramework Go service are needed to verify interface compatibility across sub-packages and shared utilities before runtime. This guide applies compile-time interface checks alongside strict naming conventions to prevent integration errors between pipeline-driven logic and service orchestration.