Coming to Unity from Unreal Engine

A translation layer for Unreal developers: the Unity name for what you already know, the workflow that replaces it, and the C# that does what your Blueprints did.

4 chapters About 65 minutes in all Free, no signup

ProgressSaved in this browser

0 of 4 chapters read

Start with chapter 1

What this guide translates

This guide is for Unreal Engine developers who already understand actors, components, Blueprints, levels, collision and gameplay scripting, but need the Unity names, workflows and C# patterns that map to those habits. It is not an engine-war article; it is a practical translation layer for building faster in Unity.

Start with concepts

The first chapters map Unreal terms to Unity terms: Actors to GameObjects, Components to MonoBehaviours, Levels to Scenes, and Blueprint graphs to C# scripts.

Then connect real scripts

Pair the guide with the script library, the kits and the free Unity C# scripts guide to turn the notes into working project code.

All 4 chapters, in order

  1. Concepts & Naming What Unreal calls X, Unity calls Y 12 min beginner
  2. Scenes & Level Structure From UE Levels to Unity Scenes 15 min beginner
  3. Scripting: Blueprint vs C# From visual nodes to clean C# code 20 min intermediate
  4. Physics & Collision Rigidbodies, colliders, and raycasting 18 min intermediate