HammeriteNavigationBakeReport

Navigation. Inherits RefCounted

What one navigation bake did, and what it could not do.

The editor and the running game bake by the same route (HammeriteNavigationRuntime.build()), so they had better say the same things about it. A report is that single voice: the tool prints it into its status panel and the message log, and a shipped build prints it to the console when asked. Most of it is counts. The part that earns its keep is what was LEFT OUT - ground that fits no agent profile, a link nothing can take, a prop nobody marked - because every one of those looks from the outside exactly like something the builder failed to find.

Properties

Methods

Property descriptions

patches

var patches: int = 0

Patches of walkable ground measured.

patches_unfit

var patches_unfit: int = 0

Of those, how many no agent profile could stand on, and which are therefore not in the bake.

regions

var regions: int = 0

Navigation regions attached, and polygons across them. More regions than rooms means some room takes different agents in different parts of it - a crawlspace, a low gallery.

polygons

var polygons: int = 0

Navigation polygons across all regions.

links

var links: int = 0

Traversal links found, and the NavigationLink3Ds emitted for them. More nodes than links means agents disagree about direction; fewer means some link is beyond every profile in the game.

link_nodes

var link_nodes: int = 0

NavigationLink3D nodes emitted for the links.

has_profiles

var has_profiles: bool = false

Whether the bake was made against a real agent-profile table or the stand-in.

warnings

var warnings: String[] = []

Everything the builders could not do, in the words they said it in.

Method descriptions

summary()

func summary() -> String

The bake in one or two lines, for a status panel or a log. Leaves out warnings.