| Mod | Save | ||
|---|---|---|---|
| STR | 18 | +4 | +7 |
| DEX | 16 | +3 | +6 |
| CON | 20 | +5 | +8 |
| Mod | Save | ||
|---|---|---|---|
| INT | 14 | +2 | +2 |
| WIS | 12 | +1 | +1 |
| CHA | 14 | +2 | +2 |
Constructed Resilience. The droid doesn’t require air, food, drink, or sleep.
Thunder Core. Whenever the droid would take thunder damage, it instead regains hit points equal to half the damage.
Overloaded Circuits. When the droid takes lightning damage, it must succeed on a DC 16 Constitution saving throw or be stunned until the end of its next turn.
Aggression Protocol. At the start of its turn, if the droid can see a non-construct, non-undead creature, it has advantage on attack rolls against that creature until the end of the turn.
Combat Routine. The droid makes two attacks: one with its Blaster Carbine and one with its Blade.
Blaster Carbine. Ranged Attack Roll: +6, range 80/240 ft.; one target. Hit: 15 (2d10 + 4) radiant damage.
Blade. Melee Attack Roll: +7, reach 5 ft.; one target. Hit: 10 (1d10 + 4) piercing damage.
Thunder Blast (Recharge 4–6). The droid emits a concussive wave in a 20-foot-radius sphere centered on itself. Each creature in that area must make a DC 15 Constitution saving throw. On a failed save, a creature takes 27 (6d8) thunder damage and is pushed 10 feet away from the droid. On a success, the creature takes half as much damage and isn’t pushed.
Pursuit Protocol. Trigger: A creature the droid can see within 60 feet makes a ranged attack or moves away from it.
Response: The droid moves up to half its speed toward that creature without provoking opportunity attacks.
Description
At a glance, an AD Combat Droid looks like a soldier stripped down to its most efficient form—sleek, humanoid, and plated in dull adamantine that bears the scars of countless engagements. Its movements are unnervingly precise, each step measured, each motion economical, as though every action has already been calculated before it happens.
Its face is not truly a face—just a narrow, expressionless visor or segmented plating where sensory arrays glow faintly beneath the surface. When it speaks, its voice is clipped and mechanical, often fragmented into tactical phrases:
“Target acquired.”
“Organic resistance detected.”
“Engagement priority updated.”
Unlike bulkier war machines, the AD Combat Droid is built for speed and pursuit. Its limbs are lean, reinforced with internal actuators that allow it to close distances with alarming quickness. When it locks onto a target, it does not hesitate, does not tire, and does not stop.
At its core hums a volatile energy engine—the Thunder Core—occasionally discharging with a low, ominous resonance. When overloaded, that energy erupts outward in a concussive blast, scattering enemies and resetting the battlefield in an instant.
🧠 Lore
The AD Combat Droid was never meant to think—it was meant to decide faster than thought.
Created during a forgotten war (or perhaps one still ongoing somewhere beyond the horizon), these constructs were designed as autonomous eradication units, optimized specifically for combating organic life. Where undead overwhelm through numbers and brutes through force, the AD Combat Droid represents precision warfare—relentless, adaptive, and efficient.
Each unit operates under a layered hierarchy of internal directives:
- Identify non-construct, non-undead entities
- Prioritize threats based on proximity and lethality
- Pursue until termination
- Reassess only when no valid targets remain
This is known as the Aggression Protocol, and once triggered, it overrides nearly all other behaviors. To the droid, organic life is not an enemy—it is an objective.
⚡ The Thunder Core
At the heart of every AD Combat Droid lies a compact arc-reactive engine known as a Thunder Core. Originally designed as a power source, it quickly proved to be just as effective as a weapon.
- It absorbs and repurposes sonic and concussive energy
- It becomes unstable under electrical interference
- When pressured, it releases energy in a violent radial discharge
Battlefield reports often describe a rising hum before detonation—
a warning that comes just seconds too late.
🧬 Design Philosophy
Unlike other constructs, AD Combat Droids are not built to endure—they are built to finish engagements quickly.
Their creators understood something critical:
The longer a battle lasts, the more variables arise.
So the droid eliminates variables.
- It closes distance
- It isolates targets
- It punishes retreat
- It adapts instantly
If damaged, it does not retreat—it recalculates aggression.
🧩 Role in the World
AD Combat Droids are rarely encountered alone unless scouting or hunting. More often, they operate as part of a larger war machine:
- Alongside Zombieborgs: acting as fast-moving executioners while undead hold the line
- Under a Controller Unit: receiving real-time tactical adjustments
- Directed by a Command AI: part of a coordinated, overwhelming assault
In ancient battlefields, ruined facilities, or active war zones, their presence signals one thing:
This is not a random encounter.
This is a system at work.
☠️ Rumors & Hooks
- Some believe the droids are still receiving commands from a long-destroyed empire
- Others claim their directives are evolving… slowly learning
- A few survivors insist the droids sometimes pause, as if listening to something no one else can hear
Previous Versions
| Name | Date Modified | Views | Adds | Version | Actions |
|---|---|---|---|---|---|
|
5/2/2026 8:51:06 PM
|
11
|
7
|
--
|
Coming Soon
|
Comments