How truong0111/percasbuildhelper works
Project type and purpose
• This is a Unity Editor extension package (“Percas Build Helper”) that provides build‐management, versioning and runtime performance utilities for Android games.
• It installs via Unity Package Manager and consists of two halves: Editor scripts (Build/Version/Validator UIs and workflows) and Runtime scripts (performance watching and utility toggles).
File structure
• Top-level:
• Editor/ – contains all .cs Editor scripts and asmdef for the editor assembly
• Runtime/ – contains runtime utilities, settings ScriptableObjects and asmdef for the runtime assembly
• package.json – Unity package manifest
• README.md – describes features and usage
• Under Editor/BuildHelper: classes for configuring and invoking Unity’s build pipeline (ConfigBuild, PercasBuilder), UI windows (PercasEditor), data containers (PercasConfigSO, PercasUtilitySO).
• Under Editor/Validator: simple pre‐build checks.
• Under Runtime: PercasRuntimeSettingsSO holds runtime configuration; PercasUtility provides in‐game performance stats UI and utility controls.
README for further insights
• Instructions on how to import via Package Manager and how to operate each feature.
a. Main components
• Unity Editor Host
• Percas Editor Plugin
• Build Management UI
• Version Management UI
• Validator subsystem
• ScriptableObject assets (PercasConfigSO, PercasUtilitySO)
• Unity Build Pipeline & Android SDK (external service)
• Percas Runtime Library
• Performance Monitor UI
• Utility toggles (time scale, FPS limit, logs)
• ScriptableObject settings (PercasRuntimeSettingsSO)
b. Relationships and interactions
• Editor UI invokes PercasBuilder which calls UnityEditor.BuildPipeline API, passing ConfigBuild settings (keystore, output folder, naming).
• Version UI updates PlayerSettings.version and PlayerSettings.bundleVersionCode.
• Validator runs pre‐build checks on project settings/assets.
• On install, Package Manager registers the Percas.Editor and Percas.Runtime assemblies.
c. Architectural patterns and principles
• Separation of concerns: Editor‐only tooling vs Runtime performance code.
• Data driven via ScriptableObjects for both build and runtime settings.
• Use of Unity Package Manager asmdef files to define clear assembly boundaries.
d. Technologies and frameworks
• Unity Editor Scripting API
• UnityEngine.Profiling for performance metrics
• Android SDK / JDK for build signing
• Unity Package Manager for distribution
Elements
• Clear component labels (e.g., “Build Management UI”, “PercasBuilder”, “PercasRuntimeSettingsSO”)
• From UI → Builder → BuildPipeline → Android SDK
• From Version UI → PlayerSettings
• At runtime: PercasUtility → Profiling APIs → On-screen UI
• Runtime scripts in another
• External systems (Android SDK, Unity APIs) in a third