RPG Maker JS Analyzer

Purpose & User Intent: The RPG Maker JS Analyzer targets game developers using RPG Maker MV/MZ who work with JavaScript; it solves cross-version compatibility, plugin integration, and code quality assessment. Primary users are indie developers, plugin authors, and studios migrating projects between MV and MZ. Use cases include migration audits, plugin compatibility checks, and scaffolding of new plugins. Core value lies in early issue detection, standardized plugin templates, and reductions in debugging cycles.
Core Logic & Features: The tool performs static analysis of JavaScript sources and project manifests to identify deprecated APIs, changes between MV and MZ, and conflicts with third-party plugins. Required features include an AST-based parser, a delta mapping between engine versions, a quantitative compatibility_score, and a scaffold/template generator for plugins. Optional/advanced features include a sandboxed evaluation environment, exportable reports, code transformation recommendations, and ready-to-use template code tailored to MV/MZ conventions.
Inputs & Outputs: Inputs include project_version (string), target_version (string), source_code (string or file payload), plugin_list (array of strings), and analysis_mode (enum: compatibility, scaffolding, metrics). Outputs include a structured compatibility_report (JSON), issues (array with fields: id, severity, description, location), generated_scaffold (code snippet), and summary_score (0–100). Validation ensures version values are MV or MZ and source_code is non-empty; external delta data absence falls back to known diffs.
Algorithms & Calculations: An AST parser analyzes syntax trees to detect API usage and API-compatibility edges. A delta_table maps MV-to-MZ changes for core APIs and plugin hooks. compatibility_score = max(0, 100 - sum(issue.weight for issue in issues)); each issue carries severity weights. Scaffold generation uses a templating engine with proper header metadata and plugin entry points. Outputs are reproducible given the same inputs.
Error & Edge Cases: Missing inputs trigger schema errors; unknown versions use a best-effort default delta. If change logs are unavailable, the tool relies on internal heuristics and cached diffs. Large projects may incur longer analysis times; timeouts are surfaced as non-fatal warnings with partial results. Circular plugin dependencies are flagged.
Industry/Region & Localization: Aligns with RPG Maker MV/MZ conventions, plugin headers, and locale-agnostic identifiers. Supports ECMAScript features present in MV/MZ; localization considerations are deferred to user-provided sources.
Assumptions & Exclusions: Assumes inputs are JavaScript sources used within RPG Maker projects; does not perform runtime instrumentation or full project migration automation; excludes non-JS assets and UI/UX concerns.