Battles Should Look and Feel Like Battles

 

Dragon Age: Battles Should Look and Feel Like Battles

One thing Dragon Age needs to bring back and expand is the feeling that the world is actually at war, unstable, and dangerous.

Not every fight should feel like a small group of enemies waiting in a hallway. Some encounters should feel like real battles: soldiers clashing, mages changing the battlefield, arrows flying overhead, creatures breaking through lines, civilians running, commanders shouting, siege weapons firing, and factions fighting for territory.

A battle in Dragon Age should not just be “the player party versus ten enemies.” It should feel like the player has stepped into a living conflict.


1. Large-Scale Battles Should Have Layers

A real battle should have multiple moving parts happening at once.

You could have:

  • Frontline warriors holding shields and formations
  • Archers firing from rooftops, hills, or broken walls
  • Mages protecting troops or destroying enemy lines
  • Rogues sneaking behind the battle to sabotage supplies
  • Cavalry, mabari, war hounds, or beasts charging through gaps
  • Darkspawn emerging from tunnels or flanking routes
  • Civilians trapped in the chaos
  • Commanders giving orders from protected positions
  • Healers and support mages trying to keep soldiers alive

The player should feel like the battle is bigger than them, but their actions can still shift the outcome.

That is the balance Dragon Age needs.

The player is important, but the world should not feel frozen until they arrive.


2. Battles Should Have Objectives, Not Just Enemy Waves

Too many RPG battles become repetitive because the only goal is to kill everything.

Dragon Age battles should have battlefield objectives.

For example:

Hold the Gate

Enemies are trying to break through a city gate. The player must help soldiers hold the line while engineers repair the mechanism.

Protect the Mages

A group of mages is casting a massive barrier spell. The player must defend them until the spell is complete.

Destroy the Siege Engine

The enemy has a ballista, trebuchet, magical cannon, or darkspawn machine destroying defenses. The player must reach it and disable it.

Rescue the Wounded

A healing camp is being overrun. The player can save soldiers, civilians, or important NPCs.

Kill the Commander

The enemy army is coordinated by a powerful commander. Taking them out causes enemy morale to collapse.

Stop the Ritual

Blood mages, Venatori, darkspawn emissaries, or demons are using the battle as cover for a ritual.

This makes battles feel like missions inside a war, not just arena fights.


3. Battlefields Should Change During Combat

A battlefield should not stay the same from start to finish.

Things should happen dynamically.

A bridge collapses.
A wall breaks.
A dragon lands.
A demon appears.
A mage shield fails.
Darkspawn burst from the ground.
A fire spreads through tents.
A commander orders a retreat.
Reinforcements arrive late.
A faction betrays another faction mid-battle.

The battle should evolve.

This would make the player feel like they are inside a real Dragon Age event instead of a scripted enemy room.


4. Factions Should Fight Differently

Every faction should have its own battlefield identity.

Darkspawn Battles

Darkspawn should feel overwhelming. They should swarm, dig, ambush, poison, corrupt, and throw bodies at the enemy. They should not fight clean. Their battles should feel ugly, desperate, and terrifying.

Qunari Battles

Qunari should feel disciplined. Heavy infantry, shield lines, powerful Saarebas, explosive weapons, controlled formations, and brutal efficiency.

Orlesian Battles

Orlesian battles should be theatrical but deadly. Fancy armor, chevaliers, duelists, assassins, banners, horns, and political betrayal in the middle of combat.

Fereldan Battles

Ferelden should feel gritty and grounded. Mabari, muddy fields, hardened soldiers, strong shield walls, and survival-based warfare.

Tevinter Battles

Tevinter should feel magical and oppressive. Slave soldiers, blood magic, arcane artillery, summoned demons, floating barriers, and elite magisters controlling the field.

Dalish Battles

Dalish battles should feel mobile and tactical. Ambushes, archers, traps, nature magic, hit-and-run attacks, and terrain advantage.

Dwarven Battles

Dwarven battles should feel heavy, industrial, and disciplined. Shield walls, golems, crossbows, traps, explosives, armor formations, and underground chokepoints.

This gives each faction personality beyond their dialogue.

You should know who you are fighting just by how the battle feels.


5. Companions Should React to the Battle

Companions should not be silent during major battles.

They should shout warnings, call out enemy movements, react to danger, and argue about decisions.

Examples:

Warrior companion:
“Shield line is breaking! We either hold it now or lose the gate!”

Mage companion:
“That barrier will not last! Those mages need time!”

Rogue companion:
“Archers on the ridge. Give me a path and I can clear them.”

Dwarf companion:
“That tunnel is wrong. Darkspawn are coming from below!”

Qunari companion:
“They are not retreating. They are reforming.”

This makes companions feel like battlefield allies, not just party members following the player.


6. Command Decisions Should Matter

The player should sometimes make command decisions before or during battles.

For example:

  • Send soldiers to defend the village or protect the bridge
  • Use mages for healing or offense
  • Ask archers to cover civilians or target enemy commanders
  • Save the noble commander or rescue common soldiers
  • Burn the crops to stop the enemy advance
  • Collapse a tunnel even if allies are still inside
  • Let one faction take heavy losses to preserve another

These choices should affect the world afterward.

A village may survive.
A faction may respect you.
A companion may disapprove.
A commander may die.
A future questline may change.
A settlement may become weaker or stronger.

Dragon Age is at its best when choices leave scars.

Battles should do the same.


7. Small Battles Should Still Feel Tactical

Not every fight needs to be massive. Smaller battles can still feel like battles if they have purpose.

A roadside ambush should involve positioning.
A village defense should involve barricades.
A cave fight should involve chokepoints.
A forest battle should involve traps and visibility.
A fortress fight should involve verticality and reinforcements.

Even a fight against ten enemies can feel better if the enemies behave like they have a plan.

Bandits should retreat, flank, throw smoke, target mages, or try to steal supplies.
Darkspawn should swarm and corrupt the area.
Templars should focus mages.
Assassins should target weak party members.
Demons should exploit fear and confusion.

The goal is not just “more enemies.”

The goal is smarter, more believable encounters.


8. Sieges Should Return in a Bigger Way

Dragon Age needs proper sieges.

Imagine:

  • Defending a fortress from darkspawn
  • Breaking into a Tevinter slave citadel
  • Holding a dwarven thaig against waves of creatures
  • Attacking a Qunari war camp
  • Protecting a city from demons
  • Fighting through an Orlesian civil war battlefield
  • Reclaiming a village from bandits and corrupted mages

Sieges should have stages.

Stage One: Preparation

You choose defenses, allies, traps, supplies, and battle plans.

Stage Two: First Assault

The enemy tests your defenses.

Stage Three: Breach

Walls fall, gates break, or tunnels open.

Stage Four: Inner Battle

The fight moves into courtyards, streets, halls, or throne rooms.

Stage Five: Final Decision

Kill the commander, negotiate surrender, sacrifice a section of the city, or retreat.

That would make battles feel meaningful and memorable.


9. Magic Should Change the Battlefield

Magic in Dragon Age should not just be damage numbers.

Powerful magic should affect the entire battle.

Mages could:

  • Raise barriers over soldiers
  • Freeze bridges or choke points
  • Set fire to siege towers
  • Collapse stone walls
  • Summon storms
  • Heal groups of soldiers
  • Cleanse corruption
  • Dispel enemy rituals
  • Open temporary Fade rifts
  • Create illusions to confuse enemy troops
  • Turn terrain into danger zones

Enemy mages should do the same.

A Tevinter magister should feel terrifying on a battlefield.
A blood mage should turn panic into a weapon.
A Saarebas should feel like walking artillery.
A demon should twist the battlefield into a nightmare.

Magic should make Dragon Age battles feel like Dragon Age battles.


10. The Aftermath Should Matter

A battle should not end with loot and silence.

Afterward, the player should see consequences.

  • Bodies on the field
  • Wounded soldiers being treated
  • Survivors searching for family
  • Commanders arguing over losses
  • Prisoners being questioned
  • Companions reacting emotionally
  • Villagers thanking or blaming you
  • Merchants reopening or fleeing
  • Factions changing their opinion
  • New graves appearing
  • Areas becoming safer or more dangerous

The aftermath is what gives the battle weight.

Without aftermath, battles feel like gameplay events.
With aftermath, they feel like history.


11. Battles Should Build Reputation

The player’s battlefield decisions should create a reputation.

NPCs should talk about it.

“They held the gate at Red Crossing.”
“They abandoned the left flank.”
“They saved the mages but lost the village.”
“They broke the darkspawn charge.”
“They let the chevaliers die.”
“They ended the siege without burning the city.”

That makes the player’s story feel like it belongs in the world.

Dragon Age should make you feel like your choices become rumors, songs, fear, respect, and political consequences.


12. The Best Dragon Age Battles Should Be Remembered

The franchise needs battles people talk about years later.

Not because they were just big, but because they had emotion, stakes, choices, and consequences.

A great Dragon Age battle should make the player remember:

  • Who died
  • Who betrayed them
  • What choice they made
  • What they sacrificed
  • What faction changed because of it
  • What companion never looked at them the same way again

That is what makes a battle more than combat.

That makes it storytelling.


Final Thought

Dragon Age battles should look and feel like battles.

They should have chaos, formations, objectives, civilians, commanders, magic, monsters, consequences, and aftermath.

The player should not feel like they are clearing out enemy groups placed on a map.

They should feel like they are stepping into a war where every decision matters.

A battle should not just ask:

“Can you defeat these enemies?”

It should ask:

“Who survives because of your choices?”


More: Dragon Age Battles Need Scale, Pressure, and Consequence

The problem with many fantasy RPG battles is that they often say a war is happening, but the gameplay shows a small skirmish.

Dragon Age should not only tell the player, “This kingdom is under attack,” or “This faction is invading.” The player should see it, hear it, and feel trapped inside it.

A real Dragon Age battle should feel like the world is moving around you.

Soldiers should not stand around waiting for the player.
Enemies should not simply spawn in clean waves.
The battlefield should not feel like a flat combat arena.

It should feel like Thedas is breaking open.


13. Battles Should Have a Sense of Weight

When a battle starts, the player should feel the weight of it immediately.

The sound should change.
The music should build.
The camera should show the scale.
The ground should shake from siege weapons, dragons, golems, or charging armies.
The sky should be filled with smoke, arrows, ash, magic, and burning debris.

You should hear:

“Hold the line!”
“Archers, loose!”
“Fall back to the gate!”
“Mages, shield the wounded!”
“Darkspawn below!”
“The left flank is gone!”
“Where is the commander?”
“Maker help us!”

The player should feel like they have entered something already in motion.

That matters.

A battle should not feel like it begins only when the player crosses an invisible trigger.


14. The Player Should Not Always Control the Whole Battle

This is important.

The player should be powerful, but they should not always feel like the only person capable of doing anything.

Other soldiers should fight.
Other mages should cast.
Other commanders should issue orders.
Other heroes should make decisions.
Other factions should win or fail without the player personally touching every objective.

That makes the world feel alive.

The player can still be the deciding factor, but not the only factor.

For example, while the player is defending the gate, a group of allied soldiers might successfully hold the bridge. Or they might fail, depending on preparation, morale, leadership, supplies, and previous choices.

That creates tension.

The player cannot be everywhere.
So choices matter.


15. Battles Should Force Hard Priorities

A good Dragon Age battle should make the player choose what matters most.

You cannot save everyone.
You cannot hold every position.
You cannot protect every ally.
You cannot stop every enemy plan.

That is where Dragon Age becomes Dragon Age.

Imagine a battle where three crises happen at once:

  • The enemy is breaking through the front gate.

  • Civilians are trapped in the lower district.

  • A blood mage ritual is opening a demon breach.

The player has to choose.

Do you save the civilians?
Do you stop the ritual?
Do you protect the soldiers at the gate?

Whatever you choose, something else suffers.

That is not unfair. That is war.

Dragon Age should not be afraid of that.


16. Every Battle Should Have a Before, During, and After

A major battle should not be one isolated mission. It should have structure.

Before the Battle

The player gathers allies, chooses defenses, scouts the area, negotiates support, trains militia, sets traps, handles morale, and decides who commands which section.

This is where RPG choices matter.

A player who helped the dwarves earlier may get engineers.
A player who saved a Dalish clan may get archers and scouts.
A player who spared a mage faction may get barrier support.
A player who angered the Chantry may lose templar reinforcement.
A player who invested in a village may find its people willing to fight.

The battle should remember your journey.

During the Battle

The player moves through changing objectives. Nothing stays still. Every decision matters under pressure.

The gate falls.
The left flank breaks.
A commander is injured.
A dragon circles overhead.
A companion is cut off.
A demon enters the battlefield.
A hidden ally arrives.

This is the chaos.

After the Battle

The result should change the world.

A settlement may become stronger.
A faction may collapse.
A companion may lose faith in you.
A noble house may owe you.
A village may be destroyed.
A new enemy may rise from the ruins.

That is what makes battles meaningful.


17. Battle Preparation Should Be a System

Dragon Age could have a full battle preparation system without turning into a strategy game.

Before a major battle, the player could assign resources.

Defensive Choices

  • Reinforce the gate

  • Build barricades

  • Set traps

  • Place archers on rooftops

  • Station mages near the wounded

  • Protect supply carts

  • Secure escape routes

  • Prepare firebreaks

  • Dig trenches

  • Seal tunnels

Troop Assignments

  • Put warriors on the front line

  • Send rogues to sabotage enemy supplies

  • Assign mages to barriers or offense

  • Use dwarven engineers for traps

  • Use scouts to detect ambushes

  • Keep cavalry in reserve

  • Place healers near civilians

  • Hold elite troops for the final push

Risk Decisions

  • Use dangerous magic for a stronger defense

  • Arm civilians

  • Collapse tunnels that may still contain survivors

  • Burn nearby fields to deny enemy cover

  • Poison the enemy’s water supply

  • Accept help from a morally questionable faction

This gives the battle depth before the sword is even drawn.


18. Morale Should Matter

Battles are not just about health bars.

Morale should affect how soldiers behave.

High morale soldiers hold formation longer.
Low morale soldiers panic, retreat, or make mistakes.
Inspired troops push forward.
Terrified troops break ranks.
Veterans respond better than raw militia.

The player could influence morale through choices.

Did you give a strong speech?
Did you bring enough healers?
Did you save the commander earlier?
Did you expose a traitor?
Did you secure food and supplies?
Did you recruit respected allies?
Did you execute prisoners and scare your own people?

Morale should shift during battle too.

If the enemy commander dies, their troops may falter.
If your banner falls, your soldiers may panic.
If a dragon lands, both sides may scatter.
If reinforcements arrive, your army may rally.

This makes battles feel human.


19. Commanders Should Matter

Every battle should have commanders who affect tactics.

A good commander changes how an army fights.

A reckless commander throws soldiers into danger.
A cautious commander keeps reserves.
A cruel commander sacrifices civilians.
A brilliant commander uses terrain.
A cowardly commander retreats too early.
A disciplined Qunari commander reforms broken lines.
A Tevinter magister uses soldiers like disposable pieces.
A darkspawn alpha overwhelms through numbers and terror.

Killing or saving commanders should change the battle.

If you defeat an enemy commander early, their army may become disorganized.
If your commander dies, your side may lose coordination.
If a companion takes command, their personality should affect the outcome.

This could create powerful companion moments.

A warrior companion might hold the line.
A rogue companion might lead a sabotage team.
A mage companion might shield an entire district.
A dwarf companion might organize engineers.
A Qunari companion might impose discipline on panicking troops.

That gives companions battlefield identity.


20. Reinforcements Should Depend on Past Choices

One of the best ways to make Dragon Age battles feel meaningful is to let past choices physically show up.

Imagine standing on a wall as the enemy approaches. You think you are outnumbered. Then you see banners on the horizon.

The Dalish arrive because you saved their clan.
Dwarven golems arrive because you helped a thaig.
Mages arrive because you protected them from persecution.
Templars arrive because you earned their trust.
A mercenary company arrives because you paid them.
A village militia arrives because you rebuilt their settlement.
A dragon cult arrives because you made a dangerous bargain.

Or maybe no one comes.

Because you burned those bridges.

That is the kind of consequence Dragon Age should lean into.

The player should be able to look at the battlefield and say:

“That is here because of what I did earlier.”


21. The Enemy Should Adapt During Battle

Enemies should not just run forward and die.

They should adapt.

If the player relies on mages, enemies send mage-hunters.
If the player holds chokepoints, enemies use flanking tunnels.
If the player uses traps, enemies send expendable scouts first.
If archers dominate the field, enemies raise shields or use smoke.
If the player targets commanders, commanders begin hiding behind guards.
If the player uses fire, enemies spread out.
If the player keeps healing soldiers, enemies target healers.

This makes the battle feel intelligent.

A Qunari commander should not fight like bandits.
A Tevinter magister should not fight like darkspawn.
A demon army should not fight like soldiers.

Every enemy force should have a brain, even if that brain is monstrous.


22. Terrain Should Matter More

Dragon Age battlefields should not be flat spaces with enemies standing around.

Terrain should change strategy.

Hills

Archers gain range. Cavalry gains charge momentum. Mages have better visibility.

Forests

Ambushes, traps, hidden archers, limited visibility, moving shadows.

Swamps

Slowed movement, poison gas, disease, hidden creatures, unstable footing.

Ruins

Collapsed walls, chokepoints, hidden rooms, old magic, vertical combat.

Cities

Rooftop archers, street barricades, civilians, burning buildings, narrow alleys.

Deep Roads

Tunnels, cave-ins, darkspawn ambushes, golem chokepoints, limited escape.

Frozen Areas

Slippery ground, freezing magic, broken ice, visibility issues.

The battlefield should be part of the fight.

Not decoration.


23. Siege Weapons and War Machines Should Matter

Dragon Age should use more battlefield machinery.

Not in a way that breaks the fantasy, but in a lore-friendly way.

  • Ballistae

  • Catapults

  • Trebuchets

  • Dwarven drilling engines

  • Qunari gaatlok explosives

  • Tevinter arcane cannons

  • Darkspawn corruption engines

  • Elven relic weapons

  • Golem siege units

  • Magical barrier towers

  • Anti-dragon harpoons

  • War wagons

  • Trap carts

  • Flame projectors powered by alchemy

These should not just be background props.

The player should interact with them.

Destroy them.
Defend them.
Aim them.
Sabotage them.
Repair them.
Steal them.
Turn them against the enemy.

That instantly makes battles feel bigger.


24. Battlefield Roles Should Be Clear

A battle feels better when every group has a purpose.

Infantry

Hold ground, protect mages, push lines, defend gates.

Archers

Control distance, punish exposed enemies, suppress enemy movement.

Mages

Barriers, healing, area denial, artillery, anti-demon work.

Rogues

Sabotage, assassination, scouting, trap disabling, supply disruption.

Cavalry or Beast Units

Break lines, chase fleeing enemies, disrupt formations.

Engineers

Repair gates, operate siege weapons, build barricades, clear rubble.

Healers

Keep soldiers alive, stabilize wounded, protect morale.

Commanders

Coordinate troops, give buffs, call retreats, change tactics.

When roles are clear, the player can understand the battle quickly and make meaningful choices.


25. The Player’s Class Should Change the Battle Experience

A warrior, rogue, and mage should experience battles differently.

Warrior

The warrior should be able to hold lines, rally troops, break formations, challenge enemy champions, defend choke points, and physically stop advances.

A warrior should feel like the anchor of a battlefield.

Rogue

The rogue should be able to sneak through chaos, sabotage siege engines, assassinate commanders, set traps, open gates, poison supplies, and rescue prisoners.

A rogue should feel like the hidden knife that changes the battle.

Mage

The mage should be able to shield allies, disrupt enemy magic, destroy formations, close Fade rifts, heal groups, and alter terrain.

A mage should feel like a walking battlefield event.

This would make class choice matter beyond combat animations.


26. Battlefield Champions Should Exist

Major battles should sometimes include elite enemy champions.

Not just bosses waiting in an arena, but battlefield threats moving through the fight.

Examples:

  • A Qunari shock trooper breaking shield lines

  • A darkspawn ogre smashing gates

  • A Tevinter battlemage burning rooftops

  • An Orlesian chevalier cutting through militia

  • A demon possessing fallen soldiers

  • A dwarven golem corrupted by red lyrium

  • A blood mage turning wounded soldiers into weapons

  • A giant beast pulling siege chains

The player may have to decide:

Do I stop the champion now?
Or do I finish the main objective first?

That creates pressure.


27. Friendly Losses Should Be Visible

The game should not hide the cost of war.

If a gate falls, soldiers should die.
If healers are not protected, wounded troops should be lost.
If civilians are ignored, the player should see the aftermath.
If a bridge is abandoned, allies on the other side may be trapped.

This does not mean the game has to be cruel for no reason.

It means consequences should be visible.

The player should feel the difference between a clean victory and a costly victory.


28. Victory Should Have Different Grades

Winning should not always mean “everything went fine.”

A battle could end in different states.

Heroic Victory

Most objectives completed, low casualties, strong morale, major allies survive.

Costly Victory

The enemy is defeated, but the city is damaged, important NPCs die, or resources are depleted.

Pyrrhic Victory

You technically win, but the losses are devastating.

Tactical Retreat

You fail to hold the area, but save key people or resources.

Strategic Defeat

The enemy wins the field, but the player may still escape and continue the story.

This makes battles more realistic.

Sometimes surviving is the victory.


29. Enemies Should Retreat, Surrender, or Break

Not every battle should end with every enemy dead.

Some enemies should flee.
Some should surrender.
Some should regroup.
Some should pretend to retreat and ambush later.
Some should desert.
Some should beg for mercy.
Some should fight to the death because of belief, corruption, fear, or control.

This makes enemies feel less like disposable targets.

A Qunari unit may retreat in perfect order.
Bandits may scatter when their leader dies.
Darkspawn may keep charging until destroyed.
Tevinter soldiers may surrender if their magister falls.
Demons may vanish and return later.

How the player treats prisoners should affect reputation.

Mercy, execution, ransom, recruitment, interrogation, or release should all have consequences.


30. Battles Should Create New Quests

A major battle should not end the story. It should create more stories.

After a battle, new quests could appear:

  • Find missing soldiers

  • Identify traitors

  • Hunt fleeing enemy commanders

  • Recover stolen banners

  • Bury the dead

  • Treat poisoned survivors

  • Rebuild damaged defenses

  • Escort refugees

  • Investigate strange magic left behind

  • Rescue prisoners taken during the retreat

  • Track darkspawn tunnels

  • Decide what to do with enemy captives

  • Help a companion mourn a fallen ally

  • Stop looters from robbing the dead

This makes the battle part of the world, not just a mission checkpoint.


31. Civilian Presence Should Change the Tone

Battles become more serious when civilians are involved.

A fight in an empty field is one thing.

A fight in a village, city, refugee camp, marketplace, or temple is different.

Civilians should run, hide, panic, pray, help the wounded, block roads, or refuse to leave.

The player may have to:

  • Open escape routes

  • Defend shelters

  • Stop fires

  • Escort children or elders

  • Protect healers

  • Decide whether to use dangerous magic near civilians

  • Stop soldiers from looting

  • Prevent panic from becoming a stampede

This is where Dragon Age can show moral pressure.

The battlefield is not just soldiers.

It is people.


32. Battle Dialogue Should Be Reactive

Characters should not give generic battle lines only.

Dialogue should react to what is happening.

If the player saves civilians, companions comment.
If the player abandons soldiers, commanders remember.
If mages are used recklessly, templars object.
If the player spares enemies, some allies get angry.
If the player sacrifices a flank, survivors blame them.
If a companion’s people are involved, they react more personally.

Example:

Companion:
“You chose the gate over the lower district. I understand the strategy. I do. But those people screamed for us.”

That is Dragon Age.

Strategy and emotion colliding.


33. Battles Should Have Political Consequences

Every major battle should shift power.

A noble house may gain prestige.
A rival faction may exploit the damage.
A city may blame mages for destruction.
The Chantry may use the battle for propaganda.
The Qunari may study your tactics.
Tevinter may retaliate.
Dwarven merchants may raise prices because supply routes are broken.
Refugees may flood nearby settlements.
Bandits may take advantage of weakened patrols.

War changes politics.

Dragon Age should show that.

A battle should affect maps, merchants, dialogue, faction strength, and future quests.


34. Battles Should Have Memory

The game world should remember famous battles.

Bards should sing about them.
Children should repeat rumors.
Survivors should recognize you.
Enemies should fear or mock you.
Commanders should study what happened.
Letters should mention the losses.
Graves should appear.
Memorials should be built.
A ruined battlefield should remain scarred.

The player should be able to return later and see what changed.

Maybe grass grows over the field.
Maybe a monument stands there.
Maybe undead rise because the dead were not properly buried.
Maybe scavengers built a settlement out of the wreckage.

That gives battles legacy.


35. The Best Battles Should Feel Like Playable History

A great Dragon Age battle should feel like something people in Thedas will talk about for generations.

Not because the player killed 60 enemies.

Because something happened there.

A kingdom survived.
A city burned.
A companion lost someone.
A faction was broken.
A dangerous alliance was formed.
A monster was unleashed.
A ruler was exposed.
A village became a symbol.
A hero became feared.

That is the kind of battle Dragon Age should aim for.

Not just combat.

Playable history.


Stronger Closing Statement

Dragon Age battles should not feel like random encounters stretched out with more enemies.

They should feel like moments where the world is being decided.

The player should see armies clash, hear commanders panic, watch soldiers break, feel magic tear through the field, and carry the consequences after the fighting ends.

A real battle should make the player ask:

Can we win?
What will it cost?
Who do I save?
Who do I sacrifice?
What will Thedas remember about this day?

That is how battles become more than gameplay.

That is how Dragon Age becomes epic again.


Dragon Age Battles Should Feel Like War, Not Enemy Placement

A battle should not feel like enemies were placed on a map for the player to clean up.

It should feel like two or more forces have goals, and the player is entering the middle of that conflict.

That means the enemy should not just exist to attack the player. They should have objectives of their own.

They may be trying to:

  • Capture a bridge
  • Burn supplies
  • Break a gate
  • Assassinate a commander
  • Kidnap a mage
  • Destroy a Chantry relic
  • Open a Fade breach
  • Collapse a tunnel
  • Poison a water source
  • Escort a prisoner
  • Protect a siege weapon
  • Retreat with stolen intelligence

The player should not always be the center of the battlefield. Sometimes the player is trying to stop something already happening.

That creates urgency.


36. Battles Should Have Multiple Sides

Dragon Age should use more than two-sided battles.

Not every conflict should be simple:

Good side versus bad side.

Thedas is more complicated than that.

A battle could involve:

  • Two human kingdoms fighting while darkspawn attack both
  • Qunari invading a port city while local criminals exploit the chaos
  • Mages and templars fighting while demons leak through the Fade
  • Dwarven houses fighting underground while Carta forces sell weapons to both
  • Dalish elves defending sacred ruins from humans, while spirits awaken beneath them
  • Tevinter forces battling Antivan mercenaries while slaves attempt an uprising
  • Orlesian nobles fighting each other while assassins target both commanders

This would make battles feel political, chaotic, and morally complex.

The player may not be choosing between perfect allies and obvious villains. They may be choosing which disaster to contain first.

That is very Dragon Age.


37. Neutral Forces Should Exist on the Battlefield

Not everyone on a battlefield should be an enemy or ally.

There should be neutral groups caught in the middle.

Examples:

  • Refugees trying to escape
  • Merchants protecting their carts
  • Healers treating both sides
  • Priests trying to evacuate civilians
  • Prisoners breaking loose
  • Servants trapped in a noble estate
  • Animals panicking and running through the field
  • Local militia refusing to follow either army
  • Mercenaries waiting to see who pays more
  • Spirits reacting to fear and death

The player’s choices could turn neutral groups into allies, enemies, casualties, or future questlines.

For example, if you protect a healer’s tent, that healer may later save an important companion. If you ignore them, wounded soldiers may die, and survivors may blame you.

Neutral groups make battles feel alive.


38. Battlefield Confusion Should Be Part of the Experience

War is confusing.

Dragon Age should allow that confusion without making gameplay frustrating.

The player should receive incomplete information.

A scout says the enemy is attacking the north gate, but it may be a diversion.
A commander claims reinforcements are coming, but they may be delayed.
A mage senses a ritual, but cannot locate it.
A companion hears darkspawn below, but no one believes them.
A noble officer gives bad orders because they are scared.
A captured enemy lies about the real attack.

The player has to decide who to trust.

That would make intelligence gathering important.

A rogue scouting ahead could reveal hidden enemies.
A mage could detect Fade corruption.
A warrior could read troop movement.
A dwarf could recognize unstable tunnels.
A Qunari companion could identify formation changes.

This gives party composition meaning before and during battle.


39. The Fog of War Should Be Emotional Too

The player should not always know who survived.

Imagine finishing a battle and asking:

Where is my companion?
Did the civilians escape?
Did the left flank survive?
Did the mages complete the barrier?
Did the commander make it out?
Did the enemy leader escape?
Did the village burn?

The battle ends, but the uncertainty continues.

Then the player walks through the aftermath and learns the truth.

That creates tension without needing fake drama.

Dragon Age should let battles breathe after the fighting stops.


40. The Sound of Battle Should Tell a Story

Sound design matters.

A battlefield should have layers of sound:

  • Swords hitting shields
  • Armor scraping
  • Arrows cutting through the air
  • Horses or beasts screaming
  • Mabari barking
  • Mages chanting
  • Barriers cracking
  • Siege engines firing
  • Buildings collapsing
  • Soldiers calling for healers
  • Commanders shouting orders
  • Civilians crying
  • Darkspawn shrieking underground
  • Demons whispering through the chaos

Sound should tell the player what is happening before they see it.

If the left flank collapses, the player should hear panic from that direction.
If a dragon approaches, the battlefield should go quiet for a second before the roar.
If a mage barrier fails, there should be a sharp magical crack that everyone reacts to.
If darkspawn tunnel upward, the ground should rumble before they emerge.

A battle should not only be seen.

It should be heard.


41. Visual Scale Should Not Mean Empty Spectacle

Big battles do not need to be fake background decoration.

The game can show scale intelligently.

There can be fighting in the distance, but it should connect to the mission.

If the player sees soldiers fighting on a wall, that wall should matter.
If siege weapons are firing, they should affect the battlefield.
If reinforcements appear in the distance, they should arrive or fail to arrive based on choices.
If a dragon circles overhead, it should eventually interact with the battle.

Players can feel when spectacle is fake.

Dragon Age should avoid battles where hundreds of soldiers are shown in the background but nothing they do matters.

The scale should be functional.


42. Battle Maps Should Have Strategic Zones

Large battles should be divided into meaningful zones.

For example, a city siege could have:

The Outer Wall

Archers, siege ladders, ballistae, falling debris, shield lines.

The Main Gate

Heavy infantry, rams, barricades, oil traps, magical barriers.

The Lower District

Civilians, fires, looters, wounded soldiers, evacuation routes.

The Market Square

Open fighting, cavalry charges, supply carts, enemy champions.

The Temple or Chantry

Refugees, healers, priests, relics, moral choices.

The Keep

Commanders, nobles, final defense, political decisions.

Each zone should have its own stakes.

The player may win one zone and lose another.

That creates a real battle report at the end.


43. Battle Reports Should Return

After major battles, the player should receive a clear but immersive report.

Not just “Quest Complete.”

A battle report could show:

  • Allies lost
  • Civilians saved
  • Enemy commanders defeated
  • Enemy commanders escaped
  • Districts damaged
  • Supplies preserved
  • Factions impressed or angered
  • Companions affected
  • Future risks created
  • Reputation gained
  • Prisoners captured
  • Strategic assets gained or lost

This would make the player understand the consequences of their choices.

It could be presented through a commander, advisor, war table, council meeting, or companion conversation.

Example:

Commander:
“We held the gate, but the lower district burned. The mages survived because of you, but the militia will not forget who was left behind.”

That is far stronger than a basic reward screen.


44. The War Table Should Connect to Real Battles

If Dragon Age uses a war table or strategic command system again, it should connect directly to playable battles.

No more choices that feel like text-only side content with little visible impact.

If you send scouts before a battle, hidden routes should appear.
If you assign engineers, barricades should be stronger.
If you recruit mages, barriers should appear on the battlefield.
If you neglect supplies, soldiers should start tired or wounded.
If you ignore a faction, they may refuse to reinforce you.
If you choose the wrong commander, troops may panic.

The war table should not replace gameplay.

It should prepare gameplay.


45. Companions Should Have Battlefield Assignments

Before a battle, the player should assign companions to roles.

Not every companion has to stay in the party. Some could command sections of the battle.

Examples:

Companion as Field Commander

They lead soldiers and affect morale.

Companion as Saboteur

They sneak behind enemy lines and disable siege weapons.

Companion as Mage Defender

They protect healers, civilians, or ritual casters.

Companion as Duelist

They intercept enemy champions.

Companion as Scout

They reveal hidden attacks or alternate routes.

Companion as Civilian Protector

They evacuate noncombatants.

The player’s trust in companions should matter.

A companion who agrees with your values may follow your order cleanly.
A companion who doubts you may challenge the plan.
A companion with trauma tied to the conflict may act emotionally.
A companion from that faction may refuse certain orders.

This makes companions feel like people, not just combat slots.


46. Companion Injuries Should Be Possible in Major Battles

Major battles should carry real risk.

Not necessarily permanent death every time, but consequences.

A companion could be:

  • Wounded
  • Captured
  • Separated
  • Traumatized
  • Temporarily unavailable
  • Forced to make a hard choice
  • Blamed by another faction
  • Praised by soldiers
  • Changed by command responsibility

If you assign a companion to hold an impossible position, they may survive but resent you.

If you send them to rescue civilians, they may save many people but lose their unit.

If you ignore their warning, they may be injured because they were right.

This would make companion management deeper.


47. Rival Commanders Should Remember You

Enemy commanders should study the player.

If the player wins a battle by using traps, the next commander brings scouts and engineers.
If the player relies on mages, the enemy brings templars, mage-hunters, or anti-magic devices.
If the player spares prisoners, enemies may attempt surrender as a tactic.
If the player executes captives, enemies may fight harder because they expect no mercy.
If the player always saves civilians, enemies may use civilians as bait.

This creates a campaign-level rivalry.

A recurring enemy commander could become one of the best villains in the game because they adapt to the player’s history.

Not just in cutscenes.

In tactics.


48. The Enemy Should Have Morale Breakpoints

Enemies should react when the battle turns against them.

Morale breakpoints could happen when:

  • Their commander dies
  • Their banner falls
  • Their siege weapon is destroyed
  • Their reinforcements fail to arrive
  • Their mage support is killed
  • Their flank is broken
  • Their supply cart burns
  • Their champion is defeated
  • Their prisoners are freed
  • Their ritual fails

Different factions respond differently.

Bandits may flee.
Qunari may regroup.
Darkspawn may frenzy.
Tevinter slaves may surrender.
Demons may possess the dying.
Orlesian soldiers may turn on incompetent nobles.
Mercenaries may switch sides if payment fails.

This makes victory feel like breaking an army, not just emptying health bars.


49. Battlefield Magic Should Have Risks

Magic should be powerful, but battlefield magic should carry consequences.

A mage can burn enemy lines, but may set homes on fire.
A barrier can save soldiers, but trap civilians outside it.
A lightning storm can destroy siege engines, but kill allied troops nearby.
A Fade ritual can close a breach, but attract spirits.
Blood magic can turn the tide, but permanently stain the area.

This creates the classic Dragon Age tension:

Power versus cost.

A mage-heavy solution should not be automatically good or bad. It should depend on control, ethics, environment, and consequences.

The player should have to ask:

Is this magic worth the damage it may cause?


50. Templars Should Matter in Large Battles

Templars should not only exist as anti-mage enemies in small fights.

On a battlefield, templars could be strategic units.

They could:

  • Disrupt enemy spellcasting
  • Protect troops from demons
  • Break magical barriers
  • Guard dangerous mages
  • Resist possession
  • Suppress blood magic rituals
  • Create anti-magic zones
  • Escort prisoners or apostates
  • Clash with allied mages over tactics

This could create great battlefield tension.

If the player brings templars, mages may feel controlled.
If the player brings mages without templars, magic may be stronger but riskier.
If the player uses both, discipline and distrust become part of the battle.

That is Thedas.


51. Healers Should Be Important Targets

Healers and support units should matter.

If the player protects healers, more soldiers survive.
If healers are overrun, casualties rise.
If enemy healers remain alive, enemy champions keep returning.
If field medics are captured, morale drops.
If healing supplies are burned, the aftermath becomes worse.

This creates objectives beyond killing.

A mission could involve escorting a healer through active combat, defending a triage tent, or choosing which wounded group receives limited healing.

That is where Dragon Age can create painful moral decisions.

Do you save the nobles who can fund the war?
The common soldiers who held the line?
The civilians who cannot fight?
The enemy prisoners who surrendered?

Those choices reveal the player’s values.


52. The Wounded Should Not Disappear

After a major battle, wounded NPCs should remain visible.

They should be in tents, temples, field hospitals, ruined homes, or makeshift camps.

Some should recover.
Some should worsen.
Some should die if resources are limited.
Some should ask about missing family.
Some should blame the player.
Some should thank the player.
Some should become future recruits, informants, enemies, or quest-givers.

This makes battle consequences human.

A war is not only the dead.

It is the people left carrying the damage.


53. Battlefields Should Become Locations Afterward

A battlefield should not vanish after the quest.

The player should be able to return.

Afterward, the area might become:

  • A graveyard
  • A refugee camp
  • A ruined settlement
  • A military outpost
  • A contested zone
  • A haunted field
  • A darkspawn-corrupted area
  • A memorial site
  • A scavenger camp
  • A political symbol
  • A place of pilgrimage
  • A future ambush location

The same map can evolve.

First it is a battlefield.
Then it is a recovery zone.
Then it becomes part of history.

That is efficient worldbuilding and strong storytelling.


54. Weather Should Affect Battles

Weather should matter in warfare.

Rain makes fire magic harder to spread but turns fields to mud.
Fog helps rogues and ambushers but confuses archers.
Snow slows movement and drains stamina.
Wind affects arrows, smoke, poison gas, and fire.
Heat exhausts armored troops faster.
Thunderstorms amplify certain magic but increase danger.

A battle in heavy rain should not feel the same as a battle under clear skies.

Imagine fighting in a muddy Fereldan field as soldiers slip, shields sink, and mabari struggle through the ground.

Imagine a Tevinter ritual battle under a lightning storm, where every spell feels unstable.

That would make battles memorable.


55. Night Battles Should Be Terrifying

Night battles should feel different.

Visibility is limited.
Torches matter.
Scouts matter.
Fear spreads faster.
Demons feel more dangerous.
Darkspawn become harder to track.
Arrows come from unseen places.
Friendly fire becomes a risk.
Command signals can be misunderstood.

The player may need to light braziers, protect signal towers, follow horns, or identify enemies by banners and sound.

Night battles could create some of the best horror moments in Dragon Age.

A darkspawn attack at night should feel like a nightmare.

You hear them before you see them.


56. Battle Signals Should Be Gameplay

Armies communicate through signals.

Dragon Age could use:

  • War horns
  • Drums
  • Banners
  • Signal fires
  • Mage flares
  • Messengers
  • Ravens
  • Dwarven sound pipes in tunnels
  • Qunari command flags
  • Tevinter magical glyphs

The player could sabotage enemy signals or protect allied ones.

If enemy horns are destroyed, their reinforcements arrive late.
If allied banners fall, morale drops.
If signal fires are lit, reserves move to the right location.
If messengers are killed, commands fail.

This is a great way to make battles tactical without overwhelming the player.


57. Supplies Should Matter Before and After Battle

Armies do not fight on courage alone.

They need food, medicine, arrows, lyrium, armor, repair materials, horses, tools, and clean water.

The player should feel that.

If supplies are strong:

  • Soldiers start with better morale
  • Archers have more ammunition
  • Healers save more lives
  • Mages have lyrium support
  • Barricades hold longer
  • Wounded recover faster

If supplies are weak:

  • Soldiers panic sooner
  • Healers are overwhelmed
  • Mages cannot maintain barriers
  • Archers run dry
  • Engineers cannot repair gates
  • Refugees suffer afterward

A pre-battle quest to protect a supply caravan should matter later.

Not as flavor text.

As visible battlefield impact.


58. The Player Should See Their Allies Fighting

When the player recruits allies, those allies should appear.

This is important.

If the player earned the support of dwarves, show dwarven soldiers, engineers, or golems in battle.

If the player earned Dalish support, show Dalish archers and hunters on the ridges.

If the player helped mages, show barriers and spell support.

If the player made a deal with mercenaries, show them holding a flank.

If the player saved a village, show its militia arriving in patched armor with old weapons.

Players remember when choices become visible.

That is how you make alliances feel real.


59. Enemy Armies Should Have Supply Lines Too

The player should be able to weaken enemies before a major battle.

Not every victory should come from fighting the full army head-on.

Before the battle, the player could:

  • Poison or steal supplies
  • Destroy bridges
  • Ambush scouts
  • Free prisoners
  • Spread false orders
  • Sabotage siege weapons
  • Assassinate officers
  • Bribe mercenaries
  • Expose a traitor
  • Start a slave revolt
  • Collapse darkspawn tunnels
  • Disrupt blood magic rituals

Then during the battle, the effects show.

Fewer enemies arrive.
Siege weapons fail.
Enemy morale is low.
A commander distrusts their own officers.
A slave unit refuses to fight.
Darkspawn emerge from the wrong tunnel.

This makes preparation feel powerful.


60. Battles Should Let the Player Win Through Strategy

The player should not always win because they are the strongest person on the field.

They should win because they made smart decisions.

A clever rogue should be able to break a battle by destroying the enemy command structure.

A diplomatic player should be able to bring enough allies to avoid disaster.

A mage-focused player should turn the terrain itself into a weapon.

A warrior leader should inspire soldiers to hold impossible ground.

A ruthless player may win quickly but leave scars.

A merciful player may win slower but gain loyalty.

That is role-playing.

The battle should reflect the kind of leader the player is becoming.


Stronger Section: What Makes a Battle Feel Real?

A real Dragon Age battle needs five things:

1. Scale

The player should feel part of something larger.

2. Pressure

The player should not have time to solve everything perfectly.

3. Choice

There should be meaningful priorities and sacrifices.

4. Identity

Every faction should fight differently.

5. Aftermath

The world should remember what happened.

Without those five things, a battle is just a large fight.

With them, it becomes a Dragon Age moment.


Final Expansion

Dragon Age should stop treating battles like bigger combat encounters and start treating them like turning points in history.

A battle should have soldiers, civilians, commanders, fear, magic, politics, sacrifice, confusion, mistakes, glory, trauma, and consequences.

The player should not walk away thinking:

“That was a long fight.”

They should walk away thinking:

“That changed everything.”

That is the difference between combat and war.

That is the difference between a skirmish and a battle.

And that is what Dragon Age needs more of.

Comments

Popular Posts