Customization and the Garage

01How the pieces fit

CCDS does not re-implement customization. It wraps RCCP's customizer with a purchase and persistence layer.

02The vehicle must be customizer-ready

The customization UI does nothing on a vehicle without RCCP_Customizer. When CCDS adds player components it configures the customizer for you:

If you add RCCP_Customizer by hand, match these. Leaving autoSave on gives you two systems writing the same state, and RCCP's copy will win at the wrong moment.

03Items and upgrades

Everything purchasable is a CCDS_CartItem:

CartItemType has eight values:

Paint · Wheel · Spoiler · Decal · Neon · UpgradeEngine · UpgradeHandling · UpgradeSpeed

Save keys are the identity of an item. Two items sharing a key share ownership. Changing a key on a shipped game makes previously bought items look unowned. Prefix them — paint_red, wheel_sport_01, upg_engine — and never reuse.

One-off items

CCDS_UI_PurchaseItem handles anything bought once.

It implements IPointerClickHandler, so the purchase fires from a UI click.

Levelled upgrades

CCDS_UI_PurchaseUpgrade handles engine, handling and speed, which are bought repeatedly.

The price is not fixed. It scales with the current level:

UpgradePrice = (int)(Mathf.InverseLerp(0, 6, UpgradeLevel + 1) * (defaultPrice * 1.5f));

So the displayed price rises each level, and the price on the cart item is a base figure, not what the player pays. Set price and check the resulting curve in play mode rather than expecting the literal number.

04What an upgrade actually changes

Upgrades act on the RCCP upgrade components, whose efficiency ceilings come from the vehicle roster:

All three default to 1.2 — a fully upgraded car is 20% better than base. Raise them per vehicle in CCDS_PlayerVehicles.asset; see Add Your Own Vehicle.

A vehicle missing one of these components accepts the purchase and applies nothing. Check the prefab has all three before shipping a car.

05Wheels

Selectable wheels live in CCDS_ChangableWheels.asset in Assets/CCDS/Resources/:

As with vehicles, the array index is the persistent ID written to the save file's ownedWheels. Append; do not insert or reorder.

06Scripting purchases

using BoneCrackerGames.CCDS;

// One-off items
if (!CCDS.IsItemPurchased("paint_red")) {
    if (CCDS.GetMoney() >= 500) {
        CCDS.ChangeMoney(-500);
        CCDS.PurchaseItem("paint_red");   // marks owned and saves
    }
}

// Levelled upgrades
CCDS.PurchaseUpgrade("upg_engine");
bool owned = CCDS.IsUpgradePurchased("upg_engine");

PurchaseItem and PurchaseUpgrade both call Save() themselves — no separate save is needed.

Neither one charges the player. Deduct with ChangeMoney yourself, and check affordability first; there is no built-in guard against negative balances.

07Vehicle ownership

Separate from items:

CCDS.IsOwnedVehicle(3);     // owned?
CCDS.UnlockVehicle(3);      // grant
CCDS.LockVehicle(3);        // revoke
CCDS.UnlockAllVehicles();   // useful while testing
CCDS.SetVehicle(3);         // make it the active selection

The index is the position in CCDS_PlayerVehicles.playerVehicles. A vehicle priced 0 is owned from the start.

08The garage marker

CCDS_Marker_Garage is a trigger volume that returns the player to the main menu, which is where customization happens.

Enter it and remain inside for 3 seconds. Leaving early cancels. There is no key to press.

Place one where the player would expect a garage. Its collider must be a trigger and large enough that a car at speed cannot pass through in under three seconds.

09Persistence

Customization state lands in the JSON save file in Application.persistentDataPath:

Clear it while testing with Tools → BoneCracker Games → CCDS → Delete Save Data, or CCDS.ResetGame() at runtime.

10Common problems

11Next

• Add Your Own Vehicle — where the upgrade ceilings are set.
• Scripting API — the full money and ownership surface.