Chaparral Village: Building an immersive visionOS adventure game

At a glance

Project structure

Source bundle/
└── ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/
    ├── ChaparralVillage/
    │   └── ChaparralVillageApp.swift
    └── Packages/
        └── RCPCustomComponents/
            └── Sources/
                └── RCPCustomComponents/
                    ├── Managers/
                    │   ├── LevelManager.swift
                    │   └── InputManager.swift
                    ├── ZoneManagement/
                    │   └── ZoneTracker.swift
                    ├── Navigation/
                    │   └── PathfindPlayer.swift
                    ├── Alchemy/
                    │   ├── Cauldron.swift
                    │   ├── Curtain.swift
                    │   ├── Effect.swift
                    │   ├── PlantGeneration.swift
                    │   └── Potion.swift
                    ├── Cutscene/
                    │   └── Dialog.swift
                    └── EcsAbstractions/
                        └── EntityComponentQuery.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Shell, Swift.
• The verified tree contains 5 project/configuration file(s) and 277 source declaration(s).

Overall architecture

flowchart LR
    N1["ChaparralVillageApp"]
    N2["ContentView"]
    N3["ARManager"]
    N4["ContainerHandler"]
    N5["RealityKit / Spatial APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/ChaparralVillage/ChaparralVillageApp.swift:15 — architecture anchor

@main
struct ChaparralVillageApp: App {
    let saveManager = SaveManager()
    @State private var appState = AppState()
    @Environment(\.physicalMetrics) var physicalMetrics

    init() {
        RCPCustomComponentsPlugin
            .create()
            .setup(context: PluginHandler())
    }

    var body: some SwiftUI.Scene {
        WindowGroup(id: AppState.mainMenu) {
            ContentView(immersive: false, saveManager: saveManager, appState: appState)
                .frame(width: physicalMetrics.convert(1.5, from: .meters), height: physicalMetrics.convert(1.0, from: .meters))
                .frame(depth: physicalMetrics.convert(1.0, from: .meters))
        }
        .windowStyle(.volumetric)
        .windowResizability(.contentSize)

        ImmersiveSpace(id: AppState.immersiveSpace) {
            ContentView(immersive: true, saveManager: saveManager, appState: appState)
        }
        // Coexist with the person's currently active system Environment so they
        // remain in their chosen surroundings while playing instead of
        // dropping back to passthrough.
        .immersiveEnvironmentBehavior(.coexist)
    }
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into visionOS.

Ownership and state

classDiagram
    ChaparralVillageApp *-- SaveManager : saveManager
    ChaparralVillageApp *-- AppState : appState
    Cauldron *-- SIMD3 : waterNormal
    Cauldron *-- Float : waterLevel

Ownership evidence

ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/ChaparralVillage/ChaparralVillageApp.swift:17 — stored dependency or nearest verified ownership anchor

@main
struct ChaparralVillageApp: App {
    let saveManager = SaveManager()
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/ChaparralVillage/ChaparralVillageApp.swift:48 — representative execution boundary

private struct PluginHandler: @MainActor RealityComposerProContext {
    // ...
        _ component: ComponentType.Type
    // ...
}

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/Packages/RCPCustomComponents/Sources/RCPCustomComponents/ZoneManagement/ZoneTracker.swift:152 — representative type boundary

@MainActor
public protocol ZoneChangeHandler {
    static func on(entered: Zone, entity: Entity)
    static func on(overlapsChangedFor zone: Zone, entity: Entity)
    static func on(exited: Zone, entity: Entity)
}

The source explicitly defines local protocol relationships: BuoyancySim → PhysicsUpdateBehavior, CutsceneManager → SceneBound, ZoneCutsceneHandler → ZoneChangeHandler, DebugDraw → SceneBound, InputProxyManager → SceneBound, ARManager → SceneBound.

Access control

Reference code

ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/ChaparralVillage/ChaparralVillageApp.swift:18 — representative boundary

@main
struct ChaparralVillageApp: App {
    // ...
    @State private var appState = AppState()
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Main application flow

sequenceDiagram
    participant ARManager
    participant Task
    participant newSession
    participant handProvider
    ARManager->>Task: Start asynchronous work
    ARManager->>ARManager: run()
    ARManager->>Task: Start asynchronous work
    ARManager->>newSession: requestAuthorization()
    ARManager->>newSession: run()
    ARManager->>Task: Start asynchronous work
    handProvider-->>ARManager: hand() stream

Reference code

ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/Packages/RCPCustomComponents/Sources/RCPCustomComponents/Managers/ARManager.swift:81 — register()

    public func register(scene: Scene, on entity: Entity) {
        #if os(visionOS)
        if hasTriedToRun {
            return
        }
        hasTriedToRun = true
        Task {
            await self.spatialTrackingSession.run(.init(tracking: [.plane]))
        }
        Task {
            let newSession = ARKitSession()
            let auth = await newSession.requestAuthorization(for: [
                .worldSensing,
                .handTracking
            ])
            hasRequestedAuthorization = true
        // ...
            do {
                try await newSession.run(providers)
                self.planesSupported = canSupportPlanes
                Task {
                    for await hand in handProvider.anchorUpdates {
        // ...
                    }
                }
            } catch {
                Self.logger.error("Failed to start ar session: \(error)")
            }
            self.session = newSession
        }
        #endif
    }

Naming conventions

• Types: App: ChaparralVillageApp; Component: CapsuleTextComponent, CurtainClothBodyComponent, CurtainPinComponent, CurtainSimulationComponent, FadingComponent; Controller: DioramaViewController; Generator: PlantGenerator; Handler: ContainerHandler, DragHandler, DraggableObjectHandler, LadderTapHandler, PathfindPlayerTapHandler; Manager: ARManager, AudioManager, CutsceneManager, InputManager, InputProxyManager; Model: DialogModel, LadderModel; Player: Player.
• Protocols: ZoneChangeHandler, TapHandler, DragHandler, CustomRestore, PhysicsUpdateBehavior, Affordance, SceneBound.
• Methods: registerComponent, registerAction, registerSystem, store, load, fadeInRestoredEntities, fadeOutExistingLevel, unload.
• Files: ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/ChaparralVillage/ChaparralVillageApp.swift, ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/Packages/RCPCustomComponents/Sources/RCPCustomComponents/Managers/LevelManager.swift, ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/Packages/RCPCustomComponents/Sources/RCPCustomComponents/ZoneManagement/ZoneTracker.swift, ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/Packages/RCPCustomComponents/Sources/RCPCustomComponents/Managers/InputManager.swift, ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/Packages/RCPCustomComponents/Sources/RCPCustomComponents/Alchemy/Cauldron.swift, ChaparralVillageBuildingAnImmersiveVisionOSAdventureGame/Packages/RCPCustomComponents/Sources/RCPCustomComponents/Alchemy/Effect.swift.

Architecture takeaways

• ChaparralVillageApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches RealityKit, Spatial, SwiftUI, RealityKitScripting through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation