y3-lua-review

To check Y3 Lua scripts for API hallucination and event mismatches, run a four-phase review that validates syntax, module paths, API calls, and event parameters against the project's reference source. This process eliminates runtime crashes by catching errors before integration.

API hallucination in Lua game development occurs when scripts call non-existent or incorrectly parameterized APIs. It causes runtime crashes because invalid function calls and event parameter mismatches fail during execution, which can be prevented by validating code against a curated API issues database.

Yes, you can automatically fix incorrect Lua API calls and event names in Y3 maps. The review process applies deterministic 1:1 replacements for clearly defined wrong patterns, such as specific API substitutions and event parameter corrections, but requires your explicit confirmation before applying changes.

To review a specific directory of Lua business scripts instead of the full Y3 project, use review scope control to specify target directory or file subsets. This produces a structured CRITICAL, WARNING, and INFO report focused only on your selected files.

Yes, the Y3 Lua code review supports include and require path consistency checks. During the basic syntax and module verification phase, it validates include and require conventions to ensure module path consistency across the reviewed business scripts.

The limitation of auto-fixing Lua event parameter mismatches is that only deterministic 1:1 replacements for clearly defined wrong patterns can be applied automatically. Non-deterministic cases cannot be auto-fixed and are instead output as suggestions for manual review.