> For the complete documentation index, see [llms.txt](https://kimscode.gitbook.io/unrealscripting/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kimscode.gitbook.io/unrealscripting/overall/unreal-scripting.md).
# Unreal Scripting
**UnrealScripting** is a focused, production-grade guide to building Unreal Engine projects using **C# as the primary language**, with **Blueprints as a first-class companion**.
No demos.\
No toy examples.\
No half-explained engine concepts.
Just **clear rules**, **real patterns**, and **usable knowledge**.
***
### Why UnrealScripting Exists
Unreal Engine documentation is scattered, inconsistent, and often unclear — especially if you want to write **real gameplay code** without drowning in C++.
UnrealScripting fixes that by:
* Treating **C# as a serious Unreal language**
* Using **Blueprints where they make sense**
* Explaining **what Unreal assets actually do**
* Showing **how systems fit together**, not just how they compile
***
### The Philosophy
#### C# — Gameplay & Systems
* Core game logic
* Runtime systems
* Tools & utilities
* Non-game Unreal applications
> If you’re coming from Other Engines like Unity, Godot, and other C# Game Engines, this is your home.
***
#### Blueprints — Data & Orchestration
* Designer-friendly logic
* Fast iteration
* Asset configuration
* Visual control flow
> Blueprints are powerful when used **intentionally**, not everywhere.
***
### What You’ll Find Here
* **Complete UAsset explanations**\
What they are, when to use them, and how to reference them safely.
* **Unity-style documentation**\
Consistent structure. Searchable. Deep — not shallow.
* **Hybrid C# / BP architecture**\
Clean boundaries, real patterns, scalable projects.
* **Math, engine data types, and fundamentals**\
Explained the way Unreal actually works.
* **Templates & reference projects**\
Built for reuse, not screenshots.
***
### Who This Is For
UnrealScripting is for developers who:
* Want **C# in Unreal**, done properly
* Use Blueprints but hate spaghetti
* Care about structure, not hacks
* Want to **build**, not fight the engine
If you want hype or beginner hand-holding — this isn’t it.
***
### Start here!
***
#### Unreal isn’t hard.
#### It’s just badly explained.
**UnrealScripting fixes that.**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://kimscode.gitbook.io/unrealscripting/overall/unreal-scripting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
