Three Role-Specific Magus Fits—and the Risks Behind Each One

Choose the build by activity, not by hull alone

There is no single general-purpose answer to a search for EVE Online Magus builds. The available evidence supports three configurations built for different jobs:

Build	Documented activity	Core idea	Primary risk
Shield-buffer kiter	Nullsec solo or small-gang PvP	Mobile tackle, speed, displacement, and skirmish support	Limited durability if caught or forced into a close trade
Active-armor brawler	Nullsec solo or small-gang PvP	Scram-range pressure supported by local repair and capacitor injection	Close-range commitment can make disengagement difficult
Active-armor drone PvE fit	Selected T1 Calm Abyssal sites	Drone-focused damage with supplementary weapons and an active armor tank	Narrow scope and unresolved testing evidence

The two PvP configurations come from a player-authored guide published by the greybill and labeled as having been written in winter 2023/2024. The guide explicitly warns that game balance or the fittings may have changed since then.¹ The Abyssal configuration comes from a separate community fit on Abyss Tracker. It documents one low-tier PvE proposal, not a PvP fit, higher-tier Abyssal solution, or general-purpose Magus.²

All three are therefore historical or community-authored fitting baselines. None is established here as a current, optimal, independently tested doctrine.

A concise selection rule is:

• Start with the shield fit when mobility, longer-range tackle, and small-gang utility are the priorities.
• Examine the armor fit when entering scram range and managing a committed active tank are intentional parts of the plan.
• Use the PvE fit only within its documented T1 Calm scope, and validate it before relying on it.

No supplied evidence establishes that either PvP variant is categorically superior. The choice depends on desired engagement range, gang composition, tackle duties, capacitor-management burden, and willingness to accept a difficult exit.

Shield-kiting Magus for mobile tackle and gang utility

The shield configuration is documented for nullsec solo or small-gang PvP, not PvE or large-fleet doctrine use. Its published module layout points toward mobile tackle: a warp disruptor, speed-oriented low slots, a shield buffer, displacement utility, and two Skirmish Command Bursts.¹

Documented shield fit

Low slots

• Damage Control II
• Nanofiber Internal Structure II
• Overdrive Injector System II
• Co-Processor II

Mid slots

• 5MN Quad LiF Restrained Microwarpdrive
• Republic Fleet Medium Shield Extender
• Micro Jump Field Generator
• Warp Disruptor II

High slots

• Three 150mm Light AutoCannon IIs
• Two Skirmish Command Burst IIs

Rigs

• Small Command Processor I
• Small EM Shield Reinforcer II

Documented drone inventory

• Five Warrior IIs
• Three Hobgoblin IIs
• Two Valkyrie IIs

Command charges

• Interdiction Maneuvers
• Rapid Deployment

This layout, including the module counts, drones, rigs, and command charges, is reproduced from the dated PvP guide.¹

What the loadout is trying to do

As a module-based interpretation, the 5MN Quad LiF Restrained Microwarpdrive, Nanofiber Internal Structure II, and Overdrive Injector System II emphasize movement. The Warp Disruptor II provides tackle, while the Republic Fleet Medium Shield Extender supplies a buffer rather than a local active-repair system. The Micro Jump Field Generator adds displacement utility.

The two Skirmish Command Burst IIs distinguish this from a simple damage-and-tackle destroyer. The documented Interdiction Maneuvers and Rapid Deployment charges align the fit with movement- and tackle-related gang support. The Small Command Processor I supports the dual-burst layout, while the Co-Processor II indicates that fitting resources mattered to the published configuration.

Three autocannons and the documented drone inventory provide offensive tools, but the source does not specify autocannon ammunition. It would be unsafe to infer a particular ammunition loadout, engagement envelope, or damage figure from the module names alone.

The drone list is an inventory, not a claim that every listed drone can be deployed simultaneously. The guide records five Warrior IIs, three Hobgoblin IIs, and two Valkyrie IIs, but it does not provide a tested deployment procedure or matchup-specific selection guide.¹

What remains unknown

The source does not provide current, independently verified values for:

• Loaded-weapon or combined drone-and-weapon DPS
• Effective hit points
• Speed or align time
• Capacitor duration
• Weapon, tackle, or command-burst ranges
• Signature radius
• CPU or power-grid margin
• Current market cost
• Required implants
• Minimum or recommended pilot skills
• A verified current import string

Those omissions matter because the fit’s proposed advantage is mobility and utility, not a documented numerical tank or damage threshold. A current fitting tool may show that the layout still works as written, needs skill-dependent adjustment, or no longer fits under current attributes. Until that check is performed, it is a concrete design baseline rather than an undock-ready recommendation.

Active-armor Magus for committed close-range fighting

The armor Magus is also documented for nullsec solo or small-gang PvP, but it is built around a different engagement decision. Its warp scrambler, dual armor repairers, capacitor booster, nosferatu, and armor command burst make it a scram-range brawler rather than a universal alternative to the shield fit.¹

Documented armor fit

Low slots

• Two Small Armor Repairer IIs
• Multispectrum Energized Membrane II
• Damage Control II

Mid slots

• 5MN Quad LiF Restrained Microwarpdrive
• Micro Jump Field Generator
• Small Capacitor Booster II
• Faint Epsilon Scoped Warp Scrambler

High slots

• Three 150mm Light AutoCannon IIs
• Small Energy Nosferatu II
• Armor Command Burst II

Rigs

• Small Auxiliary Nano Pump II
• Small Nanobot Accelerator II

Documented drone inventory

• Five Warrior IIs
• Three Hobgoblin IIs
• Two Infiltrator IIs

Consumables

• Navy Cap Booster 400 charges
• Rapid Repair command charges

The greybill guide associates this configuration with close-range commitment and warns that entering a fight can make disengagement difficult. It documents the dual repairers, capacitor support, scrambler, nosferatu, drones, rigs, and charges listed above.¹

How its systems fit the brawling role

The Faint Epsilon Scoped Warp Scrambler defines a closer tackle role than the shield fit’s warp disruptor. Once the Magus enters that environment, the two Small Armor Repairer IIs provide local active repair. The Multispectrum Energized Membrane II, Damage Control II, Small Auxiliary Nano Pump II, and Small Nanobot Accelerator II reinforce the armor-tanking structure.

The Small Capacitor Booster II, supplied with Navy Cap Booster 400 charges, gives the pilot a consumable capacitor-management tool. The Small Energy Nosferatu II provides another such tool when its operating conditions are met. The Armor Command Burst II and Rapid Repair charges complement the fit’s repair-focused design.

Together, those choices are consistent with sustained close-range pressure. They do not prove that the ship is capacitor-stable, that both repairers can run continuously, or that the nosferatu and booster guarantee sufficient capacitor under hostile pressure. The source does not quantify those outcomes.

The autocannons and drone inventory add damage options, but no autocannon ammunition is documented. The drone entries show what the fit carries; they are not evidence that all listed drones can be fielded together or that one flight is correct against every opponent.

The commitment problem

The source’s warning about difficult disengagement is a central operating constraint, not a footnote. The fit deliberately accepts close exposure in exchange for local repair, scram pressure, and armor-oriented support. Before closing range, the pilot needs a reason to believe the engagement is favorable and a plausible exit condition if it is not.¹

The evidence does not provide:

• Current armor repair per second
• Current EHP
• Loaded damage
• Capacitor-injection cadence
• Capacitor endurance under hostile pressure
• Current cost
• CPU or power-grid margin
• Matchup tables
• Validated engagement procedures
• Current-patch confirmation

Without those values, the fit cannot responsibly be described as cap-stable, highly durable, or favored against any particular target.

Shield kiter versus armor brawler: the practical tradeoffs

The two PvP fits share a hull, microwarpdrive, Micro Jump Field Generator, autocannons, drones, tackle, and command capability. Their remaining slot choices point toward substantially different jobs.¹

Consideration	Shield-kiting Magus	Active-armor Magus
Evidenced role	Mobile tackle and small-gang utility	Committed close-range brawler
Tackle type	Warp Disruptor II	Faint Epsilon Scoped Warp Scrambler
Tank approach	Medium shield buffer and Damage Control II	Dual armor repairers, resistance module, Damage Control II, and repair rigs
Command capability	Two Skirmish Command Burst IIs	One Armor Command Burst II
Documented charges	Interdiction Maneuvers and Rapid Deployment	Rapid Repair
Mobility emphasis	Nanofiber, overdrive, microwarpdrive, and a separation-focused role	Microwarpdrive for approach and positioning, without mobility-enhancing low slots
Engagement commitment	Favors maintaining separation	Intentionally enters scram range
Capacitor support	No dedicated booster or nosferatu in the documented fit	Small Capacitor Booster II, Navy Cap Booster 400 charges, and Small Energy Nosferatu II
Disengagement risk	Vulnerable if caught or scrammed	Explicit warning that disengagement may become difficult
Gang-facing support	Skirmish bursts, tackle, and displacement	Armor burst, close tackle, and displacement
Pilot-management burden	Range, movement, tackle, bursts, drones, and displacement	Repair cycles, booster charges, capacitor pressure, tackle, drones, burst, and displacement

When the shield fit makes more sense

Choose the shield baseline when the intended job is to move with a roaming gang, apply tackle, support skirmish movement, and preserve separation. Its warp disruptor, shield extender, mobility lows, and two skirmish bursts all reinforce that role.

That does not make it safe. The documented fit has no active shield repair system, and the source supplies no numerical tank figure with which to predict survival if hostile tackle removes its mobility advantage.

It is not automatically the better solo fit either. The proposed benefits depend on the pilot’s ability to preserve movement, interpret the tactical situation, and use displacement effectively. The source does not provide tested engagement procedures proving those outcomes.

When the armor fit makes more sense

Choose the armor baseline when scram-range commitment is deliberate and the pilot is prepared to manage repairers, booster charges, capacitor pressure, drones, tackle, and an eventual exit. Its modules are aligned around surviving and applying pressure after close contact has been established.

That approach may offer local repair that the shield fit lacks, but the evidence does not quantify the practical difference.

Flying difficulty and fragility

The PvP guide considers the Magus suitable for a main account but more challenging to fly as tackle than an interceptor. It also characterizes command destroyers as fragile because of their relatively large signature and low effective hit points, recommending speed and transversal as survival priorities.¹

That warning applies to both configurations. A Micro Jump Field Generator and command bursts add utility, but they do not establish the Magus as heavy tackle.

There is therefore no evidence-based overall winner:

• Shield is the clearer baseline for pilots prioritizing mobile tackle, separation, and skirmish support.
• Armor is the clearer baseline for pilots deliberately accepting scram-range exposure and active-tank management.

Micro Jump Field timing, fragility, and disengagement limits

Both documented PvP fits carry a Micro Jump Field Generator, making displacement part of their utility. That shared module does not erase the distinction between them: the shield fit emphasizes mobility and separation, while the armor fit uses displacement from within a more committed engagement profile.

The source-backed limitation is precise: a micro jump field may provide separation or an escape while leaving a scrammed target behind, but only when the Magus itself is not scrammed. It is not a guaranteed escape from tackle.¹

That limitation should shape engagement decisions. A pilot cannot assume that entering hostile scram control is reversible merely because the ship has a jump field fitted.

Applying the principle to the shield fit

The objective is to retain room to maneuver rather than voluntarily reproduce the armor fit’s close-range commitment.

This does not justify inventing an exact orbit distance or activation sequence. The guide documents neither. Actual positioning must be evaluated against current module attributes, incoming tackle, webs, hostile weapons, terrain, gang movement, and pilot skills.

The practical priority is narrower: do not surrender the mobility on which the fit is based. If hostile control removes that advantage, neither the shield buffer nor the jump field guarantees recovery.

Applying the principle to the armor fit

The armor Magus is designed to enter scram range, so its pilot should establish commitment and exit conditions before closing. Useful planning questions include:

• What objective justifies committing?
• Which hostile ships can apply scrams, webs, or capacitor pressure?
• Is the jump field likely to remain usable?
• Is friendly damage or control available to help create an exit?
• How many booster charges can be spent before withdrawal becomes necessary?
• What changes if the target receives reinforcements?

These are planning prompts, not sourced matchup answers. The available evidence contains no target-by-target engagement guide.

What the evidence does not explain

The PvP material does not document:

• Current spool or activation timing
• Exact current jump-field ranges
• Detailed hostile scram interactions beyond the stated limitation
• Friendly displacement procedures
• Fleet communication standards
• Tested engagement walkthroughs
• Reliable activation sequences
• Current counters or patch-specific edge cases

Check the module’s current in-game attributes and practice displacement mechanics before risking the ship. That is prudent validation, not a claim that practice will make every escape possible.

More broadly, the guide’s fragility warning makes speed and transversal important to both fits. Neither should be flown as though signature, incoming damage, and hostile tackle can be ignored.¹

Active-armor Magus for selected T1 Calm Abyssal sites

The third configuration is separate from the two PvP fits. It is a community fitting page with a narrow documented scope: T1 Calm Electrical, Exotic, Firestorm, and Gamma sites. Dark is marked unsuitable, but the evidence does not explain why, so a mechanical reason should not be invented.²

The page also marks the fit Omega Only. Its recommendation should not be extended to Alpha clones, PvP, higher Abyssal tiers, or other activities.²

Documented Calm Abyssal fit

High slots

• Auto Targeting System I
• Three 125mm Railgun IIs
• Arbalest Compact Light Missile Launcher

Mid slots

• Stasis Webifier II
• Cap Recharger II
• 1MN Y-S8 Compact Afterburner
• Small Cap Battery II

Low slots

• Multispectrum Energized Membrane II
• Two Drone Damage Amplifier IIs
• Small Armor Repairer II

Rigs

• Small Auxiliary Nano Pump II
• Small Explosive Armor Reinforcer II

Documented drone types

• Hobgoblin II
• Hammerhead II
• Hornet II
• Vespa II

Documented cargo

• Caldari Navy Antimatter Charge S
• Spike S
• Javelin S
• Caldari Navy Nova Light Missiles
• Nova Light Missiles
• Nanite Repair Paste

The Abyss Tracker fit author recommends deploying two medium drones and three light drones to use the stated 35 Mbit/s bandwidth. The page presents the configuration for the four named Calm weather types, marks Dark unsuitable, and labels the fit Omega Only.²

How the PvE fit is structured

As a module-based interpretation, the two Drone Damage Amplifier IIs make drones a major part of the damage plan. The three railguns and compact light missile launcher supplement that drone-focused structure, but their presence does not prove a particular total damage output.

The 1MN Y-S8 Compact Afterburner provides propulsion, while the Stasis Webifier II supplies range-control utility. The Cap Recharger II and Small Cap Battery II form the documented capacitor-support package.

For defense, the fit combines a Small Armor Repairer II, Multispectrum Energized Membrane II, Small Auxiliary Nano Pump II, and Small Explosive Armor Reinforcer II. This is an active armor structure, but its module list alone does not establish that the ship can safely tank every room, spawn, or weather variation within the named tier.

The cargo includes several rail charges, two Nova light-missile options, and Nanite Repair Paste. The source does not provide weather-specific ammunition instructions, target priorities, overheating procedures, or room tactics. Carrying the listed ammunition is not evidence for when each charge should be selected.

The proposed active drone flight is two medium drones and three light drones.

Most importantly, the documented recommendation does not establish suitability for:

• Dark weather
• Tiers above Calm
• PvP
• Alpha-clone use
• General-purpose PvE
• Guaranteed completion
• Profitability or consistency

What the published Abyssal statistics do—and do not—prove

The Abyssal page displays fitting, defense, mobility, capacitor, and price figures.

At all skills level 5, the page displays:

• CPU: 223.2 of 262.5 tf
• Power grid: 58.3 of 73.8 MW
• Total EHP: 6.37k
• Capacitor duration: Seven minutes
• Speed: 983 m/s
• Warp speed: 4.5 AU/s
• Align time: 5.19 seconds

Every value above is attributed to the historical Abyss Tracker display. None has been independently recalculated for the current game version.²

The page also displays an approximate price of 34.2 million ISK without the hull and 74.1 million ISK including the hull. Those are historical page snapshots and may differ materially from the current market.²

Module attributes, prices, fitting calculations, skill effects, and the fit itself may have changed. The published figures should not be silently converted into current claims.

Why the displayed DPS is unusable

The page shows zero DPS, but it also shows the railguns and launcher without loaded charges. That makes the displayed damage value unsuitable for evaluating actual output.²

A meaningful damage calculation would need to account for at least:

• Loaded rail ammunition
• Loaded missile ammunition
• Deployed drones
• Pilot skills
• Relevant ship and module bonuses
• Target characteristics
• Damage application rather than paper output alone

Because those inputs are unresolved by the displayed zero, no defensible DPS number can be derived from that field.

The drone-bandwidth inconsistency

The page states that the fit has 35 Mbit/s available drone bandwidth, and its author recommends two medium plus three light drones. At the same time, the statistics display shows zero bandwidth in use.²

That inconsistency suggests the displayed combat state does not represent the proposed active drone flight. It does not disprove the recommendation, but it means the page’s displayed drone-use and damage statistics cannot validate it.

The testing contradiction

The fit title includes “Untested,” while the description says it was tested on stream. No run records, completion results, loss history, timestamps, or weather-by-weather performance data resolve that contradiction.²

The responsible conclusion is that testing status remains uncertain. The page is not enough to call the fit:

• Proven safe
• Consistent across all four recommended weathers
• Profitable
• Reliable
• Independently validated
• Ready for higher tiers

Its statistics are starting points for recalculation, not current guarantees.

Validation checklist before you buy or undock

Each build should be reconstructed and tested before it is treated as usable today. The following process separates a documented baseline from a current recommendation.

1. Rebuild the fit in a current fitting tool

Enter or import every module into an up-to-date fitting application. Do not assume that an older text fit remains legal or fits under present CPU and power-grid limits.

Confirm that:

• Every module still exists under the listed name
• The hull has the required slot layout
• The rigs remain compatible
• The fit is legal under current fitting restrictions
• No module has been renamed, removed, or materially changed

The evidence does not provide a verified current import string for either PvP build. Even when a fitting page offers an export option, the configuration still needs validation against current data.

2. Load all charges and drones

A bare module layout is not a complete combat fit. Add the intended:

• Autocannon ammunition
• Railgun charges
• Light missiles
• Deployed drone flight
• Spare drones
• Skirmish command charges
• Rapid Repair charges
• Navy Cap Booster 400 charges
• Nanite Repair Paste

The PvP guide does not identify autocannon ammunition, so that choice remains unresolved. The Abyssal page lists cargo but does not provide a complete selection procedure for each room or weather.

3. Check fitting margins with the actual pilot

The Abyssal page’s fitting figures assume all skills at level 5.² That is not a substitute for checking the character who will fly the ship.

Verify actual:

• CPU use and remaining margin
• Power-grid use and remaining margin
• Capacitor behavior
• Drone bandwidth and bay use
• Command-burst operation
• Weapon and launcher requirements
• Propulsion and tackle requirements
• Armor or shield module requirements
• Micro Jump Field Generator requirements

The sources provide no minimum or recommended skill plan. Review the relevant hull, weapon, drone, tank, command burst, capacitor, propulsion, tackle, and displacement skills directly.

4. Recalculate combat and navigation statistics

Do not copy unsupported or historical values into a current comparison. Recalculate:

• Loaded turret and missile damage
• Deployed-drone damage
• Combined paper damage
• Damage-application assumptions
• EHP
• Active-repair output
• Capacitor duration
• Capacitor behavior under realistic module use
• Maximum speed
• Align time
• Signature radius
• Tackle and weapon ranges
• CPU and power-grid margin
• Current replacement cost

For the armor PvP fit, test realistic repair and booster operation rather than labeling it cap-stable. For the shield fit, measure mobility under the actual pilot’s skills. For the Abyssal fit, ensure the damage display includes loaded charges and the intended active drone flight.

5. Validate in the intended environment

For the PvP fits, begin with controlled practice rather than treating the layouts as proven roaming fits. Practice movement, tackle transitions, command bursts, capacitor use, drone handling, and Micro Jump Field displacement. Do not turn isolated practice results into broad matchup claims without repeatable evidence.

For the PvE fit, remain inside its documented scope: T1 Calm Electrical, Exotic, Firestorm, and Gamma.² One successful run would not prove consistent performance across every recommended weather. Dark and higher tiers remain outside the supplied recommendation.

6. Record what changed and what happened

When updating one of these builds, record:

• Patch or verification date
• Fitting-tool version or data release
• Complete fitted modules and rigs
• Loaded charges
• Drone inventory and active flight
• Pilot skill assumptions
• Implants, if any
• Calculated statistics
• Test environment
• Opponents or Abyssal weather
• Outcome and observed failure points

This produces a traceable result instead of another undated fit.

7. Leave unsupported gaps unresolved

The supplied evidence does not establish:

• Current import strings for every build
• Current market prices
• Current-patch performance
• Budget substitutions
• Implant requirements
• Detailed matchup guidance
• Abyssal completion times
• Failure rates
• Room priorities
• Higher-tier Abyssal viability
• A mechanical reason Dark is unsuitable

Those gaps should be filled through current testing and stronger evidence, not speculation.

Bottom line: fit the Magus around a narrowly defined job. Use the shield configuration as a starting point for mobile tackle and skirmish support, the armor configuration for deliberate close-range commitment, or the active-armor drone fit only for its documented Calm Abyssal environments.

The PvP guide is dated, while the Abyssal page contains unresolved statistical and testing inconsistencies. Each loadout is therefore a fitting baseline—not a present-day recommendation until it has been rebuilt with current data, checked against the pilot’s skills, loaded correctly, and tested in its stated environment.

Frequently asked questions

Are these Magus builds current and patch-verified?

No. The PvP guide identifies itself as a winter 2023/2024 source and warns that balance or fittings may have changed. The Abyssal page supplies historical fitting statistics but contains unresolved damage, drone-use, and testing inconsistencies.¹²

Treat all three as community-authored baselines. Verify module legality, fitting margins, loaded statistics, price, and performance in a current fitting tool before use.

Is the shield or armor Magus better for PvP?

Neither is established as categorically better.

The shield Magus is the more appropriate baseline for mobile tackle, separation, and skirmish support. The armor Magus is designed for deliberate scram-range commitment, local repair, and more active capacitor management.¹

Choose according to your role, gang needs, desired engagement range, and tolerance for difficult disengagement—not an unsupported overall ranking.

Can a Micro Jump Field Generator always save a tackled Magus?

No. The documented guidance says a micro jump field may provide separation or an escape while leaving a scrammed target behind, but only if the Magus itself is not scrammed.¹

The module is displacement utility, not guaranteed immunity from tackle. Check current mechanics and practice its use before relying on it in combat.

Which Abyssal tiers and weather types does the documented Magus fit support?

Its documented maximum is T1 Calm for:

• Electrical
• Exotic
• Firestorm
• Gamma

Dark is marked unsuitable, but the evidence provides no mechanical explanation for that exclusion. The fit is not documented for higher tiers and is marked Omega Only.²

Which drones should the Calm Abyssal Magus deploy?

The fit author recommends two medium drones and three light drones, using the stated 35 Mbit/s bandwidth. The listed drone types are Hobgoblin II, Hammerhead II, Hornet II, and Vespa II.²