Silent Shark Wiki Tools

The Tools Hub collects quick-reference pages that complement long-form Guides and Systems articles. Silent Shark rewards repetition: the same pre-fire checklist before every convoy attack prevents the classic failure modes — firing with a stale range, forgetting tube flooding, or diving noisy through a thermal layer while escorts still have a bearing.

These tools are written for the free demo and the August 12, 2026 full release alike. Mechanics in the attack loop are shared; the full game adds campaign constraints on torpedo inventory and patrol routing that the checklist calls out where relevant.

Available tools

• Attack Checklist — Phase-by-phase ticks from first hydrophone contact through egress depth, designed to print or keep on a second monitor.
• Demo vs Full Game — Feature matrix, platform support, and what you can practice now versus what waits for 1.0.
• Scenario Generator — Repeatable Demo drills for AoB, escorts, weather, and end-to-end sortie practice.

Neither page replaces tutorials. Run Getting Started once, then use the checklist until the sequence feels automatic.

When to use each tool

Situation	Tool
First week with the game	Attack Checklist every sortie
Deciding to wishlist	Demo vs Full
Returning after a patch	Checklist + Launch Notes
Teaching a friend	Checklist + Stations guide

Related hubs

• Guides Hub — Deep explanations for every checklist line.
• Systems Hub — Instrument detail behind each tick box.
• Campaign Hub — Resource limits that modify checklist priorities in career mode.
• Review Hub — Broader overview if you are new to tactical sub sims.

Offline and second-monitor use

The attack checklist is structured with markdown headings so browser print-to-PDF works cleanly. If you stream or record, blur personal notes — the checklist itself contains no spoilers for campaign events.

We will expand this hub if community tools (scenario sharing, log sheets) become common after launch. Until then, these two references cover the highest-traffic player needs identified in demo feedback and Steam discussion threads.

How tools relate to guides

Guides teach why each step exists; tools compress what to verify. Read Getting Started once, then live on Attack Checklist until muscle memory forms. Return to guides when a tick repeatedly fails — usually Four Bearings or Stadimeter Range.

Pre-launch workflow

Before August 12, 2026, recommended tool usage:

1. Week 1 — checklist every demo tutorial step.
2. Week 2 — checklist on generator convoys; read Demo vs Full before wishlist decision.
3. Launch week — checklist plus Launch Notes for save and feature expectations.

Print and PDF tips

Browser print → “Save as PDF” → tablet beside keyboard works well for ultrawide players who lack second monitor. Scale to 100%; smaller text defeats the purpose under stress.

Future tools (post-launch)

Possible additions if community requests them: patrol log spreadsheet templates, scenario seed sharing etiquette, campaign decision flowcharts for Patrol Radio prioritization. None required to enjoy the game — the attack checklist remains the highest ROI reference.

Make tools part of every sortie

Before a hard scenario, open the attack checklist and literally tick the mental boxes. After a miss, use the same checklist to find which step you skipped. When you are deciding whether to buy at launch, read Demo versus full game once, then stop comparing and go practice — the Demo already contains the targeting skill ceiling that matters most.

Tools and the rest of the wiki

Tools do not replace Guides or Systems. They compress them into actionable lists and comparisons. Bookmark this hub beside Controls so keybinds and checklists stay one click apart during training sessions.

Suggested weekly practice

Monday: Basic Tutorial refresh. Wednesday: checklist-only convoy. Friday: compare your notes to TDC systems. That rhythm beats random scenario hopping.