Think of Unreal as a real-time 3D editor + runtime. You build a world in the editor, then you “press play” and it becomes interactive.

• Level = the “map” you’re in.
• Actor = a thing in the world (door, enemy, light).
• Component = a part of an actor (mesh, collision, camera).
• Blueprint = logic without code (nodes = actions).
• Material = how a surface looks (color/roughness/normal).

You are my Unreal Engine teacher. Explain like I’m new, but don’t waste time.

Teach me Unreal Engine in this structure:
1) What it is (2 sentences).
2) The 6 core concepts I must know (Level, Actor, Component, Blueprint, Material, UI).
3) A 30-minute beginner plan (exact clicks/tasks).
4) A debugging checklist when things “don’t work”.
5) Ask me 2 questions to tailor what I learn next (game vs film vs archviz).

This player always loads the newest upload from the channel’s uploads playlist.

1. Goal: what is the clip trying to prove?
2. System: what Unreal tools make it happen?
3. Loop: how does it become gameplay (repeatable)?
4. Debug: what would break first?

You are my Unreal mentor. I’m watching a clip and want to recreate it.

Clip summary: [1 sentence]
What I’m trying to build: [1 sentence]

Deliver:
1) What the viewer sees (1 paragraph).
2) The Unreal systems involved (Blueprints / Materials / Landscape / UI / etc).
3) Exact build checklist (editor steps).
4) Debug checklist (what to check when it fails).
5) Ask 2 questions to tailor it to my project.

Aztec Adventure is an Unreal Engine 5 Blueprint-driven game: exploration, coin collecting, jumping, combat, and temple environments.

You are my Unreal Engine mentor. Teach like I’m smart but new. Keep it practical.

Project: “Aztec Adventure” (UE5, Blueprints-first).
Clip topic: exploration + coins + combat in a temple + landscape.

Answer in order:
1) What the player FEELS (1 sentence).
2) Mental model of the system (no jargon).
3) Build checklist (exact editor steps + components + key nodes).
4) Debug checklist (what to check when it doesn’t work).
5) Ask me 3 questions to tailor the next step.

Landscape + 3 textures (Grass / Dirt / Sand)

1) Create landscape
- Modes → Landscape → Create (use sensible default sizes)
- Enable Edit Layers if you want non-destructive sculpt/paint

2) Material (3 layers)
- Make a Landscape material using LandscapeLayerBlend
- Create LayerInfo assets (Grass, Dirt, Sand)
- Paint weights in Landscape mode

3) Stop obvious tiling
- Add Macro Variation (large scale noise/macro texture)
- Add Detail Normal (small scale)
- Use slope/height logic or paint pockets where buildup makes sense

You are my Unreal material teacher. Make it easy and visual.

I have tiling ground textures (BaseColor + Normal + Roughness).
Problem: tiling is obvious at distance.

Give:
1) Why tiling shows (1 paragraph).
2) Best 3 anti-tiling methods for landscapes (ranked).
3) A node plan for each (nodes + connections).
4) Tuning ranges (UV scales, noise strength).
5) Ask me 2 questions about style + platform.

• Experiences = which rules/content are loaded
• Game Features = modular plugins that can be enabled/disabled
• GAS = abilities (dash, shoot, reload) with clean rules
• CommonUI = layered UI with clean input routing

• UMG HUD first (health/ammo/coins)
• Then menus (pause/settings)
• Then CommonUI for layered navigation

You are my Unreal UI coach. Keep it simple, practical, and structured.

Goal: HUD (coins + health) + pause menu with clean input.

Answer format:
1) Where data should live (Character vs PlayerState vs GameState) in plain English
2) Widget tree layout (what widgets, where)
3) Data flow (what updates what)
4) Common bugs + fixes (bindings, focus, input mode)
5) Ask me 2 questions to continue

You are my Unreal AI tutor. Explain like I’m new, then give exact steps.

I want an NPC that:
Patrols → Detects player → Chases → Attacks → Loses sight → Searches → Returns.

Deliver:
1) Simple mental model (BT + BB + Perception connection)
2) Asset checklist (what to create)
3) Step-by-step build instructions
4) Debug checklist (what to check when it “just waits”)
5) Ask me 3 questions to tailor it

1. Goal (player experience)
2. Context (template/Lyra, BP/C++)
3. Constraints (platform/perf)
4. Evidence (screenshot/log + what you tried)

You are my Unreal Engine debugger. Be decisive and test-driven.

Rules:
- Give the top 5 likely causes (ranked).
- For each cause: a 30-second test to confirm.
- Then exact fix steps.

Context:
UE version:
Template/Lyra:
Blueprints or C++:
Expected:
Actual:
What changed:

Evidence:
- Logs (paste)
- Screenshot description
- What I tried

End by asking me 2 questions to narrow it down.

• Ask for a checklist, not a lecture
• Ask for common mistakes + debug steps
• Ask it to end with questions (keeps momentum)