# Continue.dev Ruleset for MountainLabs UE5 Development

## Build & Development Commands
- Always **verify** Unreal Engine macros (UCLASS, USTRUCT, UPROPERTY, UFUNCTION) before finalizing code.
- Test that all **BlueprintCallable** and **BlueprintReadWrite** functions are **Blueprint-safe**.
- Before sending a file, validate against latest **knowledgebase** and check if additional **Unreal Engine modules** are required.
- For any missing Build.cs modules, report clearly:  
  > "This file requires the following modules which are not present in your current Build.cs: [...]".
- Always **provide**: 
  - Full **filepath**
  - Full **filename**
  - Full **file content** (production-ready, copy-pasteable).

- NEVER SEND JUST SNIPPETS REFERENCING EXISTING CODE IN COMMENTS, ALWAYS SEND COPY PASTE CODE TO REPLACE EXISTING
## Testing Guidelines
- Test all code before delivering to ensure it works inside Unreal Engine 5 without warnings or errors.
- For Blueprint-exposed functions, verify execution through the Blueprint editor.
- For iteration sessions, after each step, revalidate that the file still compiles and is functional.
- If feature-specific modules (NavigationSystem, OnlineSubsystem, etc.) are used, confirm runtime support.
- Switch to **file download** if text exceeds practical size limits.

## Code Style & Guidelines 
- All files must start with the header:  
  ```cpp
  // Copyright Seven-Mountains-Labs, Tim Koepsel - 2024 All Rights Reserved.
  ```
- Code must strictly follow **Unreal Engine C++** standards:
  - PascalCase for class names, function names.
  - camelCase for variables.
  - UPROPERTY and UFUNCTION macros placed immediately before declarations.
  - Correct Blueprint exposure (`BlueprintCallable`, `BlueprintReadWrite`) where appropriate.
- No explanations, comments, or partial code unless explicitly requested.
- No assumptions, retries, or irrelevant code — prioritize **precise, directly usable solutions**.
- Maintain **strict technical and professional tone**; avoid theatrical or stylistic language.

## Documentation Guidelines 
- Only document code if explicitly requested by the user.
- When documenting (upon request), document:
  - Class descriptions (above UCLASS).
  - Function purpose (above UFUNCTION).
  - Important parameters in function declarations.
- Documentation must be **clear**, **technical**, and **aligned to Unreal Engine documentation standards**.
- Always link any **roadmap** or **external references** (e.g., RTSFramework Roadmap) when feature work is based on them:
  > [RTSFramework Roadmap](https://wiki.seven-mountains.eu/en/mountainlabs/rts-framework/roadmap)