autocollect-add-route

Creates and registers single-segment AutoCollect gathering routes in MaaEnd pipeline JSON files.

3.7k|317|Updated Mar 18, 2022
One-click install
npx skills add https://github.com/MaaEnd/MaaEnd --skill autocollect-add-route
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autocollect-add-route
Source: https://github.com/MaaEnd/MaaEnd/tree/main/.agents/skills/autocollect-add-route
Command: npx skills add https://github.com/MaaEnd/MaaEnd --skill autocollect-add-route

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about autocollect-add-route

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new AutoCollect route in MaaEnd?

Provide a task name in the format "路线X:区域-资源", the first teleport point, an assertion coordinate, the full path point list, and the collection type. The route file is generated following the Route6 single-segment pattern and registered automatically.

How to register an existing AutoCollectRoute JSON file into the task list?

Only the task name is needed. The route is wired into AutoCollect.json as a Sub node, added as a case in assets/tasks/AutoCollect.json, and given label keys in all five locale files without asking for path or teleport details.

What route structures does this AutoCollect workflow support?

It only supports single-segment Route6-style routes using MapLocateAssertLocation plus one MapNavigateAction Goto node. Multi-segment GotoFind1/2/3 structures with anchor chains are explicitly out of scope.

How are collection points marked in the route path?

Collection points use action strings instead of booleans: "COLLECT" for click-gathering routes and "DIG" for mining routes. User input like [x, y, true] is normalized to these strings before being written into the final path array.

When should this skill not be used for MaaEnd routes?

It does not apply to EnvironmentMonitoring, AutoEssence, or AutoEcoFarm routes, Go Service algorithm extensions, or any multi-segment GotoFindN route structure. Those require different workflows outside this skill's scope.