Nav

Home

Dashboard

Roster

CharactersClonesSkill ManagementSkills

Organization

AlliancesContactsCorporationsStructures

Hangars

Active ShipsInventory HubMutations HubShip Fitting

Combat & movement

Combat StatsRegional ActivityResearch HubTravel PlannerWar HQ

Industry & mining

Blueprint CatalogBlueprint StatsFreelance JobsIndustrial HubMining LedgerMoon ExtractionsMoon Mining HubPlanetary ColoniesPlanetary Survey

Markets & finance

Acquisitions HubEconomy StatisticsHyperNetKillmail Market IntelPlex VaultRaw Ore MarketsRefined MineralsWallet Ledger

Comms

CalendarEmailsNotifications

Workspace

Image ShareNotesOverview LabTo Do List

Reference

Wiki
HelpSettings
UTC15:53

Loading…

Topics

Static reference articles on mechanics and fitting trade-offs. Pick a topic below; section links appear when you open an article.

All topics

Fitting

  • Mining BreakdownStrip miners vs ORE strip miners, crystals, mining upgrades, survey chipsets, residue trade-offs, ore-hold compression timing, and barge/exhumer comparisons.

Combat

  • Bumping MechanicHow collision bumping works in EVE, mass and speed trade-offs, and reference bump fits ranked for frigate through capital targets.
  • War MechanicsDeclare wars, warm-up and cooldown timers, weekly bills, War HQ rules, allies, surrender, and victory conditions — split into Attacker and Defender guides.

On this page

  • War mechanics overview
  • War phases & timers (both sides)
  • War eligibility (who can be in a war)
  • Aggressive war vs mutual war
  • Attacker — role overview
  • Attacker — declaring war
  • Attacker — bills & renewal
  • Attacker — winning, losing & invalid wars
  • Attacker — surrender & mutual status
  • Defender — role overview
  • Defender — when you are attacked
  • Defender — allies & assistance
  • Defender — ending the war on your terms
  • Defender — after the war ends
  • War HQ & structure objectives

War Mechanics

Ready
Declare wars, warm-up and cooldown timers, weekly bills, War HQ rules, allies, surrender, and victory conditions — split into Attacker and Defender guides.
Wiki/War Mechanics

Combat

War Mechanics

Declare wars, warm-up and cooldown timers, weekly bills, War HQ rules, allies, surrender, and victory conditions — split into Attacker and Defender guides.

Last reviewed 2026-06-02

War mechanics overview

Formal wars let corporations and alliances fight in high-sec and low-sec without CONCORD destroying the aggressor and without security status loss — within the rules of the active war. Wars are a diplomacy tool: declaration, timers, weekly bills, eligibility, allies, surrender, and structure-based objectives.

This guide is split by role. Shared rules (timers, eligibility, war types) come first; then Attacker and Defender sections focus on what each side should do at each phase. Use War HQ in the app to track notifications and timelines for wars touching your characters.

  • Parties — wars are between corporations and/or alliances (member corps are included).
  • Spaces — high-sec and low-sec war combat is legal between war participants; null-sec is always null rules.
  • Not a substitute for diplomacy — standings, intel, and structure timers still matter outside the war UI.

War phases & timers (both sides)

Every aggressive war moves through predictable phases. Mutual wars share the cooldown and combat rules but skip warmup and weekly billing. Ally corps add a separate short warmup before they may shoot the attacker.

Core war timeline (aggressive / standard war)

PhaseDurationWhat it means
Warm-up (startup)24 hoursWar is declared and billed, but parties cannot legally war-combat yet. Both sides prepare logistics, move assets, and read notifications.
Active war week7 days per paid cycleLegal combat between war participants (and eligible allies) in high/low sec. Renew by paying the weekly CONCORD bill before the cycle lapses.
Cooldown24 hours after war endsWar is over on paper, but combat remains legal for 24 hours — prevents ending a war to dodge a specific fight. CONCORD protection returns after cooldown.
Surrender peace block14 daysIf surrender is accepted, neither side may declare war on the other again for two weeks.
Ally join warm-up4 hoursAfter a defender accepts an ally, that ally must wait 4 hours before engaging the attacker (not the defender).

Instant re-declaration (cooldown replacement war)

SituationWarm-up?Why
Either side declares a new war while the previous war is in its 24h cooldownNo — shooting allowed immediatelyBoth sides were already legal combatants; CCP removed the old “deploy during enemy warmup” loophole.
Brand-new war (no overlapping cooldown)Yes — 24 hoursStandard preparation period before first legal shots.

Mutual wars do not use the 24h declaration warm-up or weekly ISK bills. They still use the 24h cooldown when retracted or ended.

War eligibility (who can be in a war)

War eligibility controls who may declare wars, be declared on, and join as a defender ally. NPC corporations are never eligible. For player corps, owning certain Upwell structures (or a customs office) makes you eligible — which is also why structure-heavy corps are common war targets.

  • Eligible — can declare aggressive wars (if your side meets other rules), be wardecced, and receive ally offers on defense.
  • Ineligible — cannot declare or be declared on; existing wars may wind down on a timer if eligibility is lost.
  • Alliance eligibility — if any member corp owns a qualifying structure, the alliance becomes embroiled in alliance-level wars.
TriggerEffect
Corp anchors a qualifying Upwell structure (or customs office)Corp becomes war eligible — can attack and be attacked.
Last qualifying structure destroyed, unanchored, or transferred awayCorp may become ineligible; active wars end after a delay (see defender section).
Corp leaves alliance during warWars copy to the leaving corp; alliance war may cooldown; corp wars can continue if bills paid.

Aggressive war vs mutual war

Aggressive wars are paid, structure-tied declarations against a target. Mutual wars are opt-in on both sides — invitation and acceptance — and follow a lighter ruleset focused on PvP agreements rather than CONCORD billing.

Aggressive warMutual war
Started byAttacker declares on targetInvitation → acceptance (like corp applications)
Weekly ISK bill100M ISK / week to CONCORD (attacker pays)None
War HQ structureRequired for attacker (designated HQ)Not required
War eligibilityRequired for participantsNot required
AlliesDefender may take allies (4h ally warm-up)Allies dropped when war becomes mutual
Typical endBill lapse, HQ loss, surrender, eligibility lossEither side retracts, 90 days without PvP kills, or mutual revoked

Attacker — role overview

The attacker is the corporation or alliance that declared the aggressive war (or accepted a mutual invitation). Your responsibilities are paying CONCORD, maintaining War HQ if required, coordinating the 24h warm-up, and renewing or ending the war deliberately.

  • CEO or director of the executor corp (in an alliance) declares from Corporation → Wars.
  • Shareholders receive notifications when war starts and when it ends.
  • Legal targets are the declared defender entity and their allies in that war — not random neutrals.

Attacker — declaring war

Declaration is immediate once you confirm the target search result — there is no second fee confirmation dialog. Plan ISK and structure readiness before clicking Declare War.

  • Open Corporation window → Wars (or Alliance → Home tab for executor corp) → Declare War → search target corp or alliance.
  • Designate a War HQ Upwell structure for aggressive wars — if HQ is destroyed, unanchored, or leaves space, the war becomes invalid and enters cooldown.
  • First week’s war bill is paid automatically on declaration; a bill for week two is issued immediately and must be paid manually to continue past day seven.
  • During an existing war’s 24h cooldown, either side may declare a replacement war that starts with combat legal immediately (no new warm-up).

Attacker checklist at declaration

StepDetail
Confirm targetVerify corp vs alliance scope — entire alliance is included when you dec the alliance.
Fund wallet100M ISK + planned renewal weeks; unpaid wars lapse at cycle end.
War HQAnchor and set HQ before relying on war validity; HQ loss ends the war.
Notify membershipWarm-up is for moving caps, updating SRP, and assigning scouts — not for shooting yet.

Attacker — bills & renewal

Aggressive wars are rented from CONCORD in one-week slices. If you stop paying, the war becomes invalid — defenders get relief on a timer, but the 24h post-war cooldown may still allow final engagements.

  • Flat 100 million ISK per week (current ruleset) — not per member.
  • Making the war mutual (defender option) removes your weekly fee while mutual status lasts.
  • Track due dates in Corporation → Wars → Our Wars; treat lapse like losing the war objective.

Attacker — winning, losing & invalid wars

Victory in EVE wars is operational, not a scoreboard flag. You win when the defender cannot sustain operations, surrenders, or you achieve your strategic goal before the war lapses. The game ends wars through concrete triggers.

OutcomeWhat happensAttacker impact
Weekly bill not paidCONCORD invalidates the war at cycle endWar ends; 24h cooldown; you must re-declare (and warm up) if you want a new aggressive war.
Your War HQ destroyed / unanchored / removedWar becomes invalidTreat as defeat — defenders may still shoot during cooldown.
Defender loses war eligibility (no structures left)War ends 24h after eligibility loss (timing interacts with warm-up — see defender section)You may need instant re-declare during cooldown to continue pressure if they re-anchor.
Defender accepts your surrender offerWar ends immediately (+ 24h cooldown); 14-day mutual re-dec blockYou pay agreed ISK; diplomacy window before next war.
War is mutual and you retractWar ends after standard 24h cooldownNo weekly bills while mutual; allies already removed.

War Report (Corporation → Wars → Open War Report) tracks kills and ISK destroyed — useful for measuring effectiveness, not for automatic victory.

Attacker — surrender & mutual status

Surrender is an offer from either side’s CEO/director; the other side accepts or declines. ISK can accompany the offer. Mutual status is primarily a defender-driven toggle that changes billing and ally rules.

  • Send Surrender Offer from Our Wars — include ISK payment if that is the deal.
  • If defender sets war mutual: your weekly bills stop, allies are dropped, and neither side may add allies while mutual.
  • You may retract a mutual war — standard 24h cooldown applies.
  • Mutual wars auto-end after 90 days with no PvP kills between the parties.

Defender — role overview

The defender is the corporation or alliance named in the declaration. You receive notifications at declaration, at war start (warm-up end), and when the war ends. Your goals are survival, ally coordination, structure defense, and choosing whether to escalate (mutual) or negotiate (surrender).

  • You do not approve an incoming aggressive war — it is live after declaration, with combat after warm-up.
  • High-sec CONCORD still protects non-participants; only war participants gain legal aggression rights against each other.
  • Use War HQ and corp notifications to align pilots on timers — duplicate corp broadcasts are normal across characters.

Defender — when you are attacked

From the moment of declaration, assume assets in high/low sec are at risk once the 24-hour warm-up ends. Use warm-up for move ops, fuel, backup structures, and ally outreach — not for pretending the war does not exist.

  • Structure timers (armor/hull, vuln windows) are separate from war timers but often coincide — watch StructureUnderAttack notifications.
  • If you are not war eligible, you generally cannot be dec’d — but the moment you anchor a qualifying structure you become a target.

Defender timeline after declaration

WhenYour statusRecommended actions
T+0 declarationWar pending; combat illegalConfirm attacker identity, verify War HQ on killboards, ping leadership, start ally search.
T+24h warm-up endsWar activeTreat undocked industrialists and structures as wartime targets; enable wartime SRP and comms.
Each paid attacker weekWar continues if attacker paysMonitor bills indirectly via war status; push for mutual only if that helps your strategy.
War end + 24h cooldownCombat still legalDo not assume immediate safety — plan for final ganks and instant re-declaration wars.

Defender — allies & assistance

Only the defender side may accept allies in aggressive wars. Allies fight the attacker legally after a 4-hour preparation timer. Allies cannot join if they are already at war with the attacker.

  • Open for Allies — flag on Our Wars so third parties can find you in All Wars → Assistance requests.
  • Review Offer Assistance messages; ISK payment is optional and one-time from Master Wallet if accepted.
  • Accepted allies engage attackers only after 4h — plan coverage for EU/US TZ gaps.
  • Mutual war — allies are removed automatically; coordinate direct with partner corps instead.

Defender — ending the war on your terms

Defenders can force strategic outcomes by destroying the attacker’s War HQ, making the war mutual, accepting surrender, or removing eligibility (structure transfer/decommission) with awareness of delayed end timers.

MethodResult
Destroy attacker War HQWar invalid → 24h cooldown
Declare mutualStops attacker weekly bills; allies dropped; either side may later retract
Accept attacker surrenderImmediate end + 14-day re-dec block + 24h cooldown
Offer your own surrenderIf accepted, same peace block rules
Attacker fails to pay billWar lapses at cycle end
You lose last qualifying structureWar ends 24h after eligibility loss (special rules if loss happens during attacker warm-up)

If your last structure is destroyed during the attacker’s 24h warm-up, combat may still become legal for 24h after warm-up ends before the war fully concludes — plan structure recovery accordingly.

Defender — after the war ends

War end notifications go to involved parties and shareholders. CONCORD resumes normal high-sec rules after the 24-hour cooldown unless a replacement instant war is declared during that window.

  • Cooldown fighting — attackers may pursue a last engagement; keep wartime fleets and alarms through the full 24h.
  • Instant re-war — either side may declare during cooldown with no warm-up; common when redeploying structures.
  • Surrender peace — 14 days where neither party can declare on the other; use for negotiation or recovery.
  • Update standings and diplomacy contacts so members do not shoot ex-war participants under old rules of engagement.

War HQ & structure objectives

Aggressive wars tie the attacker to a designated War HQ Upwell structure. Structure combat notifications (under attack, reinforced, destroyed) are the operational heartbeat of many wars — War HQ in NewEden Axiom surfaces these alongside war lifecycle alerts.

  • War HQ loss invalidates the aggressive war — primary defender objective in structure-heavy metas.
  • Defenders still defend their own engineering complexes and citadels under normal siege rules.
  • Corp leaving alliance copies wars to the corp; alliance-level war may enter cooldown simultaneously.
Notification themeTypical meaning
WarDeclared / DeclareWarNew war — start warm-up clock
CorpBecameWarEligible / CorpNoLongerWarEligibleEligibility changed — review vulnerability
StructureUnderAttack / ReinforcedActive siege — form response
StructureDestroyed / LostObjective taken — check if War HQ or eligibility changed
AllyJoinedWarAggressorMsg / ally offersThird party entering — review ally contracts