OpenMW Lua gets dramatically easier when the editor knows the engine surface and the engineer knows how to verify it.
Cod3x tooling is deliberately part of the field manual rather than a separate download with no methodology attached.
Use Testing OpenMW Lua to choose the right layer for pure logic, context/tooling checks, in-game integration, and performance harnesses.
Use Source-Diving Workflow to establish facts, Coding Agents for the short operational contract, and So You Want To Code With AI? for the larger discipline: give the machine a map, sources, constraints, and a proof burden.
Cod3x and LuaLS
Context-aware annotations turn engine contracts into editor feedback.
So You Want To Code With AI?
AI raises your leverage, which raises your responsibility for the code you ship.
Coding Agents
Cod3x should make machine-assisted OpenMW Lua less plausible-looking and more correct.
Source-Diving Workflow
When documentation stops, inspect annotations, OpenMW source, production use, and history in that order.
Testing OpenMW Lua
Separate pure logic tests, engine-contract checks, in-game integration tests, and performance harnesses.