> 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!

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Unreal C#</td><td><a href="/files/0XakOXpFaIrv1VrvOpQl">/files/0XakOXpFaIrv1VrvOpQl</a></td><td><a href="/pages/JVSOQY6CA1pWJZ98PBmV">/pages/JVSOQY6CA1pWJZ98PBmV</a></td></tr><tr><td>Unreal BP</td><td><a href="/files/Pdi27a67BoUnxWMFK6E2">/files/Pdi27a67BoUnxWMFK6E2</a></td><td><a href="/pages/bJYNR2zLGu8RKrjGk4wj">/pages/bJYNR2zLGu8RKrjGk4wj</a></td></tr></tbody></table>

***

#### 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kimscode.gitbook.io/unrealscripting/overall/unreal-scripting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
