<div align="center"> <h1>TrialStats</h1> <p>A high-performance, client-side session auditing and metrics instrumentation utility for Trial Chambers.</p> <a href="https://github.com/Hardik-Verma/TrialStats"><img src="https://cdn.jsdelivr.net/npm/@intergrav/devins-badges@3/assets/cozy/available/github_vector.svg" height="36"></a> <a href="#"><img src="https://cdn.jsdelivr.net/npm/@intergrav/devins-badges@3/assets/cozy/built-with/gradle_vector.svg" height="36"></a> <a href="#"><img src="https://cdn.jsdelivr.net/npm/@intergrav/devins-badges@3/assets/cozy/requires/fabric-api_vector.svg" height="36"></a> <a href="https://modrinth.com/mod/trialstats/"><img src="https://cdn.jsdelivr.net/npm/@intergrav/devins-badges@3/assets/cozy/supported/fabric_vector.svg" height="36"></a> </div> --- ### **⚠️ Nomenclature Re-indexing Notice** **TrialTracker has officially been refactored and renamed to TrialStats.** This structural rebranding aligns the utility with its core architecture: executing localized telemetry, indexing vault history, capturing trial data blocks, and compiling active runtime session analytics. **TrialStats is explicitly engineered as a client-side analytics utility for legitimate gameplay pipelines; it contains zero macro, automation, or exploit simulation vectors.** *Note: For backward compatibility with legacy binaries, fallback references to `trialtracker` may persist within internal mod identifiers, configuration subdirectories, file path mapping schemas, and historical archive references.* --- ### **Overview** **TrialStats** implements an asynchronous tracking and performance logging platform tailored entirely for Trial Chamber environments. Operating completely within the local client runtime without requiring server-side server software modifications, it dynamically intercepts player position vectors to initiate background recording loops the moment a Trial Chamber boundary configuration is verified. --- ### **Key Features** * **Automated Boundary Verification** — Tracks and monitors local spatial data to automatically initialize and terminate session auditing intervals immediately upon entering or exiting Trial Chamber parameters. * **Granular Loot & Combat Telemetry** — Compiles detailed, multi-channel registers tracking standard vault interactions, Ominous Vault ingestion states, Trial Spawner event frequencies, and total localized entity terminations per lifecycle. * **Persistent Structural Archiving** — Preserves historical datasets of structural run parameters, detailing coordinate mapping history for previously unlocked vaults and local workspace indexes. * **Integrated HUD Projections** — Overlays dynamic HUD indicators and world markers natively within the local screen projection layout to assist with live chamber tracking. * **Zero Server Overhead** — Operates entirely as a modular client thread, bypassing the need for dedicated server plug-ins or configuration adjustments while supporting immediate settings updates. --- ### **Execution & Operation** 1. **Dependency Verification:** Ensure the active runtime environment contains validated versions of the **Fabric Loader**, **Fabric API**, and **Cloth Config API**. 2. **Deployment:** Inject the compiled `TrialStats` binary payload directly into the target client's `mods` file hierarchy. 3. **Initialization:** Access the localized settings matrix using the custom keybind to configure auto-termination profiles, toggling HUD projections, and auditing saved session history. --- ### **Dependencies & Integration** * **Required Environments:** Fabric API, Cloth Config API. * **Optional Integrations:** Mod Menu framework (provides direct, streamlined interfacing with native configuration panels). --- <div align="center"> <p>Available exclusively for the Fabric Mod Loader ecosystem.</p> </div>

TrialStats

A high-performance, client-side session auditing and metrics instrumentation utility for Trial Chambers.

### ⚠️ Nomenclature Re-indexing Notice TrialTracker has officially been refactored and renamed to TrialStats.

This structural rebranding aligns the utility with its core architecture: executing localized telemetry, indexing vault history, capturing trial data blocks, and compiling active runtime session analytics. TrialStats is explicitly engineered as a client-side analytics utility for legitimate gameplay pipelines; it contains zero macro, automation, or exploit simulation vectors.

Note: For backward compatibility with legacy binaries, fallback references to `trialtracker` may persist within internal mod identifiers, configuration subdirectories, file path mapping schemas, and historical archive references.

### Overview TrialStats implements an asynchronous tracking and performance logging platform tailored entirely for Trial Chamber environments. Operating completely within the local client runtime without requiring server-side server software modifications, it dynamically intercepts player position vectors to initiate background recording loops the moment a Trial Chamber boundary configuration is verified.

### Key Features Automated Boundary Verification — Tracks and monitors local spatial data to automatically initialize and terminate session auditing intervals immediately upon entering or exiting Trial Chamber parameters. Granular Loot & Combat Telemetry — Compiles detailed, multi-channel registers tracking standard vault interactions, Ominous Vault ingestion states, Trial Spawner event frequencies, and total localized entity terminations per lifecycle. Persistent Structural Archiving — Preserves historical datasets of structural run parameters, detailing coordinate mapping history for previously unlocked vaults and local workspace indexes. Integrated HUD Projections — Overlays dynamic HUD indicators and world markers natively within the local screen projection layout to assist with live chamber tracking. Zero Server Overhead — Operates entirely as a modular client thread, bypassing the need for dedicated server plug-ins or configuration adjustments while supporting immediate settings updates.

### Execution & Operation 1. Dependency Verification: Ensure the active runtime environment contains validated versions of the Fabric Loader, Fabric API, and Cloth Config API. 2. Deployment: Inject the compiled `TrialStats` binary payload directly into the target client's `mods` file hierarchy. 3. Initialization: Access the localized settings matrix using the custom keybind to configure auto-termination profiles, toggling HUD projections, and auditing saved session history.

### Dependencies & Integration Required Environments: Fabric API, Cloth Config API. * Optional Integrations: Mod Menu framework (provides direct, streamlined interfacing with native configuration panels).

Available exclusively for the Fabric Mod Loader ecosystem.