orion-code-style

To enforce consistent C++ code formatting in Unreal Engine, apply project-specific style rules to newly created or modified .h and .cpp files. This includes validating Tab indentation, CRLF line endings, copyright headers, and generated header placement through a dedicated validation script.

C++ code style validation covers Unreal Engine .h and .cpp source files, as well as Build.cs and Target.cs configuration files. It checks include management, naming conventions, comments, dependency placement, and generated header ordering to ensure production-ready consistency.

To validate Build.cs and Target.cs coding conventions, run the project style validation script against these Unreal Engine configuration files. This verifies dependency placement, formatting consistency, and naming rules to keep your module definitions aligned with engineering standards.

Yes, Unreal Engine C++ formatting requires Tab indentation and CRLF line endings to maintain project consistency. The style validation script checks these specific line ending and indentation requirements across .h, .cpp, Build.cs, and Target.cs files.

You should run Unreal C++ style validation when adding a new gameplay module, refactoring existing systems, or reviewing code changes. This ensures all touched files remain aligned with project coding conventions and prevents style drift across the codebase.

Generated header ordering matters in Unreal C++ code style because it maintains include management consistency and prevents compilation issues. The validation script checks that generated headers are placed correctly according to Orion framework standards across modified source files.