Contact

Reader Corrections

Grand strategy guides age quickly. Patches change values, DLC can move mechanics, and a console command that worked in one version may behave differently after the next update. If you are reporting a correction, the most useful note includes the page URL, the exact sentence or table row that looks wrong, the game version or patch number, and what you saw in game.

Corrections are prioritized when they affect campaign decisions: broken commands, wrong IDs, outdated opening moves, changed DLC requirements, missing prerequisites, or advice that could make a player lose time in a first campaign. Style suggestions are welcome too, but accuracy fixes come first.

If a guide has several possible interpretations, include the context that changed the result. For example, mention the active DLC, ruleset, difficulty, country, empire type, focus path, start date, or console state. A short reproduction note is often enough to separate a real outdated guide from a mechanic that depends on setup.

Reports do not need to be long. A useful correction can be as simple as “the command on this row no longer works in version X” or “this building unlock now requires a different technology.” Clear evidence is more helpful than a polished message, and small verified fixes are easier to ship than broad complaints without a test case.

Guide Requests

Guide requests work best when they describe a specific player problem. Instead of only asking for a broad topic like economy or warfare, include the game, the country or empire type if relevant, the point in the campaign, and the decision that feels unclear. Examples include a Germany opening in Hearts of Iron IV, a first EU5 market problem, or a Stellaris build that falls behind after the early game.

Strong requests usually include one of three things: a decision that needs a recommendation, a mechanic that needs a plain-English explanation, or a reference table that would save time. A request for “best divisions for 1939 infantry defense” is easier to turn into a useful HoI4 article than a request for “more war guides” because the scope is testable and the reader outcome is clear.

If a request is about a new article, include what the finished guide should help a reader do. That might be surviving the first fifty years, choosing a DLC during a sale, fixing a broken console command, planning an industry build, or understanding why an economy falls behind. A clear outcome makes the guide easier to outline and verify.

Reference Corrections

If a guide links to an official wiki, developer diary, patch note, store page, or in-game term and the reference no longer matches the current mechanic, report the public page URL, the external target, and the game version where the mismatch appears.

Reference notes are handled like corrections: they should point to something a reader can verify, such as a broken link, a changed patch note, a renamed mechanic, or a table row that no longer matches the live game.

Keep Reports Safe and Useful

Send only details that can be checked from a public page or from the game itself: the article URL, game and version, the visible issue, and what should change. Do not include passwords, account credentials, API keys or tokens, payment details, private save files, server or admin details, or unrelated personal information.

The feedback bot is for public site maintenance: guide corrections, page bugs, source fixes, and topic suggestions. Reports that miss the page URL, game version, or reproduction detail may need follow-up before they can be fixed; account, payment, server-admin, and private-data support is outside this channel.