Skip to content
The Technical ArtistArt. Code. Pipelines. Games.
Home/Unreal Engine/Blueprints 101
tutorial 04
unreal engine

Blueprints 101

Starterguide~2 min read

Blueprints from a TA angle: editor tools, artist-facing actors, construction scripts, and the point where you stop and ask for C++.

On this page What Blueprints Are Anatomy Of A Bp Construction Script Performance Discipline

4.1What Blueprints Are (And Aren't)

Blueprints are Unreal’s visual scripting system. They’re useful for gameplay classes, editor helpers, placement tools, and artist-facing controls. Blueprint execution has overhead, so profile frequently repeated logic and discuss a native implementation with an engineer if it becomes a bottleneck.

4.2Anatomy Of A Blueprint Actor

  • Components panel - the actor's parts: meshes, lights, collision shapes, particle systems, arranged in a hierarchy.
  • Event Graph - runtime logic driven by events: BeginPlay, Tick, overlaps, input. Execution flows along the white wire; data along the coloured ones.
  • Variables - typed, with the all-important Instance Editable flag that exposes them to level designers, and Expose on Spawn for spawn-time configuration.
  • Functions vs Macros vs Events - functions return values and keep graphs tidy; custom events are for latent/async flows.

4.3The Construction Script For Editor Tools

Placeholder with instructions to screenshot a spline fence construction script
Screenshot placeholder: a spline-fence Construction Script

The Construction Script runs in the editor whenever an instance is placed or edited. Useful examples include: a fence that scatters posts along a spline, a room that resizes trim meshes, a light fixture that syncs emissive colour to the light. Add Instance Editable variables and designers get sliders instead of hand-placing twenty meshes.

Construction script cost

Heavy construction scripts run while artists drag things around. That can make placement and editing noticeably slower. Cache expensive results, and for large placement jobs use PCG or editor-time Python.

4.4Performance Discipline From Day One

  • Turn Tick off by default. Most actors never need it. Event-driven logic (overlaps, timers, delegates) beats polling every frame.
  • If the logic needs regular updates but not every frame, increase the Tick Interval and test the response. For example, 0.1 seconds aims for roughly ten updates per second, subject to frame timing. See Epic’s actor ticking guide.
  • Avoid Get All Actors of Class in Tick - cache references once at BeginPlay.
  • Casting to heavy BP classes creates load-time reference chains - prefer interfaces or component checks. A BP_Prop that casts to BP_GameMode drags the entire game mode (and everything it references) into memory with it.

There's more detail in Performance -> CPU, Blueprints & Ticks.

<- Previous
Materials 101