Make and Break

How UOrreryTerrainBake::BakeAuthoring bakes.

What a bake did, or why it refused.

The brush tool's state, for a HUD and for tests (Tier 3 value, no object references).

The answer to a construction call.

A linear earthwork (road, rail, canal bank) as Blueprint states it, in cm.

What an earthwork does to the ground, in Unreal units: the preview and the committed numbers.

What PlacePlate or PlaceCorridor did.

What NewTerrain did.

One brush stroke as a script states it: the tool, its settings as the tool's details panel shows them, and the cursor's path over the ground.

What ApplyEditorStroke did.

The feature a client's Replace or Remove request names, as the server knows it.

What the stack knows about one feature.

What the follow subsystem is tracking and has queued.

Where a tile store's ground sits on the earth: metadata only, never read by the terrain.

One ground answer in Unreal units.

What an importer's scripting entry returns.

Where along a corridor a keep-out run lies, and whether its ends get a tunnel opening.

One paint layer: what the player calls it and which slice of the material's layer textures it draws.

One grass entry of a paint layer: which ULandscapeGrassType grows where.

One paint layer at a point and its weight: an entry of FOrreryTerrainGroundSample::Paint.

A brush mask a client offers to upload, as CanAddBrushMask sees it: the mask's size from the offer, and what this player has uploaded so far.

The client's acknowledgement (ServerAck, unreliable, 4 Hz): a lost one is replaced by the next.

The client's first message (ServerHello): what both sides must share before anything else travels.

The outcome of one request, sent to its client only (ClientRequestResults).

The network settings (Project Settings, Orrery Terrain, Network): built-in replication, request rules, pacing and checkpoints.

What the net hub has done so far, for a debug overlay and for tests.

The server's answer to an accepted Hello (ClientWelcome): the client's author id and its join.

Which attributes the points carry (the Z, rotation and density are always written).

How a terrain surface data samples.

One record of the authority's ordered stream: what a game with its own transport relays from OnTerrainRecordBP on the authority to ApplyTerrainRecord on every replica, in Seq order.

How a terrain renders: tier, LOD, far field and shadow invalidation (Tier 3 authoring data).

Runtime settings of one terrain, edited on AOrreryTerrainActor.

What the terrain's colour runtime virtual texture is doing (UOrreryTerrainSubsystem::GetRvtStatus).

What a terrain save keeps (editor authoring layer).

The authority's sculpt rules, edited with the terrain's runtime settings (Tier 3 config).

The sculpt tool's state, for a HUD and for tests (Tier 3 value, no object references).

What one finished stroke moved, in cubic metres, for a costed game (a sculpt beneath a feature is a sculpt cost, never re-charged to construction).

One line of the stat terrain panel.

What a tile store was built from, so an importer can tell whether the host changed since (see IsImportCurrent).

One brush application, in Unreal units, for Blueprint and game input.

A brush mask named by its content hash: the 64-bit hash of its canonical bytes, which is what a sculpt record carries.

What a terrain's registry says about one mask.

The ground changed under Bounds.

An area earthwork as Blueprint states it: a building pad, yard or apron.

A terrain save beside a game's save slot, as the game keeps it in its own USaveGame: the file the terrain wrote and the hashes that pair it with this game save.

What saving the terrain to a slot did.

A splat brush as a terrain holds it: up to four channels, each a paint layer and a registered mask, in the fixed order red, green, blue, alpha.

One channel of a registered splat: a paint layer and the mask that weights it.

How UOrreryTerrainBake::BakeAuthoring bakes.

A linear earthwork (road, rail, canal bank) as Blueprint states it, in cm.

One brush stroke as a script states it: the tool, its settings as the tool's details panel shows them, and the cursor's path over the ground.

Where along a corridor a keep-out run lies, and whether its ends get a tunnel opening.

Which attributes the points carry (the Z, rotation and density are always written).

How a terrain surface data samples.

One record of the authority's ordered stream: what a game with its own transport relays from OnTerrainRecordBP on the authority to ApplyTerrainRecord on every replica, in Seq order.

What a terrain save keeps (editor authoring layer).

One brush application, in Unreal units, for Blueprint and game input.

A brush mask named by its content hash: the 64-bit hash of its canonical bytes, which is what a sculpt record carries.

An area earthwork as Blueprint states it: a building pad, yard or apron.

A terrain save beside a game's save slot, as the game keeps it in its own USaveGame: the file the terrain wrote and the hashes that pair it with this game save.

A splat brush as a terrain holds it: up to four channels, each a paint layer and a registered mask, in the fixed order red, green, blue, alpha.

One channel of a registered splat: a paint layer and the mask that weights it.