Request Abandon Node

Listens for the player pressing the abandon/quit button during a mission. When this node exists in a flowgraph, the mission must be stopped manually (auto-stop is suppressed). Category: logic.

Pins

Inputs

Outputs

Behavior

• C:work(): Each frame, checks self.reset flag. If true, outputs flow and value=true for one frame, then resets
• C:onRequestAbandon(): Hook handler - sets self.reset = true when player requests abandon
• C:_afterTrigger(): Clears reset flag after processing
• data.blocksOnResetGameplay = true - prevents default reset behavior
• Logs abandon event to flowgraph manager

Lifecycle

• _executionStarted(): Clears reset flag
• _executionStopped(): Clears reset flag

Usage Example

-- Typical abandon handling flow:
-- [Request Abandon].flow → [Show Confirm Dialog] → [Finish Mission]

-- Or immediate stop:
-- [Request Abandon].flow → [Activity Stop]

-- The node's existence tells the system that abandon handling
-- is managed by the flowgraph, not automatically.
-- Without this node, pressing abandon auto-stops the mission.

Internal Details

• Uses _afterTrigger (underscore prefix) for internal cleanup - called after graph traversal
• The reset flag ensures impulse behavior: output fires for exactly one frame
• Previously used action maps (FlowgraphControls) - now commented out

Additional Exports

init(mgr, ...)

• mgr - any
• ... - any

drawMiddle(builder, style)

• builder - any

• style - any

• name - string - (see source)

• color - any - (see source)

• description - any - (see source)

• category - string - (see source)

• pinSchema - table - (see source)

• tags - table - (see source)

See Also

• Activity Attempt Node - Related reference
• Activity Flow Node - Related reference
• Activity Hook Trigger Node - Related reference
• FlowGraph Guide - Guide