Campaign Dealer

Vehicle and item stock management for campaign dealer/vendor locations. Tracks purchasable inventory with add/remove/buy operations and campaign save/resume support.

Overview

Maintains a stock inventory keyed by item type (e.g., $$$_VEHICLES). Supports both table-based items (vehicles with model/config) and numeric items (currency). Integrates with the campaign save system for persistence.

Public API

Stock Structure

M.state.stock = {
  ["$$$_VEHICLES"] = {
    { model = "pickup", config = "configs/pickup_stock.pc" },
    { model = "coupe", config = "configs/coupe_sport.pc" }
  },
  ["$$$_MONEY"] = 5000  -- Numeric stock type
}

Item Operations

-- Add a vehicle to dealer stock
campaign_dealer.addToStock("$$$_VEHICLES", { model = "pickup", config = "stock.pc" })

-- Get available vehicles (returns deep copy)
local vehicles = campaign_dealer.getStock("$$$_VEHICLES")

-- Remove after purchase
campaign_dealer.removeFromStock("$$$_VEHICLES", { model = "pickup", config = "stock.pc" })

-- Numeric items
campaign_dealer.addToStock("$$$_MONEY", 1000)
campaign_dealer.removeFromStock("$$$_MONEY", 500)

Duplicate Detection

For table items, existItem checks if an identical entry already exists by comparing all key-value pairs:

-- Will not add duplicate if model+config already in stock
campaign_dealer.addToStock("$$$_VEHICLES", { model = "pickup", config = "stock.pc" })

Notes

• Item type keys are uppercased internally (string.upper)
• The buy function is a stub - purchase logic is handled in campaign_exploration.uiEventSelectVehicle
• Table items are matched by model + config for removal
• Stock persists across campaign saves via onSaveCampaign / onResumeCampaign
• Uses deepcopy for serialization to prevent reference issues
• goto continue pattern is used for early loop exit

See Also

• Campaign System - Overall campaign orchestration
• Campaign Exploration - Vendor/garage UI integration