RPG NW.js Validator

Purpose & User Intent: This tool analyzes RPG Maker projects that run on NW.js runtimes to determine compatibility and readiness for export. Target users include solo developers, small studios, and tool builders who upgrade NW.js versions, migrate between RPG Maker MV and MZ, or prepare cross‑platform builds. It helps decide whether a project is ready for a given NW.js version and flags where updates are required. Core Logic & Features: The tool applies a domain‑specific compatibility matrix between RPG Maker engine versions and NW.js runtimes. Required features include automatic RPG Maker version detection (MV or MZ), NW.js version validation, and generation of a structured report with actionable recommendations. Optional/advanced features include asset usage insights, memory/flag tuning guidance, and a patch fragment suitable for manual integration. Outputs are non-destructive and do not modify source code unless explicitly exported by the user. Inputs & Outputs: Inputs consist of project_path (string), rm_version (string: MV or MZ), nwjs_version (string), and target_platforms (array). Outputs include a compatibility_score (0–100), issues (list of items with severity), recommended_changes (list of configuration hints), and a summary description suitable for release notes. The tool can also emit a JSON fragment compatible with a project’s build config. Algorithms & Calculations: The core method uses a version matrix to map MV to NW.js ranges and MZ to its supported runtime windows. It detects deprecated API usage, checks for engine-specific WebGL and Node API differences, and computes a percentile score reflecting conformity to the matrix. It generates recommended flags and a minimal patch snippet for common adjustments. Edge handling relies on input validation and deterministic defaults when external data is unavailable. Industry/Region & Localization: Assumes RPG Maker’s global deployment with EN as default locale; exports typically target Windows/macOS; respects standard file paths and common build script conventions; currency and units are not changed by the tool. Assumptions & Exclusions: Assumes local filesystem access to the project and that the user governs changes; it does not perform runtime tests, license checks, or automatic code edits; UI behavior and front-end presentation are out of scope.