y3-lua-pipeline

Safe Y3 Lua development requires reading API safety rules and known Lua issues before coding, then enforcing mandatory script directory detection to ensure correct engine-loading paths. This eliminates high failure rates caused by misplaced scripts or unverified API calls during hot-reloads.

Y3 Lua UI interaction code fails during hot-reload when scripts are not placed in correct engine-loading paths or when APIs are used without verification. Enforcing strict script directory detection and checking y3-lualib references prevents these failures.

Correct Y3 Lua script routing requires executing a mandatory directory detection checklist to choose the proper code.lua path and module routing. This ensures event handling, unit effects, and buff logic load deterministically through the official y3-lualib framework.

Y3 Lua development constrains implementations to official y3-lualib APIs and prevents invented API calls for damage and death logic. You must verify API existence in y3 source or references before writing gameplay systems to ensure reliable execution.

Yes, y3-lualib provides a unified scope covering both gameplay systems including AI behaviors, timers, and save/load logic, alongside UI Lua interaction code. Both require the same API safety checks and script directory verification before implementation.

Known limitations when writing Y3 Lua skill effects and timers include encountering undocumented API behaviors and engine-loading path issues. Reading the project's known Lua issues and verifying API existence in references before coding mitigates these constraints.