Skip to content

AlbiDR/Clash-Manager

Repository files navigation

Clash Manager Logo

Clash Manager

Backend Client Docs License: GPL v3

An engineered ecosystem for high-precision clan leadership.

Clash Manager is a production-grade, distributed architecture designed to automate the administrative complexities of competitive Clash Royale clans. It orchestrates a synchronized Supabase Binary Stack comprising an edge-native ingestion engine and a live-synchronized, persistence-backed progressive web application.



Screenshots

Light Mode
Dark Mode


Mission Architecture

Most clan tools rely on ephemeral API fetches-displaying a snapshot of the present moment that vanishes upon refresh. Clash Manager is different.

Persistence vs. Ephemerality

The system builds a Persistent Clan Database in Supabase. By archiving every war, every donation cycle, and every member interaction, the system constructs a rich historical tapestry. This allows for deep trend analysis, "heritage" tracking for long-term members, and the ability to spot performance decay before it becomes a problem.

The Scoring Engine

The system replaces intuition with a Complex Valuation Metric that sorts players by their true worth across two distinct dimensions.

Internal Metrics: Clan Roster (RPeS & PeS)
  • RPeS (Raw Performance Score): The absolute value derived from a member's contributions while being part of the clan (donations, war fame, war participation, trophies, tenure, Clan Voyage participation).
  • PeS (Performance Score): A relative percentage (0-100%) normalized against active clan benchmarks and adjusted via Inertia & Heritage logic.
  • Inertia & Heritage: Algorithmic decay applied to stagnant profiles, balanced by momentum tracking for incoming recruits to eliminate historic stat bias.
External Metrics: Headhunter Scouting (RPoS & PoS)
  • RPoS (Raw Potential Score): Calculated from a recruit's lifetime external battle logs, donations and war consistency.
  • PoS (Potential Score): A relative percentage (0-100%) normalized against the last month of scouted recruits and compared against the current internal clan performance for coherency.

The Headhunter Protocol

Recruitment is no longer passive. The Headhunter Engine continuously scans global tournament brackets and active members' battle logs via Supabase Edge Functions to identify elite, clanless recruits.

  • Edge-Native Discovery: High-concurrency Deno functions scan tournaments and active member battles around the clock.
  • Smart Filtering: Valibot-enforced validation ensures only top-tier candidates reach the UI.
  • Batch Operations: Sequence-driven blitzing allows leaders to invite recruits in minutes.


Dictionary

  • DeepNet: The high-performance, sovereign PWA infrastructure featuring intelligent local caching and live synchronization for administrative clan operations.
  • Headhunter: The global discovery engine that autonomously scans tournaments and active members' battles to identify elite, clanless recruits.
  • Nightly: The automated, multi-stage maintenance pipeline that ensures monorepo-wide structural integrity and synchronization.


System Ecosystem

Supabase Backend (Binary Stack)

The central nervous system. A high-performance infrastructure hosted on Supabase.

  • Role: Orchestrates ingestion pipelines, manages persistent state, and exposes materialized features.
  • Architecture: Unitary Database with isolated substrate, drivers, and features schemas.
  • Documentation: Read Technical Specifications
Client Core (PWA)

The command center. A Vue 3.5 Progressive Web Application designed for administrative operations.

  • Role: Provides a fluid, low-latency interface for data visualization and deeper analytics.
  • Features: Sovereign Design System, Persistent Caching (IndexedDB), and Hardware Haptics.
  • Documentation: Read Technical Specifications


Architectural Topology

View System Data Flow

The system utilizes a linear, high-integrity data flow with sub-second interaction latency.

flowchart TD
    subgraph Upstream
        CRAPI["Clash Royale API"]
    end

    subgraph "Supabase Backend"
        Edge["Edge Functions<br/>(Deno / Ingestion)"]
        DB["Postgres Substrate<br/>(Storage & Logic)"]
        Views["Feature Views<br/>(API Ready)"]
    end

    subgraph "Client Layer (PWA)"
        UI["Vue 3 Interface<br/>(Sovereign Design)"]
        Cache[(IndexedDB)]
    end

    Edge <-->|Round-Robin Fetch| CRAPI
    Edge -->|Ingest| DB
    DB -->|Project| Views
    UI <-->|RPC & Query| Views
    UI <-->|Hydration| Cache
    UI -->|Manual Trigger| Edge
Loading


Android Wrapper (TWA) Icons

The Android APK is a Trusted Web Activity packaged with Bubblewrap. The native project lives outside this repo at ~/bubblewrap-project.

Bubblewrap's default adaptive icon is broken (solid-white background layer, empty foreground, no monochrome layer). gen-android-icons.mjs replaces it with a correct, fully-native set generated from logo.svg:

Layer Source
background @color/ic_launcher_background — solid brand #0B0E14
foreground logo fitted by its true height into the 108dp safe zone (the mark is taller than wide)
monochrome white silhouette for Android 13+ themed icons
legacy pre-masked square + round PNGs for API < 26

Workflow — always regenerate icons immediately before building the APK, and always after bubblewrap update (which restores Bubblewrap's broken default):

pnpm icons:android                      # regenerate the adaptive icon set
pnpm icons:android -- --preview         # also emit launcher previews to .icon-preview/
cd ~/bubblewrap-project && bubblewrap build

The script is idempotent and validates against the live res tree. Override the target with ANDROID_RES_DIR=….



Nightly Pipeline

The Nightly pipeline is an automated maintenance and optimization engine designed as a 12-stage multi-agent system to enforce structural purity, optimize performance, and synchronize system documentation. Running nightly on the Nightly branch, this sequenced pipeline executes key phases to keep the monorepo pristine:

  1. Harden: The Runtime Integrity Auditor. Secures validation boundaries and eliminates the "any" plague across the stack.
  2. Verify: The Logic Integrity Auditor. Proves system integrity through automated test suite execution and logic proofs.
  3. Baseline Consolidation: The Declarative Schema Hardener. Hardens database schemas and consolidates incremental migrations into the master baseline.
  4. Optimize: The Substrate Hygiene Engineer. Refines code structures, enforces DRY principles, and prunes dead code.
  5. Document (README): The Architecture Truth Architect. Synchronizes technical blueprints with the implementation state (reconciles documentation drift).
  6. Document (TSDoc): The Interface Contract Architect. Hardens interface contracts and architectural remarks via TSDoc.
  7. Version Integrity: The Version Consistency Auditor. Eliminates version drift and enforces semantic versioning across the monorepo.
  8. Dependency Audit: The External Health Auditor. Monitors external dependency health and security.
  9. Refactor: The Structural Surgery Engineer. Orchestrates large-scale structural improvements and architectural migrations.
  10. APK & PWA Wrapper Integrity Auditor: Secures shell configuration boundaries, runtime safety, and configuration drift.
  11. APK & Native Wrapper Optimizations: Optimizes compilation assets, native caches, and native webview performance bounds.
  12. Hybrid Shell UX & UI Auditor: Verifies fluid native-wrapper responsiveness, screen transitions, and gesture integration under webview contexts.


License

GNU GPL v3. Copyright (c) 2026 AlbiDR. This project is free software and available under the GPL v3 License.

About

Clash Manager is an advanced, serverless PWA for Clash Royale clan leadership, engineered with Vue 3 and Google Apps Script. It features automated persistent logging, Moneyball-style algorithmic performance scoring, and a high-frequency background recruiting engine that transcends standard API wrappers.

Topics

Resources

License

Stars

Watchers

Forks

Contributors