What problem does it solve?
Adding a new Arknights SideStory event to MAA requires coordinated edits across multiple JSON files (stage navigation tasks, StageActivityV2 activity config, and the MaaRelease mirror repository), each with its own ordering, OCR, and versioning rules that are easy to get wrong.
Core Features & Use Cases
- Guided information collection: Enforces a checklist of 11 required inputs (event prefix, stage numbers, drop items, OCR text, roi coordinates, timings) before any file is modified.
- Multi-file coordinated editing: Generates the tasks navigation file, updates local StageActivityV2 cache, and optionally syncs the MaaRelease remote source with correct ordering rules (stages ascending in tasks, descending in StageActivityV2).
- OCR vs template matching handling: Applies OCR text splitting rules for long event names, or manages template-image workflows including MinimumRequired version bumps.
- Use Case: When a new SideStory event launches, provide the event prefix, stage list, and drop materials, and the Skill produces all required JSON edits plus MaaRelease synchronization steps.
Quick Start
Add navigation for the new SideStory event with prefix TO, stages 7-9 plus a stage 4 rock-farming stage, and update StageActivityV2 and MaaRelease accordingly.