Naval Action Player Guide
The problem with most Naval Action guides and wikis is that they are dependent on human beings to stay current, which means that they are rarely current.
At Naval Gaming, we have created this project to solve the problem by using AI to maintain a comprehensive player guide that is updated with the push of a button.
Explanations are written from credited sources and re-checked against every game patch. Live figures — ship stats, ports, prices — are pulled straight from the game data feed. We lead with the Peace server. Use the menu on the left to choose a topic.
Standing on the shoulders of the community
This Guide does not invent the game — it synthesizes the hard-won knowledge of the captains and developers who documented Naval Action long before us, and we are grateful to every one of them. The prose here is original, but the facts are theirs, and they deserve the credit:
- Aquillas (Eléazar de Damas) — whose 120-page Naval Action User Guide (now in its 13th revision) is the most thorough single document ever written about this game. It is the structural backbone of our coverage: if a topic matters, Aquillas almost certainly mapped it first.
- The Naval Action Wiki — the collaborative reference maintained by countless anonymous editors, our cross-check for names, tables, and the small details that are easy to get wrong.
- FearAndLoathing — author of Fear’s Comprehensive Guide on Steam, a generous and widely-read introduction that has oriented a generation of new captains.
- Prezeey — author of the 2026 New & Returning Player Comprehensive Guide on Steam, a current post-relaunch primer that helps us keep new-captain guidance in step with today’s game.
- felixvictor — creator of na-map, the community mapping and ship-comparison tool whose methodology helps us read the raw game data the same way the veterans do.
- The Naval Action developers — originally Game Labs, who built the game, and today the Bermuda Computer Club that maintains it and continues its development. Their patch notes and developer announcements are the final word on what the game actually does today.
How we stay current with the patch notes
The reason most guides fall out of date is simple: Naval Action keeps changing, and people stop editing. We close that gap mechanically. Whenever a patch lands, we pull the official developer announcements straight from Steam — fetched live through Valve’s ISteamNews API, the same patch feed the developers publish to — and re-check every page the change touches against it. A balance pass that re-tunes repairs, boarding, or cannon ranges shows up in our reading list the moment it is posted, so the pages here track the latest state of the game rather than the state it was in whenever someone last had time to write about it. When the patch feed and an older source disagree, the patch feed wins.
For the full method — how sources are weighted, how live numbers are wired in, and why the prose is always our own — see How this Guide is made.