write-angelscript

What problem does it solve?

Helps developers reliably write and modify AngelScript (.as) files by enforcing project conventions, guiding API lookup, and promoting a save-for-hot-reload validation workflow so changes can be tested immediately without unnecessary C++ compilation or guessing signatures.

Core Features & Use Cases

• Local API discovery: Instructs authors to consult the Kit's content/reference/AS_API and Docs-UE-Angelscript before coding.
• Safe fallback for missing signatures: Directs use of angelscript-api-query to verify or fetch API signatures and persist them back to local reference docs.
• Hot-reload and testing workflow: Emphasizes saving .as files to trigger immediate reload, provides debugging and print-key guidelines, and links to TDD via angelscript-tdd-agent-iteration for automated tests.
• Common pitfalls & conventions: Notes project-level gotchas (no #include, use value types for engine objects, FName keyed prints) and file placement/namespace expectations for Script/ files.

Quick Start

Open the Kit's content/reference/AS_API and Script-Examples to confirm signatures (use angelscript-api-query if missing), then write or edit the target .as file under Script/ and save to validate changes via hot-reload.