What problem does it solve?
Adding a new auto-gathering route to MaaEnd requires coordinated edits across route JSON files, the AutoCollect pipeline entry, task registration, and five locale files, which is error-prone when done manually.
Core Features & Use Cases
- Route File Generation: Creates a new
AutoCollectRouteX.json following the Route6 single-segment pattern with MapLocateAssertLocation and MapNavigateAction nodes.
- Path Normalization: Converts user-supplied
[x, y, true] collection points into "COLLECT" or "DIG" action strings based on route type.
- Full Registration: Wires the route into
AutoCollect.json, assets/tasks/AutoCollect.json, and all five interface locale files.
- Use Case: A developer provides a task name like "路线6:四号谷地-轻红柱状菌", a teleport entry point, an assertion coordinate, and a path point list, and receives a complete route file plus all registration edits.
Quick Start
Ask the assistant to create a new AutoCollect route named "路线7:某区域-某资源" with teleport point SceneEnterWorldXxx, an assertion coordinate, the full path point list, and whether it is a click-collect or dig route.