Guide

Game minion and summon systems explained

Harbor Outpost's engineer class shipped with three deployable drones, two auto-turrets, and a remote mine layer. Closed-beta telemetry showed the fantasy worked: engineers cleared outpost defense waves 34% faster than melee classes. Server profiles told a different story. A single engineer in a four-player session could field eleven active entities; pathfinding and perception queries for those units consumed 38% of simulation CPU. Boss add phases melted because drones soaked aggro while players bursted objectives. The refactor introduced hard summon caps per owner, shared population budgets per encounter, behavior stacks with explicit retreat states, and aggro contribution caps so tanks kept their role. Engineer clear time dropped only 9% while server frame time variance fell by half.

Minions and summons are player-owned combat entities that multiply agency without multiplying input bandwidth. They differ from story companions (persistent, narrative-weighted) and from authored enemy waves (director-controlled). This guide covers taxonomy, ownership and authority, spawn pipelines, AI behavior stacks, targeting and aggro contribution, balance levers, multiplayer sync, the Harbor Outpost engineer refactor, a technique decision table, pitfalls, and a production checklist.

Taxonomy: minion, summon, deployable, and pet

Teams blur labels in design docs. Clear categories prevent scope creep and help engineers size systems correctly:

Type	Player control	Typical lifetime	Examples
Combat minion	Indirect (stance orders)	Until death or dismiss	Skeleton army, spirit wolves, zerglings
Timed summon	Ability-triggered	Fixed duration or charge bar	Ultimate clone, elemental totem
Deployable	Placement on ground	Until destroyed or zone exit	Sentry turret, healing beacon, trap
Pet (combat)	Often direct or hybrid	Persistent across zones	Hunter pet, druid companion

Each category shares a core pipeline (spawn, own, perceive, act, die) but differs in caps, networking cost, and how much companion-style personality players expect. Pets and story companions overlap; if a pet has quest dialogue, treat social AI separately from combat minion logic.

Ownership, authority, and spawn pipeline

Who owns the entity?

Every summon needs an OwnerId (player or squad), a SpawnSource (ability ID, item, talent), and an AuthorityMode:

Server authoritative — required for PvP and competitive PvE. Server simulates position, targets, and damage.
Client cosmetic — only for single-player or non-interactive VFX familiars. Never let client damage rollups reach loot tables.
Hybrid — server validates targets; client interpolates motion. Common in co-op horde modes with tight bandwidth.

Spawn validation checklist

Before instantiating, the spawn service should reject or queue requests that fail any gate:

Owner under personal cap (e.g. max 3 active drones).
Encounter under global summon budget (e.g. max 24 player-owned units).
Valid navmesh / placement ray (no spawning inside geometry).
Line-of-sight or range rule for deployables.
Cooldown and resource cost consumed atomically on server.

Pool minion actors like projectiles. Spawning from scratch allocates components, registers perception listeners, and allocates path queries — the hidden cost that sank Harbor Outpost profiling.

AI behavior stacks

Minions need simpler brains than boss AI but more structure than “attack nearest.” A behavior stack is a priority-ordered list of states evaluated each tick:

Priority	State	Entry condition
1	Forced command	Player pinged target or stance button pressed
2	Retreat / leash	Distance from owner > leash radius or HP < threshold
3	Defend owner	Owner took damage within last N seconds
4	Attack assigned target	Valid hostile in weapon range
5	Follow formation slot	Default idle when no threats

Implement perception with the same layers as enemies but narrower queries: minions rarely need full-map awareness. A cone or radius check every 200–400 ms beats continuous perception scans on twelve units. Stagger evaluation frames across minions so all drones do not retarget on the same tick.

Leash and lifetime rules

Without leashes, minions pull entire camps across the map. Standard patterns:

Soft leash — speed boost back toward owner after distance threshold; combat continues.
Hard leash — despawn or teleport at edge; used for deployables tied to a room.
Timed expiry — visible countdown; prevents indefinite accumulation between pulls.
Zone binding — auto-dismiss when owner leaves encounter volume (common for boss arenas).

Targeting, aggro, and readability

Minions participate in threat systems unless you explicitly exclude them. Define per minion:

Threat multiplier — 0.5x for pets avoids stealing tank aggro; 0x for pure cosmetic familiars.
Target priority class — can bosses ignore summons until players engage?
Damage attribution — XP and kill credit flow to owner; loot rules may differ in MMOs.

Players must read what minions are doing. Use silhouette size caps, team-colored outlines, and distinct attack VFX. If twelve identical drones clutter the screen, readability collapses even when balance is fine. UI counters (“Drones 2/3”) reduce accidental over-summon.

Balance levers without gutting the fantasy

Nerfing summon damage alone often pushes players to abandon the class. Tune across multiple axes:

Lever	Player feel	Ops impact
Personal cap	Army fantasy capped at “small squad”	Linear CPU savings
Minion HP pool	Fragile pets need positioning skill	Fewer sustained path queries
Ability cooldown	Burst windows, not permanent uptime	Predictable load spikes
Damage efficiency	Owner must contribute; pets assist	Shorter time-to-kill on adds
Boss immunity phases	Summons still clear trash; boss stays a test	Prevents skip strats

Compare DPS contribution against wave budgets: if player summons replace an entire trash pack's intended difficulty, either raise wave health or lower summon efficiency until clear times match design targets.

Multiplayer sync and bandwidth

Each active minion is another networked entity. Mitigations:

LOD for AI — distant minions tick at 5 Hz; owner-adjacent at 20 Hz.
Compressed state — send stance enum + target ID, not full path waypoints every frame.
Interest management — replicate summons only to players within encounter radius.
Deterministic seeds — cosmetic idle animations driven locally from spawn seed.

In large-scale PvP, consider converting summons to ability-bound “spirit strikes” (no persistent actor) when population exceeds a threshold. Document the downgrade so players understand why their skeleton horde became a single AoE in battlegrounds.

Harbor Outpost refactor: engineer deployables

Before refactor, engineers could place two turrets and three drones with no encounter budget. Drones used full enemy-grade perception at 60 Hz. Tanks reported zero threat generation because drones out-DPSed them on adds.

After:

Personal cap: 2 deployables + 1 drone (3 total combat entities).
Encounter budget: max 8 player-owned units across the party.
Drone perception throttled to 5 Hz with 12 m radius.
Threat multiplier 0.35 on drone damage; turrets generate 0 threat.
Hard zone dismiss on boss arena entry; soft leash 25 m elsewhere.
Object pool warmed at zone load for 32 minion slots.

Playtest surveys showed engineer satisfaction rose once players understood caps as “tactical loadout” rather than arbitrary nerfs. UI telegraphs cap and leash on the ability bar.

Technique decision table

Approach	Best when	Weak when
Persistent combat minions	Class identity (necro, engineer), solo ARPG	High player count, tight CPU budgets
Timed summons	Burst cooldown fantasy, clear power windows	Players want always-on companions
Ground deployables	Area denial, defensive objectives	Fast-moving mobile combat
Narrative companions	Story escorts, relationship systems	Swarm combat, competitive balance
Director-spawned allies	Scripted set pieces, AI director pacing	Player build customization
Ability-only spirits (no actor)	Mass PvP, mobile SKU performance	Visual fantasy of owning an army

Common pitfalls

No encounter budget — four summoners spawn forty units in one boss room.
Minions use boss-grade AI tick rates — death by a thousand path queries.
Aggro vacuum — tanks idle while drones tank everything.
Leashless world pulls — minions drag half the zone into town.
Unreadable swarms — identical meshes obscure telegraphed boss attacks.
Client-authoritative damage — exploit summon multiplication in PvP.
Forget dismiss on disconnect — orphaned turrets block progression triggers.
Pool cold start — first summon spike causes frame hitches.

Production checklist

Define taxonomy (minion vs deployable vs pet) in design wiki.
Implement OwnerId, SpawnSource, and server authority on all combat summons.
Enforce personal cap and encounter-wide summon budget at spawn gate.
Warm object pools per zone; profile spawn/allocation cost.
Ship behavior stack with leash, retreat, and forced-command priorities.
Throttle perception frequency; stagger retarget ticks across units.
Configure threat multipliers and boss target-priority rules.
Add UI cap counter and leash warning before players hit hard dismiss.
Test four-player engineer squads against server frame budget.
Document PvP downgrade path if summons convert to ability-only effects.

Key takeaways

Minions multiply simulation cost linearly — caps and budgets are design tools, not afterthoughts.
Behavior stacks with explicit leash and retreat states prevent world pulls and idle deaths.
Aggro contribution must be tuned so summons assist without replacing tanks and threat gameplay.
Server authority and pooled spawns keep co-op and PvP fair under load.
Readability and UI telegraphing matter as much as DPS spreadsheets for player satisfaction.