credit-shopping-log-analysis

Analyzes MaaEnd CreditShoppingMain logs to reconstruct purchases, discounts, refreshes, and credit spending.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When the MaaEnd credit shopping automation behaves unexpectedly, users cannot tell what was actually bought, at what discount, whether refreshes fired, or how many credits were spent. This Skill turns raw MaaFramework logs into a verifiable reconstruction of the CreditShoppingMain task run.

Core Features & Use Cases

  • Purchase Reconstruction: Confirms actual purchases via CreditShoppingBuyConfirm and claim-success nodes, mapping internal item names to Chinese product names.
  • Shelf Snapshot Recovery: Rebuilds slot-level shop shelves anchored on CreditIcon TemplateMatcher results, including ADB half-shelf merging and post-purchase 9-slot states, without inventing item names.
  • Refresh & Discount Analysis: Distinguishes daily refresh quota exhaustion from prudent refresh triggers, and derives per-item discounts by comparing IsDiscountPriority2 OCR scans.
  • Use Case: A user asks "why didn't prudent refresh trigger and what did credit shopping buy?" The Skill locks the task_id, reads the frontend pipelineOverride config, and produces a timeline showing the feature was disabled plus the exact items purchased.

Quick Start

Analyze my MaaEnd logs and tell me what the credit shopping task bought, what discounts applied, and whether any refresh was triggered.

Frequently Asked Questions about credit-shopping-log-analysis

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

FAQPage Schema
How do I find out what the MaaEnd credit shopping task actually bought?

Search maafw.log for CreditShoppingBuyConfirm Action.Succeeded entries within the task_id, then confirm a CreditShoppingClaimConfirm or purchase-success recognition closed the reward screen. Item names come from shelf OCR text or A3 acquisition messages, never from guesswork.

How to tell if prudent refresh triggered in CreditShoppingMain logs?

Prudent refresh only counts as triggered when a Node.Recognition.Starting entry for CreditShoppingPrudentRefresh appears in the log. Presence in parse_node or NextList does not count, and an enabled:false flag in the mxu-web pipelineOverride means it was deliberately disabled.

Why does the log show CreditShoppingRefreshCountReached but no refresh happened?

CreditShoppingRefreshCountReached means the in-game daily free refresh quota is exhausted, not that MAA refreshed the shop. The click after this node continues scanning remaining items and does not count as a successful shop refresh.

Can shelf contents be reconstructed without item name OCR in the logs?

Yes. Shelf slots are anchored on CreditIcon TemplateMatcher results, which define slot count and column order independently of BuyFirstOCR or Priority2OCR. When name OCR is absent, the analysis reports slot-only shelves and explicitly marks items as unidentified.

Does this log analysis workflow apply to other MaaEnd tasks?

No. The procedure is scoped strictly to CreditShoppingMain and must not be reused for AutoStockStapleMain, AutoStockpileMain, or general issue troubleshooting, since node names and evidence sources differ per task.