This guide focuses on story and table choices for an Air Genasi Cleric. It does not assume a D&D rules edition or prescribe character mechanics. For a sourced build using the revised Air Genasi with the 2014 Cleric, see Air Genasi Cleric Build Guide (2014 Cleric + MotM Species).
An Air Genasi Cleric brings two parts of a character’s life into the same story: an elemental heritage and a chosen relationship to a faith, deity, community, or cause. Those parts can reinforce each other, compete, or stay mostly separate. Let the player decide which relationship matters and how it changes over time.
Start with the character’s own beliefs
Ask what drew the character to their calling. Was it a promise, a person they hoped to help, a practice they found meaningful, or a question they cannot leave unanswered? The answer does not need to come from their ancestry. An Air Genasi can serve a sea god, follow a local tradition, question organized religion, or have a faith that is private and practical.
Give the player room to define what elemental heritage means to this character. It might shape family history, a community’s traditions, or the way the character describes themselves. It does not require a restless temperament, a love of freedom, a connection to a particular plane, or a conflict with religious service. A character can share any of those traits, but the ancestry alone should not decide them.
Build hooks with the player
A useful campaign hook gives the character a choice and lets the player decide how to respond. Before adding an elemental relative, a temple dispute, or a prophecy, ask whether that subject interests the player. Offer more than one possible connection and leave room for the character to decline, reinterpret, or redirect it.
- A family question: Someone arrives with a story about the character’s ancestry. The player can decide whether to investigate, set a boundary, or ignore it.
- A community request: A congregation or neighborhood asks the character for help. The character can choose what obligation, if any, they accept.
- A difference of practice: Two groups interpret the same teaching in different ways. Let the character listen, mediate, challenge either side, or decide the dispute is not theirs to solve.
- A place that remembers: A local shrine, storm observatory, or travel route holds meaning for the character. Invite the player to decide what happened there and whether they want it to return in the story.
Keep hooks connected to the wider party. A personal scene can reveal a choice or relationship without turning every session into a test of one character’s identity. Let other characters contribute, and share the spotlight across different goals and relationships.
Let relationships change in more than one direction
A mentor, congregation, family member, or local leader does not need to be an obstacle or a source of approval. They can disagree about one decision and still care for the character. They can misunderstand the character, learn something, or have their own goals that do not revolve around the player character. These relationships feel more lived-in when both sides can change.
For example, a temple might need the character’s help during a crisis while also asking them to respect a tradition they question. A relative might share a family story but not know what the character should do with it. A village might ask the Cleric to mediate a dispute without treating their faith as a magical answer to every problem. Each setup leaves the player room to decide what the character values and how they act.
Use short scenes to give those choices space: a conversation after a difficult service, a message the character can answer or set aside, or a quiet moment before the group travels on. Not every hook needs to become a quest. Some details can deepen the character’s world and then rest until the player wants to return to them.
Make faith specific without making it compulsory
“Cleric” can mean different things in different settings. One character may belong to a temple with a clear hierarchy; another may serve a community without formal membership; a third may understand their powers through a personal vow. Ask the player which parts they want in the story. Avoid treating religious service as automatic obedience or making the DM the final authority on what the character believes.
If a deity or organization gives the character a request, make its stakes clear and leave the response open. The character might accept, negotiate, refuse, or look for another way to help. Consequences can follow from choices, but they should arise from the situation rather than from a rule that the character must be punished for questioning authority.
Use elemental imagery as an invitation
Wind, open spaces, changing weather, distant voices, and motion can add texture to a scene. Treat them as prompts the player can use or ignore. A breeze might stir a character’s clothing at a tense moment, or it might mean nothing at all. Ask before using ancestry as a reason for an involuntary mood, a loss of control, or a forced reveal.
Let the character’s appearance and habits come from the player. Some Air Genasi might have a faint breeze, unusual skin or hair, or a voice with a soft echo; others may present differently. A stranger’s reaction can create a roleplaying opening, but it should not make the character responsible for educating every NPC or force the player into a fixed outsider story.
Share control of difficult scenes
Stories about faith, family, discrimination, grief, and belonging can matter deeply. Before using those themes, check what the player wants at the table and how much detail they are comfortable exploring. Give them ways to pause, change direction, or keep a scene offscreen. The character’s heritage can create opportunities for connection as well as tension; the story does not need to rely on prejudice or rejection.
For practical mechanics and a clear version boundary, use the Air Genasi Cleric build guide. Keeping character mechanics in that guide lets this one stay focused on player choice, campaign hooks, and relationships.
