Rules edition: The character examples here use the 2014 Player’s Handbook Gnome and Wizard rules. These are Dungeon Master ideas for including a Gnome Wizard in a war campaign, not a new combat subsystem. For player-facing spell and build choices, see our Gnome Wizard war-scenario guide; for investigation-focused play, see our Rock Gnome investigation guide.
A Gnome Wizard can be a useful lens on a war story, but the character should remain one member of the party rather than its automatic strategist or protagonist. Give the player situations where preparation and magical knowledge matter, then make room for the rest of the group to shape what happens. A war campaign feels more convincing when its dangers and decisions affect the whole party.
Agree on the war story before play
Before putting atrocities, civilian danger, captivity, or political coercion into the campaign, ask the group what subjects they want to include or avoid. Clarify whether the table wants tactical battles, espionage, travel, political negotiation, or a mix. This is especially important when the campaign places player characters near civilian casualties or forces them to choose between military orders and personal values.
Decide how the campaign handles scale. The standard combat rules resolve individual characters and creatures; they do not automatically determine the movement or morale of a whole army. If you want mass battles, use a published subsystem your table has chosen or agree on a simple, transparent method before the outcome is at stake. Do not treat an improvised “morale check” as a normal ability check that a Wizard’s Portent can automatically replace.
Make the Gnome’s features matter without making them a solution
Under the 2014 rules, every Gnome has advantage on Intelligence, Wisdom, and Charisma saving throws against magic. That can matter when an enemy magical effect calls for one of those saves, but it is not broad resistance to magic damage or protection from weapon attacks. Describe what a magical threat does, call for the correct save, and let the feature apply only when its wording fits.
A Forest Gnome’s minor illusion can support a plan with a small image or sound, within the cantrip’s range and duration. It does not create moving troops or a damaging diversion. A Rock Gnome’s Tinker feature makes particular small clockwork devices; it does not grant an automatic battlefield gadget or a bonus to siegecraft. Invite creative proposals, then use the spell, feature, check, or tool rules that actually apply.
Build encounters with more than one useful role
Give the party choices about reconnaissance, evacuation, fortification, negotiation, and supply lines—not just opportunities to cast the largest area spell. A Wizard might identify a magical barrier while another character finds a safe route, persuades a local guide, or protects civilians. Let different skills and character histories reveal different parts of the situation, so one spell list cannot bypass every scene.
Vary encounter goals. A battle could be about holding a bridge long enough for people to escape, capturing a courier, disrupting a ritual, or retreating with evidence. State the objective and relevant constraints clearly. These goals let control and utility spells shine without requiring every scene to end when one side reaches zero hit points.
Keep 2014 Wizard features and spells inside their rules
A 2014 Wizard chooses an Arcane Tradition at level 2. For example, an Evoker’s Sculpt Spells can protect selected creatures from certain Evocation spells under the feature’s conditions. A Diviner’s Portent can replace a visible creature’s attack roll, saving throw, or ability check with a stored d20 result; it does not make an entire plan succeed or alter a check the game has not called for. An Abjurer’s Arcane Ward is a pool of hit points, not temporary hit points, and it does not make the Wizard safe to place on the front line.
Read the full spell description before deciding what an action accomplishes. Range, sight, targets, components, duration, and concentration can all matter in a battlefield scene. A divination spell may reveal only the information its text promises; an illusion may be recognized or investigated; and a concentration spell can end when its caster loses concentration. Explain consequences consistently, whether the spell is cast by a player character or an enemy.
Give military decisions consequences, not predetermined answers
War stories can ask hard questions without declaring that there is only one virtuous choice. A Gnome Wizard might question an order, seek a prisoner exchange, protect civilians, or argue that a risky magical weapon will cause harm long after a battle ends. Let these choices change relationships, resources, or future opportunities in understandable ways; avoid making the character’s Intelligence or alignment decide the answer for the player.
After a major mission, show what changed. The party might learn that a supply route is open, that a local leader no longer trusts the army, or that an enemy spellcaster has adapted to their tactics. Such consequences make preparation meaningful while leaving the players free to revise their plans. Keep victories and failures proportional to what the party actually did and the rules actually resolved.
