Storm Dragon
Name Generator

01

A name granted after the season

Choose the people who recognize the title and the observations they use. Sailors may honor a dragon for leaving one harbor approach clear during autumn departures; farmers may remember rain arriving after a delayed planting. These groups need not agree that the same action was beneficial.

A title such as Third Bell Thunder can recall a warning delivered early enough for crews to secure a fleet. Explain the bell schedule and the season in which it mattered. The creature's personal name should remain distinct from this assessment, allowing other ports to address it without endorsing an agreement they never helped negotiate or had any chance to reject.

02

Thunder as advance notice

Thunder is useful when the name describes communication rather than raw loudness. Decide whether the dragon can place a warning rumble ahead of dangerous weather, and distinguish that signal from an ordinary storm. Repeated timing or a recognizable sequence helps witnesses interpret it fairly.

The signal must have a range; distant communities cannot react to a sound they never hear. A thunder epithet can therefore carry an obligation to maintain alternate warnings through flags or messengers. This creates meaningful work for human partners and prevents a spectacular voice from replacing every local system.

Consider people who cannot hear the signal and design an equally reliable visible indication.

03

Fog changes whose map works

Fog names can refer to a passage opened, a boundary concealed, or a sheltered rest period. Avoid assuming concealment is inherently deceptive. A fishing crew may need fog to cool shallow nursery waters, while another crew needs clear visibility to return home.

Define how long the dragon can maintain the mist and whether it moves with the wind. An epithet involving a lamp or buoy is more specific than a general claim to mystery. A title such as Lantern Gap records the maintained opening through which boats navigate.

Once a new harbor wall changes airflow, keeping that opening usable can become a political and practical problem the creature cannot solve by reputation alone.

04

High wind has a destination

Wind redirected away from one town must go somewhere in a consistent setting. Give the dragon a clear capacity: it can bend a gust over a ridge, reduce its peak for a short interval, or warn of a pressure change. Publish that capacity beside the seasonal bargain so distant communities receive the same qualified description as nearby negotiators.

Choose one before designing the name. A wind title may commemorate guiding seed-bearing air toward a damaged hillside, yet later residents may object to the same seasonal pattern filling their streets with dust. Treat these complaints as evidence about changed circumstances rather than ingratitude.

The name can remain historically accurate while its old achievement no longer serves everyone living under the route of that particular current of moving air.

05

The rain allocation hearing

For a grounded case, two valleys need the same approaching rain front. One risks crop failure; the other has recently settled a floodplain that cannot absorb a sudden downpour. The dragon has promised rainfall to the first community, but the original bargain predates construction downstream.

Let barometers, stream levels, and planting records make the problem understandable. Nobody needs a perfect forecast. The difficult decision concerns how to distribute uncertainty, warn residents, and share the work of preparing drainage.

A weather title earned in an earlier season can become the focus of the hearing, with different witnesses interpreting what the dragon actually promised to deliver.

06

Keep a record of the miss

Finish the name by giving it a history that includes an imperfect forecast. Perhaps the dragon warned correctly about wind but overlooked a flooded road that delayed evacuation. Admitting that omission does not make its weather knowledge worthless.

It makes the agreement capable of revision. Test the result in a sailor's grateful account, a grower's complaint, and the creature's own explanation of its limits. A successful storm name carries both spectacle and accountability: readers can picture the sky changing, understand who benefits, and identify a practical task for characters on the ground.

The dragon remains extraordinary while the story still needs neighbors who measure, maintain, argue, and choose.

07

Revision case: Temvarax and cross-station calibration

Draft setup for Temvarax at the stormward compact: Compare pressure readings against elevation records before deciding whether the approaching front has changed course. This example uses “Temvarax, Samelevel” as the proposed public introduction. Failed cross-station calibration version: Temvarax receives “Samelevel” before anybody addresses this obstacle: A repaired gauge uses a copied scale that makes one valley appear consistently more threatened.

For Temvarax, the apparent achievement therefore exceeds the evidence. In cross-station calibration, the draft treats recognition as permission to approach or command. Revised cross-station calibration scene: Technicians must visit an exposed station and temporarily suspend its usual public forecast board.

Keep Temvarax's introduction provisional while that cost is paid. The cross-station calibration evidence arrives through an observable detail: Its maintenance note lists the harbor station's reference height instead of the ridge station's actual elevation. Keep the observer outside the recorded boundary for Temvarax; distinguish a response from an agreement.

Introduction before revision: “Temvarax, Samelevel” is announced as settled. After revision: “Temvarax” is used pending the cross-station calibration evidence; “Samelevel” records only the accepted result. In this storm dragon scene, “Galvaryn” takes the other speaking role.

The ending for Temvarax must still acknowledge the local conflict: A promised rainfall would save one valley while flooding a settlement downstream. With cross-station calibration, a limited agreement leaves space for disagreement without making “Samelevel” meaningless.

08

Revision case: Aerakor and affected basin hearing

Draft setup for Aerakor at the stormward compact: Include all three basins in a rainfall decision before using the dragon's available delaying interval. This example uses “Aerakor, Downstream” as the proposed public introduction. Failed affected basin hearing version: Aerakor receives “Downstream” before anybody addresses this obstacle: One community wants the rain moved beyond the map used by the current negotiating council.

For Aerakor, the apparent achievement therefore exceeds the evidence. In affected basin hearing, the draft treats recognition as permission to approach or command. Revised affected basin hearing scene: The hearing consumes time that could otherwise extend preparations in the most vocal valley.

Keep Aerakor's introduction provisional while that cost is paid. The affected basin hearing evidence arrives through an observable detail: An irrigation ledger lists a downstream settlement absent from the council's celebrated weather compact. Keep the observer outside the recorded boundary for Aerakor; distinguish a response from an agreement.

Introduction before revision: “Aerakor, Downstream” is announced as settled. After revision: “Aerakor” is used pending the affected basin hearing evidence; “Downstream” records only the accepted result. In this storm dragon scene, “Galvaryn” takes the other speaking role.

The ending for Aerakor must still acknowledge the local conflict: A promised rainfall would save one valley while flooding a settlement downstream. With affected basin hearing, a limited agreement leaves space for disagreement without making “Downstream” meaningless.

09

Revision case: Ravelion and public forecast review

Draft setup for Ravelion at the stormward compact: Separate an accurate weather prediction from failures in the warning and evacuation procedures that followed. This example uses “Ravelion, Afterfront” as the proposed public introduction. Failed public forecast review version: Ravelion receives “Afterfront” before anybody addresses this obstacle: A correct wind warning is being used to dismiss residents whose only escape road flooded first.

For Ravelion, the apparent achievement therefore exceeds the evidence. In public forecast review, the draft treats recognition as permission to approach or command. Revised public forecast review scene: Officials and dragon must document mistakes openly before requesting another season's ceremonial endorsement.

Keep Ravelion's introduction provisional while that cost is paid. The public forecast review evidence arrives through an observable detail: The road crew's closure time predates the bell station's notice that everyone should begin leaving. Keep the observer outside the recorded boundary for Ravelion; distinguish a response from an agreement.

Introduction before revision: “Ravelion, Afterfront” is announced as settled. After revision: “Ravelion” is used pending the public forecast review evidence; “Afterfront” records only the accepted result. In this storm dragon scene, “Galvaryn” takes the other speaking role.

The ending for Ravelion must still acknowledge the local conflict: A promised rainfall would save one valley while flooding a settlement downstream. With public forecast review, a limited agreement leaves space for disagreement without making “Afterfront” meaningless.