How sassembla/autoya works
Core Modules and Their Roles
• AssetBundle Module: Represented in both the “Assets/Autoya/AssetBundle” folder and the “AssetBundles” directory at the root. This module handles the download, preloading, and management of asset bundles. Include subcomponents like AssetBundleList, AssetBundleLoader, and AssetBundlePreloader.
• Authentication Module: Found under “Backyard” and “ThirdPartyAuthentication.” This module is responsible for handling basic authentication flows (including third-party methods like SignInWithApple).
• Connection Module: Under “Assets/Autoya/Connections” and potentially integrated in “Backyard,” this module supports HTTP, TCP, and UDP communications with external servers or endpoints.
• Notification Module: Located in “Assets/Autoya/Notification,” this component manages both local and remote notifications and includes platform-specific plugins.
• Purchase/IAP Module: Under “Assets/Autoya/Purchase,” this module integrates with Unity Services (and possibly native services) to provide in-app purchasing.
• Information and Persistence Modules: Under “Assets/Autoya/Information” and “Assets/Autoya/Persistence.” They deal with displaying game information and managing local persistence or caching of data (e.g., URL caching, file persistence).
• Settings and Manifest: Configuration resources in “Assets/Autoya/Settings” and “Assets/Autoya/Manifest,” which supply essential runtime and build-time configuration.
• Editor Tools: Found under “Assets/Autoya/Editor” and the “Editor” directory that contains AssetGraph and AutoyaEditorTool components. These tools help with asset bundle building and link.xml generation.
• Test Framework: The “Assets/AutoyaTests” (and usage of MiyamasuTestRunner) represent the testing support, helping validate each module via unit and integration tests.
Relationships and Data Flow
• How the Unity runtime uses Autoya’s core modules for tasks like downloading asset bundles, authenticating users, and processing network requests.
• Authentication module with the Connection and Purchase modules where secure communications and user validation are required.
• Links from the Editor Tools to the AssetBundle Module, showing how build-time processes (asset bundle creation, manifest generation) feed into runtime use.
• That the Test framework interacts with all these modules to ensure correct behavior and integration.
Important Architectural Patterns and Design Principles
• Modularity & Separation of Concerns – Each feature (authentication, connection, asset management, etc.) is encapsulated in its own submodule.
• Editor vs. Runtime Separation – Differentiate between editor tools and runtime components, with a clear boundary for build processes versus game execution.
• Versioning & Updatability – The asset bundles and sub-assets are versioned (e.g., “1.0.0”, “1.0.1”), which suggests that the system supports incremental updates and asset updates.
Technologies & Integration Points
• Unity Engine: The underlying platform.
• Miyamasu Test Runner: For testing.
• Third-Party Authentication Plugins (e.g., SignInWithApple).
• Potential integration with Unity Services for in-app purchases.
• Networking libraries built into the Autoya framework (HTTP, TCP, UDP).
Putting It All Together
• An Editor Tools section that feeds into the runtime (illustrating pre-processing/build activities).
• An external interactions section (external authentication, purchase servers, asset servers) that communicate with the connection and purchase modules.
• Finally, include a testing “sandbox” that interacts with almost all modules to verify functionality.