× Phaseshift FCOM Tutorials

Understanding Quantum's file hierarchy



(This article is still under construction!)


  • Assets
    • Photon
    • QuantumUser
      • Editor
        • Quantum assets used in Unity Editor context like editor and gizmo settings, all content is added to the Quantum.Unity.Editor assembly.
      • Resources
        • Server Configs
        • Session Configs
      • Scenes
        • The default location for the initial demo scenes.
      • Simulation
        • Any code you want to synchronize across the network. This is the simulation code and will be added to the Quantum.Simulation.dll. Place game code and Qtn files in here. Important to note: Quantum 'does not know about Unity' from here, and therefore cannot be queried. Unity scripts should be saved within View.
        • OTN FIles
        • AssetTypes (Quantum's Scriptable Objects)
        • System scripts (Physics run, or anything you want to be synced/deterministic)
        • /Prototypes
          • Prototypes are like Unity's GameObject prefabs, but have Entity Prototypes and are as such instantiated over the network
      • View
        • Any code that you do not want synchronized across the network. This would be your usual Assets/Project/Runtime directory for code. Think of it as a store for scripts on the Unity side. It's content is added to the Quantum.Unity.dll.
    • Scenes

Documentation


To explore more on these topics, check out the documentation:

Quantum Project

Liked this article?

Please consider sharing!
Author

Josh Lyell

Game Developer