This is an old revision of the document!
Table of Contents
Torque Tycoon > Game Components
Player Statistics
Torque Tycoon records 39 active statistics for each pilot. They cover flying, logistics, exploration, flight quality and defensive contribution. Achievements place milestones on these values; Ranks combine selected achievement rows into four progression ladders.
Recording starts with the first sortie, even before a Discord account is linked. Linking through DCSBot makes the recorded progress eligible for achievements, ranks and Discord roles, including progress earned before linking.
Where to see them
Tycoon > My Statistics in the Radio Menu shows your own values, field positions, recent achievements and nearest achievement targets. Refresh from backend pulls a fresh snapshot after a landing or delivery.
In Discord, /tycoon stats shows a player's values and /tycoon top shows a leaderboard where enabled. Your cockpit card is personal and is shown only to your own DCS group.
Flight and activity
| Statistic | What it measures |
|---|---|
| Flight hours | Total time in player slots, mirrored from DCSBot sessions. |
| Takeoffs | Takeoffs recorded in DCSBot sessions. |
| Landings | Landings recorded in DCSBot sessions. This is the value used by the landing achievement row. |
| Crashes | Crashes recorded in DCSBot sessions. |
| Flight distance | Distance flown by player-controlled aircraft, in kilometres. |
| Tycoon landing events | Landing events exported directly by the Tycoon mission runtime. This is kept separately from the DCSBot landing counter. |
Core logistics and exploration
| Statistic | What it measures |
|---|---|
| Delivered crates | Tycoon cargo crates delivered by the player. |
| Delivered freight | Total delivered cargo weight in metric tons. |
| Sites supplied | Distinct delivery targets supplied by the player. |
| Mapped sites | Distinct sites whose mapping was attributed to the player. |
Flight quality and operating conditions
The mission samples player aircraft every 0.5 seconds, but it does not store the samples or a position track. At the end of a sortie it writes only counters and extrema.
| Statistic | What it measures |
|---|---|
| Smooth cargo deliveries | Deliveries whose carrier sortie had at least ten cargo samples and kept at least 95% of them within 20 degrees of bank and 3 m/s downward speed. |
| Steady cargo sorties | Cargo sorties with at least ten cargo samples and no sampled bank angle above 45 degrees. |
| Feather-touch landings | Landings with no more than 1.0 m/s sampled downward speed. |
| Nap-of-the-earth sorties | Sorties of at least 50 km with at least 80% of airborne samples below 50 m AGL. |
| Maximum sampled bank | Largest absolute bank angle sampled across the player's sorties. |
| Maximum sampled pitch | Largest absolute pitch angle sampled across the player's sorties. |
| Maximum sampled descent | Largest downward vertical speed sampled across the player's sorties. |
| Lowest sampled AGL | Lowest sampled height above terrain. |
| Efficient deliveries | Deliveries with a delivery-efficiency factor of at least 95%. |
| Night deliveries | Deliveries made between sunset and sunrise for the mission date. |
| Low-visibility deliveries | Deliveries made while the archived mission visibility was below 3 km. |
| Longest delivery | Longest direct source-to-destination delivery distance. |
| Damaged deliveries completed | Deliveries completed after the carrier or cargo took combat damage. |
| Landing streak without carrier loss | Largest number of landings between player carrier-loss events. |
Advanced logistics
| Statistic | What it measures |
|---|---|
| Fresh site deliveries | First attributed delivery after a site's first mapping, provided it arrived within one hour. |
| Projects supplied | Completed construction projects that received a matching player delivery while the project was open. |
| Solo city supply sessions | Completed sessions in which one player was the City's only attributed supplier and supply stayed at target throughout. |
| Mixed material days | UTC days on which the player delivered Lumber, Steel and Building Materials. |
| Production runs supplied | Completed production runs that consumed player-delivered input crates. |
| Delivery lineage depth | Deepest valid input-production chain behind a delivered crate. |
| Regions fully supplied | Regions in which the player has supplied every active mapped site. |
| Emergency deliveries | Deliveries made while the destination was below 10% supply before delivery. |
| All sites supplied | Whether the player has supplied every site that is currently active and mapped. |
Advanced exploration
| Statistic | What it measures |
|---|---|
| Bearing-only discoveries | Sites mapped from rumored state through direction-finding work. |
| Stations calibrated | DF stations for which the same player completed all twelve sectors. |
| First site mappings | Sites for which the player owns the earliest attributed mapping event. |
Bearing-only attribution starts with the Phase 8 catalogue. Older mapping events still count as mapped sites, but are not guessed retroactively to have been bearing-only discoveries.
Security contribution
| Statistic | What it measures |
|---|---|
| Threats neutralized | Player-attributed kills against units registered as Tycoon threats or ambushes. General DCSBot kill totals do not count. |
| Threat groups cleared | Complete static Tycoon threat groups to which the player contributed a hit or kill. |
| Ambushes repulsed | Cleared Tycoon ambushes to which the player contributed while the target survived. |
For a cleared group or ambush, every attributed participant receives group credit. Unit kills are credited only to the killer. An ambush ending in target_destroyed does not count as repulsed.
Privacy
/tycoon mydatalists everything stored about you./tycoon optoutremoves you from leaderboards, announcements, Discord rank roles and public lists. Your own numbers remain visible to you./tycoon deletemydataerases your data where the server has enabled it. Achievements and ranks are deleted, names are removed and world-history facts are retained only under a random pseudonym.
Your IP address is never stored. Flight telemetry retains sortie aggregates only; it does not retain sampled positions or a flight track.
