
TrialStats
Track your Trial progress in real-time with clean UI, smart stats, and seamless integration.
Screenshots






About this Mod
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
- Dependency Verification: Ensure the active runtime environment contains validated versions of the Fabric Loader, Fabric API, and Cloth Config API.
- Deployment: Inject the compiled
TrialStatsbinary payload directly into the target client'smodsfile hierarchy. - 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.
Available Versions
How to Install TrialStats on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (1.21.11).
Install Mod
Open the mod browser in the dashboard and search for "TrialStats". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.21.11, 1.21.10, 1.21.9 (+9 more)
Server-side
✗ UnsupportedRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
TrialStats server crashes on startup – what to do?
Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.21.11). You can switch loaders with one click in the panel.
Is TrialStats compatible with fabric?
TrialStats officially supports fabric for Minecraft 1.21.11, 1.21.10, 1.21.9. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with TrialStats – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if TrialStats consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install TrialStats with just one click on your server.