Keep mutable details dated
Use current announcements and the game client for recipes, costs, resource scaling and quality outcomes. This page intentionally avoids an undated cost table or permanent resource ratio.
Ship crafting is a workflow: identify the current blueprint, gather the required resources, use the relevant shipyard or crafting port and confirm the result in the live build.
| Checkpoint | Current-build guidance |
|---|---|
| Blueprint | Start with the blueprint or recipe shown by the current game and Do not assume a permanent threshold from an older guide. |
| Resources | Check the current resource list and weight or scaling rules before gathering; recent developer notes make those values update-sensitive. |
| Crafting port | Confirm which current port or shipyard context supports the construction step you need. |
| Final validation | Review the completed hull, quality context and current in-game requirements before repeating the workflow. |
Use current announcements and the game client for recipes, costs, resource scaling and quality outcomes. This page intentionally avoids an undated cost table or permanent resource ratio.
For market and production context, read the trading economy guide. For ship vocabulary, use ship rates and classes; for current PvP eligibility, see Ship Rating and PvP Limits.
Naval Action crafting follows a current-build workflow: identify a blueprint or recipe, plan resources, confirm the shipyard or port context, start construction and validate the result.
Official material frames resources as part of construction and notes that blueprints, permits and shipyard requirements may change. Protect the required resources and verify the current interface before committing them.
Choose the intended role, read the current blueprint and resource requirements, confirm the shipyard, start construction and validate the finished ship. No undated cost, ratio or recipe table is reliable enough to freeze here.
Trading Economy owns market advice; Ship Rates and Classes owns terminology; fittings and PvP limits remain separate guides. Review after blueprint, resource, shipyard, port or crafting-rule changes.
Sources: Naval Action official site; official blog. Sources last checked: Sep 1, 2026.
After a ship is built, confirm that the intended blueprint, resources and shipyard result match the current record. If a permit, port rule or material requirement has changed, update the note rather than relying on an old community table. This keeps crafting separate from market speculation and ship-combat theory.
Resource protection is part of the planning decision. Before construction, consider whether the needed materials are safe, whether the current port accepts the blueprint and whether the build result can be checked after completion. Avoid treating a single historical requirement as a permanent recipe.
Use a validation sequence for Naval Action ship crafting. Start with the blueprint or recipe source, then list only the resources the current official material confirms. Check the relevant shipyard or port step next, and validate the result in the present interface before committing more materials. This workflow is more durable than copying an undated cost table or assuming a permanent resource ratio.
Separate the blueprint question from ship rates, classes, combat, trading economy and system requirements. A crafting guide can explain what to verify without claiming that one hull, port, or recipe is universally best. If the official site or blog does not state a cost, threshold, availability condition, or result, mark that field UNKNOWN and keep the claim out of the checklist.
Confirm the blueprint, gather the documented inputs, identify the current shipyard or port, and inspect the final confirmation before crafting. Recheck after an official blueprint, resource, shipyard, port, or crafting-rule change. Treat community recipes as leads for investigation, not authority for a permanent ratio or guaranteed outcome.
Disclosure: this site may earn a commission if you use an approved affiliate link. Editorial opinions are independent. Read the disclosure