Editorial Standards

How the math works

Every calculator on GamerStation is hand-written. I read the source material (developer documentation, patch notes, game API responses, official press kits, peer-reviewed automotive engineering texts where applicable), implement the formula in TypeScript, and verify the output against an in-game control case.

• Forza Horizon 6 Tune Calculator: Spring rates are computed from sprung corner mass and a target ride-frequency Hz per surface (the formula is k = (2π × f)² × m, standard race-engineering practice). Damper values map a critical-damping ratio onto the game's 1 to 20 slider scale. Differential lock scales with horsepower per drivetrain. Gearing is a geometric progression between launch ratio and top-gear ratio that targets the chosen top speed at redline.
• Tune Grade: Six to eight weighted rules per race category compare the user's tune values to standard conventions (e.g. drag wants low rear pressure and stripped aero; drift wants high rear pressure, high caster, locked rear diff). Rules and weights are documented in lib/forza-horizon-6/grade.ts.
• Dota 2 damage calculator: Implements the public damage formulas Valve documents in the Dota 2 source files and patch notes. Magic resistance, armor reduction, and pre/post-mitigation order match the in-game engine.
• Subnautica crafting tool: Walks recipe trees the same way the in-game fabricator does: every output item links to its inputs, and the simulator drains inventory greedily so an intermediate you already own does not count as a missing ingredient.
• LoL champion stats: Per-level stats come from Riot's public Data Dragon JSON, updated with each patch.

Where the data comes from

Game data on GamerStation falls into three categories. Tool-specific source notes appear in the footer of every page that uses outside data.

• 1. Publisher-published lists. The Forza Horizon 6 car list comes from forza.net, published officially by Microsoft. League of Legends champion and item data comes from Riot's public Data Dragon API. Dota patch notes come from Valve's official patch page.
• 2. CC-licensed wikis. Per-car Forza Horizon 6 stats (weight, HP, drivetrain, aspiration) come from the Forza Fandom wiki under CC BY-SA 4.0. Subnautica blueprint locations come from the Subnautica Fandom wiki on the same license. Wiki sources are attributed inline on every page that uses them.
• 3. User input. The Tune Calculator runs entirely on inputs the user types in (car weight, front weight distribution, class, drivetrain). Community Tunes are user-submitted and attributed to the posting player.

How I handle errors and updates

Errors fall into two categories: game-data drift (e.g. a patch changes a champion's base stats and our database is stale) and math bugs (a formula is wrong or a slider range is off). Both get fixed when reported.

• Game-data updates: Usually within a day of a patch. The script that pulls Data Dragon runs automatically on the LoL side; Forza Horizon 6 car data refreshes when I re-run the import script (manually for now, automation planned).
• Math fixes: Within hours of confirming the bug. When a math fix lands I leave a one-line revision note at the top of the relevant page so people who copied the wrong numbers know to recalculate.
• Content corrections: Wiki-sourced facts (a car's weight, a blueprint's fragment count) are pulled fresh on demand. If the wiki updates and we're showing the stale value, email me and I'll force a refresh.

How the per-entity pages work

Some pages on GamerStation are generated programmatically from data: per-car tune pages, per-blueprint pages, per- champion pages. The tune output, the recipe, the stat table, the calculated grade are all real values computed from real inputs through the math and data sources described above. Prose around them is kept short and factual.

Community Tunes are real player submissions, attributed to the player who posted them, and graded by the same physics model the calculator uses.

How GS Sync works (what it does and doesn't do)

GS Sync is the free desktop companion app for GamerStation. The hotkey opens a small browser window pointed at the right GamerStation tool for whatever game is currently running. It is not a cheat tool and it does not read game memory.

Specifically, GS Sync does the following and only the following:

• Checks the list of currently running Windows processes to see whether a supported game is open (for example, ForzaHorizon6.exe for Forza, the LoL client for League). This uses the same standard Windows API that Discord uses for game-presence detection.
• On a registered hotkey press, opens the matching tool URL on gamerstation.gg in a Chromium-based webview. The URL includes a query flag so the site knows it's being opened by the companion app.
• Signs you in to your GamerStation account inside the webview through a one-time auth code, so any saved presets or supporter perks are available without re-logging.

GS Sync does not call ReadProcessMemory or any equivalent. It does not inject into any game process, hook any anti-cheat surface, parse save files, or read in-game state. Builds, decks, recipes, and tune inputs are entered manually by you on the website.

On Slay the Spire 2 the companion app can populate the GamerStation deck builder with the current run so the deck doesn't have to be re-typed. The companion app does not attach to the running game, hook anti-cheat, or read process memory; it works with what the game itself writes locally.

Report an error

Email gamerstationllc@gmail.com with the page URL and what looks wrong. Include a screenshot if you can. I read every email and reply when I've either fixed the issue or have a question about your report.