Component Reference

CCDS components live in namespace BoneCrackerGames.CCDS. The tables list their Add Component → BoneCracker Games → CCDS → paths where defined; networking support components are described separately below.

01Naming conventions

02Base classes

MonoBehaviour
├── ACCDS_Component            [SelectionBase] — caches the scene manager
│   ├── ACCDS_Vehicle          [DefaultExecutionOrder(10)] — health, damage, control lock
│   └── CCDS_Singleton<T>      thread-safe generic singleton
├── ACCDS_Manager              minimal base for managers
├── ACCDS_PunComponent         MonoBehaviour locally; MonoBehaviourPunCallbacks with BCG_CCDS_PUN
└── ACCDS_Mission              SDK-independent mission base
    └── ACCDS_MultiplayerMissionBase

Interfaces:

Implement ICCDS_CheckEditorError on your own components and the Validation Panel reports them alongside CCDS's.

ACCDS_PunComponent retains public virtual void OnEnable() / OnDisable() hooks without PUN. Derived components should use public override and call the base implementation in both SDK states. PhotonViewComp exists only under BCG_CCDS_PUN; guard SDK-specific code with that symbol. Neither this base nor ACCDS_Mission requires an authored PhotonView.

ACCDS_Vehicle

The base for every CCDS vehicle. Beyond component caching it provides:

OnEnable raycasts down from the first wheel and snaps the vehicle to the ground, resetting velocities unless skipVelocityResetOnEnable is set.

03Optional networking

During Play Mode with BCG_CCDS_PUN, CCDS generates PhotonView components from bindings. Without PUN, the same bindings, missions, vehicles and UI component types remain available for local gameplay. CCDS_NetworkBinding.GeneratedView is null when no view has been generated; IsPrepared and Origin describe runtime preparation.

Prefab bindings use sceneId = 0. In a saved authoring scene, Tools → BoneCracker Games → CCDS → Multiplayer Setup → Register Active Scene and Assign IDs records the scene, assigns IDs and adds the bootstrap when bindings need one. This changes the scene without saving it automatically. See scene registration.

The dependency bootstrap owns BCG_CCDS_PUN and enables it only after detecting a complete supported SDK on disk. Keep the binding data when removing or reinstalling the optional SDK; do not replace it with authored PhotonViews.

04Managers

Create them with Tools → BoneCracker Games → CCDS → Create Scene Managers →, not by hand.

05Player and AI

Add these with the vehicle setup prompt — it also creates the binding and stores ordered observer references, with or without PUN installed. See Add Your Own Vehicle.

06Cameras

07Missions

Support components:

08UI

Animation helpers under UI/Animations/:

CCDS UI Panel Transition · CCDS UI Layout Group Element Popper · CCDS UI Panel Enabler On Text Change · CCDS UI Slider Highlighter · CCDS UI Text Highlighter · CCDS UI Text Popper On Text Change

09Replay

States: Neutral, Recording, Playing, Paused, Rewinding.

Default keys on CCDS_ReplayUI: R toggle panel, F5 record, F6 play, F7 pause. R also resets the vehicle in CCDS_Player — rebind one of them if you ship the replay UI.

10Debug

The panel toggles on F12 and requires CCDS_Settings.enableDebugPanel. The console toggles on F11.

11Misc

12Testing

Sandbox components for CCDS_Vehicles_Prototype. Not for shipping scenes.

13Script execution order

Set automatically by CCDS_ScriptExecutionOrderSetup on every editor load. Do not set it per script — your value is overwritten.

The shape: save data first, then networking, then managers, then vehicles, then cameras, then debug. RCCP and RTC manage their own orders independently.

14Next

• Scripting API
• Events Catalog