Synchronizing group gameplay with TabletopKit

At a glance

Project structure

Source bundle/
└── TabletopKit Mini-Game/
    ├── TabletopKit Mini-Game/
    │   ├── TabletopKitMini-GameApp.swift
    │   ├── CustomAction.swift
    │   ├── GameEquipment.swift
    │   ├── GroupActivityManager.swift
    │   ├── GameInteraction.swift
    │   ├── GameObserver.swift
    │   ├── GameRenderer.swift
    │   ├── CustomEquipmentState.swift
    │   ├── Game.swift
    │   └── GameSetup.swift
    └── Packages/
        └── RealityKitContent/
            ├── Sources/
            │   └── RealityKitContent/
            │       └── RealityKitContent.swift
            └── Package.swift

Structure observations

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

Overall architecture

flowchart LR
    N1["TabletopKitMini-GameApp"]
    N2["GameView"]
    N3["GroupActivityManager"]
    N4["GameRenderer"]
    N5["TabletopKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

TabletopKit Mini-Game/TabletopKit Mini-Game/TabletopKitMini-GameApp.swift:16 — architecture anchor

@MainActor
@main
struct MiniGameApp: App {
    @State var game: Game

    init() {
        self.game = Game()
    }
    var body: some SwiftUI.Scene {
        WindowGroup {
            GameView()
                .environment(game)
        }
        .windowStyle(.volumetric)
        .defaultSize(width: 2, height: 2, depth: 2, in: .meters)
    }
}

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 TabletopKit.

Ownership and state

classDiagram
    ResetPlayer o-- EquipmentIdentifier : playerId
    ResetPlayer *-- Int : seat
    FreezePlayer o-- EquipmentIdentifier : playerId
    ActivatePlayer o-- EquipmentIdentifier : playerId

Ownership evidence

TabletopKit Mini-Game/TabletopKit Mini-Game/CustomAction.swift:11 — stored dependency or nearest verified ownership anchor

struct ResetPlayer: CustomAction {
    var playerId: EquipmentIdentifier
    // ...
}

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

TabletopKit Mini-Game/TabletopKit Mini-Game/Game.swift:40 — representative execution boundary

    @MainActor
    init() {
        renderer = GameRenderer()
        // ...
    }

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

TabletopKit Mini-Game/TabletopKit Mini-Game/TabletopKitMini-GameApp.swift:17 — representative type boundary

@MainActor
@main
struct MiniGameApp: App {
    @State var game: Game
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

TabletopKit Mini-Game/Packages/RealityKitContent/Sources/RealityKitContent/RealityKitContent.swift:10 — representative boundary

public let realityKitContentBundle = Bundle.module

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

Naming conventions

• Types: App: MiniGameApp; Manager: GroupActivityManager; Observer: GameObserver; Player: ActivatePlayer, FreezePlayer, Player, ResetPlayer; Renderer: GameRenderer; View: GameView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: apply, playerID, aimingSightID, bankID, stoneID, lilyPadID, logID, coinID.
• Files: TabletopKit Mini-Game/TabletopKit Mini-Game/GroupActivityManager.swift, TabletopKit Mini-Game/TabletopKit Mini-Game/GameInteraction.swift, TabletopKit Mini-Game/TabletopKit Mini-Game/GameObserver.swift, TabletopKit Mini-Game/TabletopKit Mini-Game/GameRenderer.swift, TabletopKit Mini-Game/TabletopKit Mini-Game/Game.swift, TabletopKit Mini-Game/TabletopKit Mini-Game/GameSetup.swift.

Architecture takeaways

• TabletopKitMini-GameApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches TabletopKit, RealityKit, SwiftUI, Spatial 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.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation