Floating City
Name Generator

01

Define what stays above the ground

Decide whether the city rises as one connected structure, several tethered platforms, or a planted mass supported by a single lift system. Crystal engines, living roots, and seasonal winds suggest different limits, but none should simply remove every practical constraint. The invented city of Aerhaven travels slowly along a recognized circuit and descends only to prepared transfer height, never landing directly on ordinary fields.

A generated drift or port ending should connect to that movement. Draw its underside, public decks, workshops, and quiet residential areas. Include ground viewpoints as well as skyline views.

The city name may contain an anchoring valley even while the settlement is elsewhere, preserving a relationship that geography alone cannot show as a fixed dot on a conventional map.

02

Give lift an ordinary operating limit

State one useful limit in plain language: lift weakens beyond a seasonal range, heavy loads require reducing another burden, or the system needs regular work at a particular altitude. Then carry that rule into daily choices without turning the guide into an engineering manual. Aerhaven schedules heavy cargo transfers before adding stored rainwater, so trade and weather affect the same operating plan.

Maintenance crews need safe access to the lift equipment and authority to delay departure. The city name might appear on inspection panels and ground schedules alike. If the system changes, show warning signs residents can recognize rather than waiting for an arbitrary total failure.

Predictable limits make a floating place feel inhabited because people can plan, disagree, and revise plans around them.

03

Trace food, water, and return loads

Deck gardens can provide herbs, greens, and meaningful public space without feeding an entire city automatically. Grain, timber, and replacement cloth come from ground partners. Roof channels collect rain into covered stores, while dry periods increase dependence on transferred water.

Waste and worn equipment must go somewhere, so include agreed return loads, sorting work, and compensation for communities receiving them. A name celebrating clouds should not conceal those material relationships. Show workers weighing cargo, gardeners managing wind exposure, and cooks adjusting meals when a transfer is late.

The city has its own rhythms, yet its apparent freedom depends on people below performing tasks that visitors admiring the skyline might never notice unless the story deliberately follows a load through the whole exchange.

04

Make the anchoring region a relationship

The anchor councils include sky residents and ground communities hosting transfer stations. Their agreement sets approach times, compensation for shaded fields, and the maintenance of cargo paths. A new destination may offer higher prices, but moving the route can disrupt partners who planted crops or built stores for the established circuit.

Do not imply that every prior agreement must last forever. Instead, give changes a notice period and a way to share transition costs. The formal name may retain the original valley title, making a debate about naming also a discussion of obligations.

A city that calls itself anchored can mean more than a chain tied to stone; it can acknowledge promises that continue while its decks travel beyond the horizon of the households that helped sustain them.

05

Follow the soil on the returning chain

An anchor chain returns with dark soil unlike anything at the mapped transfer station. A neglected lower shelf beneath cloud has become a productive settlement, and the city has been using an older chart that overlooks its gardens. Begin with a ground market waiting below while the sky council prepares to depart for a lucrative new route.

Characters can accompany a supply basket, meet the shelf's growers, and compare the chain's contact marks with the current transfer plan. The immediate objective is avoiding another damaging approach and completing a promised food exchange. The discovery should expand recognition of existing people, not create a claim to newly found land.

A revised circuit can include the shelf if residents want participation and the city accepts the cost of safer, better informed transfers.

06

Name movement without promising escape

Try the generated title on a ground delivery, a deck school's map, and a departure song. Let the public short form travel easily, while the official version records an anchoring relationship that matters to residents. Give major decks and transfer stations distinct names so characters can discuss routes clearly.

Describe a quiet evening with gardens secured against wind, water levels checked, and lights visible far below. The city can be wondrous without functioning as an escape from every responsibility attached to a settlement. Its name becomes richer when movement changes relationships rather than erasing them.

End with one agreement the next departure must honor, showing that a place carried through the sky still exists within a network of work, care, and promises shared with people who remain on the ground.

07

Revision case: Aerwick and crop notice

Draft setup for Aerwick at the anchor councils: Published approach windows let ground growers protect beds, move equipment, and prepare shared cargo paths before the city arrives. This example uses “Aerwick, Fieldanchor” as the proposed public introduction. Failed crop notice version: Aerwick receives “Fieldanchor” before anybody addresses this obstacle: An outdated chart omits a productive shelf whose gardens lie where the next anchor contact is planned.

For Aerwick, the apparent achievement therefore exceeds the evidence. In crop notice, the draft assumes the named destination is already accessible. Revised crop notice scene: Sky crews accept delays and compensate disrupted work instead of treating every field beneath the route as empty clearance.

Keep Aerwick's introduction provisional while that cost is paid. The crop notice evidence arrives through an observable detail: Dark soil on the returning chain contains fresh garden roots unlike the bare station ground shown in the city atlas. Give the destination a working connection and name the person responsible for maintaining it.

Introduction before revision: “Aerwick, Fieldanchor” is announced as settled. After revision: “Aerwick” is used pending the crop notice evidence; “Fieldanchor” records only the accepted result. In this floating city scene, “Starfloat” takes the other speaking role.

The ending for Aerwick must still acknowledge the local conflict: A new route improves trade while separating the city from the ground communities that supply its food. With crop notice, a limited agreement leaves space for disagreement without making “Fieldanchor” meaningless.

08

Revision case: Cloudel and return loads

Draft setup for Cloudel at the anchor councils: Agreed sorting and return services keep worn equipment and unwanted materials connected to responsible ground processing. This example uses “Cloudel, Roundhaven” as the proposed public introduction. Failed return loads version: Cloudel receives “Roundhaven” before anybody addresses this obstacle: A faster commercial circuit bypasses the station contracted to receive materials already accumulating beneath the service deck.

For Cloudel, the apparent achievement therefore exceeds the evidence. In return loads, the draft assumes the named destination is already accessible. Revised return loads scene: The city reserves cargo capacity and pays receiving workers rather than using every downward journey only for new purchases.

Keep Cloudel's introduction provisional while that cost is paid. The return loads evidence arrives through an observable detail: Labeled return bundles name a partner absent from the proposed itinerary despite an unexpired service agreement. Give the destination a working connection and name the person responsible for maintaining it.

Introduction before revision: “Cloudel, Roundhaven” is announced as settled. After revision: “Cloudel” is used pending the return loads evidence; “Roundhaven” records only the accepted result. In this floating city scene, “Starfloat” takes the other speaking role.

The ending for Cloudel must still acknowledge the local conflict: A new route improves trade while separating the city from the ground communities that supply its food. With return loads, a limited agreement leaves space for disagreement without making “Roundhaven” meaningless.

09

Revision case: Driftwick and route transition

Draft setup for Driftwick at the anchor councils: Notice and shared adjustment funds help former supply partners adapt when the moving city's commercial circuit changes. This example uses “Driftwick, Bondrift” as the proposed public introduction. Failed route transition version: Driftwick receives “Bondrift” before anybody addresses this obstacle: The sky council celebrates higher prices while overlooking relatives and growers losing their only regular transfer connection.

For Driftwick, the apparent achievement therefore exceeds the evidence. In route transition, the draft assumes the named destination is already accessible. Revised route transition scene: New trade profits support households that planted crops or built stores specifically for the established arrival schedule.

Keep Driftwick's introduction provisional while that cost is paid. The route transition evidence arrives through an observable detail: Ground stores are full of requested grain even as the departure board announces that their station will be skipped. Give the destination a working connection and name the person responsible for maintaining it.

Introduction before revision: “Driftwick, Bondrift” is announced as settled. After revision: “Driftwick” is used pending the route transition evidence; “Bondrift” records only the accepted result. In this floating city scene, “Starfloat” takes the other speaking role.

The ending for Driftwick must still acknowledge the local conflict: A new route improves trade while separating the city from the ground communities that supply its food. With route transition, a limited agreement leaves space for disagreement without making “Bondrift” meaningless.