What problem does it solve? When building NetEase Minecraft mods with the QuModLibs framework, developers often fall back to raw NotifyToServer/NotifyToClient calls, which breaks the project's communication conventions. This Skill enforces the correct QuMod event registration and dispatch patterns for all client-server RPC logic. ## Core Features & Use Cases - QuMod RPC API Reference: Covers server-side Call, MultiClientsCall, @AllowCall, @InjectRPCPlayerId and client-side Call, Request, @AllowCall. - Ready-to-use Code Templates: Provides patterns for server-to-client, client-to-server, and request-response (with callback) communication flows. - Convention Enforcement: Ensures JSON-serializable payloads, automatic playerId injection, and function-name-based routing while forbidding native ModAPI calls. - Use Case: When adding a new feature where the client requests data from the server, use this Skill to generate a @AllowCallStatic server endpoint and a matching client Request call with a response callback. ## Quick Start Generate a QuModLibs RPC endpoint that lets the client request player data from the server and handle the response callback.