How we write guides

Every guide on GamesLink is about a game we made ourselves. That gives us something most guide sites don't have: the game's own source code and design notes. This page explains how that turns into a guide, and where automation is used.

Where the facts come from

A guide starts from the rules the game really runs on. For each game we read its code and design notes for the numbers that matter to a player: how long a run lasts, when bosses and waves arrive, what upgrades cost, how scoring works, and how difficulty ramps from level to level.

If a number appears in a guide, it is the number the game uses. Where a guide gives a figure we calculated rather than read directly, such as a damage-per-second comparison or how many seconds a fuel tank lasts, it is worked out from the game's own values. Anything we couldn't confirm is left out rather than guessed, so you won't find invented statistics, player counts or ratings anywhere on the site.

How the guides are drafted

We use AI writing tools to help draft guides and articles. The tools are given the game's source code and design notes and asked to explain the game for players, with a list of which file each fact came from. That source list is kept with every guide so it can be checked.

Drafts are then checked against the code. When a draft and the game disagreed, the game won. In a few cases this process also found mistakes in our own short game descriptions, and we corrected those too.

Who is responsible

Guides and articles are published under the name of Son Hoang, who made the games and is responsible for what the site says about them. When a game changes in a way that affects the advice, the guide is updated and its date changes.

Spotted a mistake?

If a guide says something that doesn't match what happens in the game, please tell us at contact@gameslink.online with the guide's name and the section. We check it against the game and fix whichever one is wrong.