Games

I am a beginner in this engine on purpose. Years of 3D modeling taught me meshes, UVs, and materials. They did not teach me a playable loop. Unreal Engine 5.8 is where I am learning that: a character you can move, a clock on screen, a start line, a packaged build you can unzip on Windows and actually run.

The editor is the workbench. A map is a level. Play In Editor runs the game inside that map without leaving the desk. Package Project is the step that turns the same map into FGIU.exe — the file on this page. Same mannequin, same timer, no editor around it.

First Game in Unreal started from Epic’s third-person template in 5.8. Graybox on purpose: prototype floor, lime and orange platforms, a painted start line. The camera sits behind the mannequin. Input is Enhanced Input — actions, not raw keys glued to the pawn. The HUD is a widget. The loop is short: spawn, run, watch the clock. Art later. Play first.

5.8 is not a different Unreal. It is the current one: World Partition for large maps, Nanite and Lumen when I need them, PCG when the world has to grow from rules. None of that is the first homework. The first homework is a body that walks and a timer that ticks. The download below is that homework, packaged.

Engine

Unreal Engine 5.8

Logic

Blueprints

Template

Third Person

Build

Windows Win64

A Blueprint is a class with a graph instead of a source file. Open it and you get an Event Graph: events on the left, work to the right. White pins are execution — the order things run. Colored pins are data — Boolean, Integer, Float, Object, the type of the wire. If the types do not match, the wire refuses. That is the type system, drawn.

The events that matter first are few. Event BeginPlay fires once when the actor exists. Event Tick fires every frame. Event ActorBeginOverlap fires when something enters a collision. A timer is often just an Integer set on begin play, then read by the HUD. Compile has to succeed before any of that runs. Red errors in the graph are the same as a failed build.

There is a Level Blueprint on the map, and there are Blueprint Classes in the Content Browser. The class is the reusable one: a pawn, a lamp, a collectible, a widget. The level graph is for things that only exist in this map. First Game in Unreal keeps the loop on classes — input on the character, time on a widget — so packaging the project packages the logic with it.

Visual scripting is still scripting. Execution flows. Data is typed. A broken wire is a bug. The difference is you can see the flow on one screen: BeginPlay sets the timer, Tick updates the widget, overlap ends the run. That is why I am learning games this way in 5.8 before I write the same loop in C++. The graph is the lesson. The Windows build is the proof it ran.