EndScreen Whole (Flowgraph Node)

Overview

Node Name: EndScreen Whole
Category: singleActive
File: extensions/flowgraph/nodes/ui/updatedUI/endScreenWhole.lua

All-in-one end screen node that builds the complete end screen (header, results, objectives, ratings, buttons) in a single node. Alternative to the modular EndScreen Begin + content nodes + Screen Finish approach.

Note: Showing two of these at the same time will break everything.

Pin Schema

Input Pins

Pin	Type	Description
`flow`	flow	Activates the end screen
`reset`	flow (impulse)	Resets the node
`text`	string/table	Results subtext
`failed`	bool	Whether the player failed (hidden)
`change`	table	Attempt change data
`progressKey`	string	Key for the attempt
`customBtnsFirst`	bool	Custom buttons before defaults (hidden)

Output Pins

Pin	Type	Description
`flow`	flow	Standard outflow
`build`	flow (chain)	Fires once to build additional content
`retry`	flow	Player pressed "Retry"
`contStart`	flow	Player pressed "Continue at Start"
`contHere`	flow	Player pressed "Continue Here"

Custom buttons can be added via the editor (same system as EndScreen Begin).

Internals

Key Methods

Method	Description
`openDialogue()`	Builds complete end screen: buttons, header, results, objectives, ratings
`closeDialogue()`	Triggers `ChangeState('play')`
`buttonPushed(action)`	Sets matching output and closes dialogue
`updateButtons()`	Manages dynamic custom button pins
`work()`	Handles build flow and auto-skip timer

Data Properties

Property	Default	Description
`data.includeRetryButton`	`true`	Include retry button
`data.autoBuild`	`true`	Auto-build header, results, objectives, and ratings

How It Works

When flow activates, if autoBuild is true, calls startUIBuilding('endScreen', self).
openDialogue() builds the full button set (next missions, retry with entry fee, continue, tutorial override, custom buttons).
If autoBuild, automatically adds header, text panel with results/attempt, objectives, and ratings, then calls finishUIBuilding().
If autoBuild is false, the build chain output lets downstream nodes add content manually.
Auto-skip timer stops mission after 2 seconds if autoSkipStartScreen is set.

Usage Example

-- Simple usage: single node handles everything
-- [Trigger] → [EndScreen Whole] → (retry) → [Reset]
--                                → (contHere) → [Continue]

-- With custom content (autoBuild = false):
-- [EndScreen Whole] → (build) → [Custom Panel] → [Screen Finish]

Key Dependencies

mgr.modules.ui - UI building system
career_career.isActive() / career_modules_playerAttributes - career integration
gameplay_missions_missions - next mission linking
gameplay_missions_missionScreen.stopMissionById() - auto-skip

Previously Undocumented (Added by Audit)

C:getCmd(action) - Function handling getCmd logic
Input Pin: _active (any)

Overview

Node Name: EndScreen Whole
Category: singleActive
File: extensions/flowgraph/nodes/ui/updatedUI/endScreenWhole.lua

Note: Showing two of these at the same time will break everything.

Pin Schema

Input Pins

Pin	Type	Description
`flow`	flow	Activates the end screen
`reset`	flow (impulse)	Resets the node
`text`	string/table	Results subtext
`failed`	bool	Whether the player failed (hidden)
`change`	table	Attempt change data
`progressKey`	string	Key for the attempt
`customBtnsFirst`	bool	Custom buttons before defaults (hidden)

Output Pins

Pin	Type	Description
`flow`	flow	Standard outflow
`build`	flow (chain)	Fires once to build additional content
`retry`	flow	Player pressed "Retry"
`contStart`	flow	Player pressed "Continue at Start"
`contHere`	flow	Player pressed "Continue Here"

Custom buttons can be added via the editor (same system as EndScreen Begin).

Internals

Key Methods

Method	Description
`openDialogue()`	Builds complete end screen: buttons, header, results, objectives, ratings
`closeDialogue()`	Triggers `ChangeState('play')`
`buttonPushed(action)`	Sets matching output and closes dialogue
`updateButtons()`	Manages dynamic custom button pins
`work()`	Handles build flow and auto-skip timer

Data Properties

Property	Default	Description
`data.includeRetryButton`	`true`	Include retry button
`data.autoBuild`	`true`	Auto-build header, results, objectives, and ratings

How It Works

When flow activates, if autoBuild is true, calls startUIBuilding('endScreen', self).
openDialogue() builds the full button set (next missions, retry with entry fee, continue, tutorial override, custom buttons).
If autoBuild, automatically adds header, text panel with results/attempt, objectives, and ratings, then calls finishUIBuilding().
If autoBuild is false, the build chain output lets downstream nodes add content manually.
Auto-skip timer stops mission after 2 seconds if autoSkipStartScreen is set.

Usage Example

-- Simple usage: single node handles everything
-- [Trigger] → [EndScreen Whole] → (retry) → [Reset]
--                                → (contHere) → [Continue]

-- With custom content (autoBuild = false):
-- [EndScreen Whole] → (build) → [Custom Panel] → [Screen Finish]

Key Dependencies

mgr.modules.ui - UI building system
career_career.isActive() / career_modules_playerAttributes - career integration
gameplay_missions_missions - next mission linking
gameplay_missions_missionScreen.stopMissionById() - auto-skip

Previously Undocumented (Added by Audit)

C:getCmd(action) - Function handling getCmd logic
Input Pin: _active (any)

EndScreen Whole (Flowgraph Node)

Overview

Pin Schema

Input Pins

Output Pins

Internals

Key Methods

Data Properties

How It Works

Usage Example

Key Dependencies

Previously Undocumented (Added by Audit)

See Also

On this page

EndScreen Whole (Flowgraph Node)

Overview

Pin Schema

Input Pins

Output Pins

Internals

Key Methods

Data Properties

How It Works

Usage Example

Key Dependencies

Previously Undocumented (Added by Audit)

See Also

On this page