khapaev/caliber-ads-calculator

1. This repository is a small, browser-side calculator for Caliber ADS sensitivity. There is no backend, database, or build pipeline visible in the repo; the whole app appears to run as a static site.

2. The architecture is centered in docs/, which likely serves as the deployable front-end bundle:

- docs/index.html provides the page structure and mounts the calculator UI.

- docs/styles.css handles presentation.

- docs/app.js contains the interactive logic and calculations.

- docs/weapons.json is the static game-data source the calculator reads from.

3. The main domain boundary is between UI and game data. The UI lets the user pick an operator/weapon, while the JSON data defines the weapon inventory, compatible sights/modules, and other parameters needed for sensitivity math.

4. The core computation flow is client-side:

- user selects an operative or weapon,

- the app filters the available sights to only those compatible with that weapon,

- the app calculates ADS sensitivity for the same cm/360,

- it also calculates ADS sensitivity with FOV compensation,

- and it outputs the final ADS FOV plus the resulting AimSensitivityModifier values.

5. weapons.json is the primary data dependency. It likely encodes the mapping between operatives, weapons, and supported modules/sights extracted from Caliber version 1.4.0.9646.13464, so the correctness of the calculator depends on this file staying in sync with the game data.

6. app.js is the main orchestration layer. It likely owns:

- loading/parsing weapons.json,

- populating dropdowns or selectors,

- reacting to user input,

- performing all math for ADS/FOV/sensitivity,

- rendering computed results back into the page.

7. index.html and styles.css form a simple presentation boundary. There are no signs of framework routing, server templates, or component hierarchy beyond what a small interactive page would need.

8. The app’s data flow is one-way and local: static JSON data plus user input produce computed sensitivity outputs in the browser. There is no evidence of network calls, persistence, authentication, or cross-service communication.

9. The repository is documentation-light and purpose-specific. The README confirms the calculator’s scope: it is a technical sensitivity tool for Caliber, not a general game companion or stats tracker.

10. For an architecture diagram, the key boxes are:

- Browser/UI layer,

- Calculation logic in app.js,

- Game-data source in weapons.json,

- Static hosting surface in docs/.

11. The important external dependency is the game’s internal data model, but it is already captured offline inside the repo. That means the system’s “integration point” is not a live API, but a curated static extraction from the game client.

12. In short: this is a self-contained static calculator where the front-end owns all interaction and computation, and the JSON file provides the authoritative compatibility/data model used by the sensitivity formulas.