G2G Activity

Background activity that spawns random vehicles into the world. Uses a step-based sequence with fade-to-black transitions for vehicle spawning.

Public API

| Function | Signature | Returns | Description | |------ | M.dependencies | table | {"util_stepHandler"} |---- | M.activateFinished | () | nil | activateFinished ||-----------| | M.onVehicleSwitched | onVehicleSwitched handler |---------|-------------| | M.activate | () | nil | Starts the background activity, spawns vehicles | | M.deactivate | () | nil | Removes all spawned vehicles | | M.toggleActive | () | nil | Toggles activation state | | M.isActive | () | boolean | Returns whether the activity is active | | M.getVehicleOptions | () | table | Returns filtered list of eligible vehicle models/configs | | M.onDeserialized | onDeserialized handler |

Dependencies

• util_stepHandler

Vehicle Selection

getVehicleOptions() filters the vehicle list with these criteria:

• Type: Cars and Trucks only (no buses, no auxiliary)
• Performance: Must have top speed > 10 (excludes static/broken configs)
• Mode filters (hardcoded to Default):
  • Old Cars: max year ≤ 1985
  • New Cars: min year > 1985
  • Race and Rally: Config type Race or Rally
  • RWD Only: Drivetrain == RWD
  • Off-road: Off-Road Score ≥ 50

Returns array of {model, configs[], paints[]} entries.

How It Works

1. activate() builds a step sequence: fade-to-black → spawn N vehicles → fade-from-black
2. Each vehicle is randomly selected from getVehicleOptions() with random config
3. Spawned vehicle IDs stored in vehicleIds for cleanup
4. deactivate() deletes all spawned objects from scene tree
5. Auto-deactivates on mission end and career start

Spawn Sequence

local sequence = {
  stepper.makeStepFadeToBlack(),
  stepper.makeStepSpawnVehicleSimple(model, config, callback),
  -- ... repeat for vehicleCount
  stepper.makeStepFadeFromBlack()
}
stepper.startStepSequence(sequence, finishedCallback)

Hooks

Notes

• Default vehicleCount is 1
• Vehicle options cached after first call
• Uses editor.onRemoveSceneTreeObjects for clean editor integration
• Not persistent across serialization - always deactivates on save

Module Variables

See Also

• Gameplay Systems Guide - Guide