- Gridlords async PvP pits your castle against other players' layouts in automated battles without simultaneous play.
- Defense matters most: your castle must survive attacks with no direct control during combat.
- Focused unit packages outperform broad, unfocused unlocks in almost every matchup.
- Review each battle result and change one priority at a time to improve steadily.
- Early Access balance can shift strategy value quickly, so keep builds flexible.
How Gridlords Async PvP Works
Gridlords, developed by Sphere Studios and published by Goblinz Publishing, entered Steam Early Access on October 7, 2026 as a fantasy pixel-art castle autobattler. The asynchronous PvP system means you build and defend a castle while other players attack your layout — and you raid theirs — without needing both players online at the same time. Battles resolve automatically based on the castles, units, heroes, and upgrades each side has prepared.
Because combat is automated, success in Gridlords async PvP comes from preparation rather than reflexes. Every placement decision, upgrade order, and unit unlock you make becomes your "input" for battles that happen without you.
Video Highlights:
- Official first look at castle building and asynchronous battles
- Shows the pixel-art aesthetic and grid-based layout system
- Demonstrates how automated combat resolves between castles
| Async PvP Concept | What It Means | Strategic Impact |
|---|---|---|
| Automated battles | Combat resolves without direct control | Layout quality decides outcomes |
| Castle defense | Your grid defends when offline | Defense must work unattended |
| Asynchronous raids | Attack castles of other players | Study opponent layouts before committing |
| Grid placement | Buildings and units occupy fixed tiles | Positioning errors are hard to undo |
| Upgrade timing | Stronger castle over time | Sequence upgrades around your win condition |
Treat async PvP as a preparation game. If a defense fails, the fix is almost always in your grid layout, unit package, or upgrade order — not in reaction speed.
Defensive Layout Principles
A strong defense protects its most important structures, buys time for damage dealers to work, and leaves room for upgrades as the grid expands. Automated battles reward consistent layouts rather than last-second adjustments.
Establish the Frontline
Place durable units and defensive structures where enemy pressure arrives first. The frontline absorbs the opening impact without exposing your highest-value damage or support pieces. Avoid putting fragile damage dealers on the first contact line just because they have higher attack values.
Protect Vulnerable Structures
Identify buildings that provide damage, economy, or key upgrades but cannot withstand direct pressure. Keep high-value support in the inner grid and place ranged damage on protected sides rather than exposed corners.
Upgrade the Failure Point
Find the element that causes battles to fail first. If the frontline collapses instantly, improve durability or reinforcement. If enemies reach your core while the frontline stands, improve damage, range, or targeting support.
Adapt Against Attack Patterns
Review where enemy pressure concentrates. Dense attacks favor compact area damage and layered defense; attacks that bypass the frontline require protected secondary positions and flexible coverage.
| Defense Layer | Role | Placement Guidance | Common Mistake |
|---|---|---|---|
| Frontline | Absorb first contact | Compact front row, reinforcement space behind | Fragile units on the front line |
| Damage core | Eliminate attackers | Protected positions behind the front | Damage at exposed corners |
| Economy buildings | Sustain development | Inner grid, away from attack paths | Economy on outer edges |
| Defense structures | Shield key buildings | Cover the most important structures first | Spreading protection evenly |
Grid space is limited. Placing structures carelessly can block future merges or make a stronger layout impossible — plan tiles before filling them.
Offense and Build Archetypes
When attacking, your goal is to exploit the opponent's weakest layer. When defending, your goal is to have no exploitable layer. These three build archetypes define how most async PvP castles take shape.
Aggressive Pressure
- Fast development and early offense
- Punishes slow, greedy openings
- Forces opponents to react
- Weak if the first push fails
Defensive Scaling
- Protected growth and late-game power
- Stable against uncertain opponents
- Layered defense around the core
- Can lose initiative to fast aggression
Balanced Progression
- Flexible economy, production, and defense
- Adapts after seeing the opponent
- Forgiving for new players
- Weaker than specialized builds at peak timing
Aggressive builds should maintain enough economy and defense to keep operating if the first pressure window does not decide the match. Defensive builds must protect their economy, since losing resource structures early delays the entire scaling plan. Balanced builds work best when you keep open grid space for later merging and adaptation instead of committing every tile immediately.
| Archetype | Hero Priority | Unit Package | Item Focus |
|---|---|---|---|
| Aggressive Pressure | Early combat impact, unit tempo | Frontline pressure plus converting damage | Immediate combat reliability |
| Defensive Scaling | Consistency, survivability | Durable units plus a reliable damage source | Resilience and sustain |
| Balanced Progression | Flexible, no extreme requirements | Frontline, damage, and utility mix | Broadly useful coverage |
Balance changes during Early Access can quickly shift the value of aggressive openings, defensive scaling, and specific unit packages. Re-test established compositions after each patch.
Unit Packages and Synergies
Focused unit packages are consistently stronger than broad, unfocused unlocking. A small group of complementary units — a frontline, a damage source, and a utility or defensive option — is easier to upgrade, easier to produce, and easier to evaluate after each battle.
Follow these principles when assembling your package:
- Cover distinct battlefield roles instead of stacking options that solve the same problem
- Avoid unlocking more units than your economy can support
- Upgrade units you expect to use across multiple matches
- Adjust the package after observing how opponents defend
Hero choice should reinforce the package. Frontline-oriented heroes suit castles that collapse early, damage-oriented heroes help compositions that survive but cannot finish fights, and utility-oriented heroes shine when positioning and timing decide results.
| Unit Role | Function | Synergy Partner |
|---|---|---|
| Frontline | Absorb damage, hold position | Ranged damage behind the front |
| Damage dealer | Convert survival into kills | Utility that extends engagements |
| Utility / Control | Interrupt attack patterns | Concentrated damage windows |
| Defensive support | Protect fragile structures | Durable frontline in front |
A hero, buildings, items, and units should all point at the same win condition. Isolated upgrades rarely win async PvP battles.
PvP Improvement Checklist and Mistakes
Improvement in Gridlords async PvP comes from disciplined iteration: review each result, identify whether the problem was economy, placement, unit composition, or timing, and change one priority at a time.
Async PvP Readiness Checklist:
- Economy and production buildings are protected inside the core
- Frontline covers the most likely attack path
- Unit package has distinct roles, not duplicates
- Upgrades target the current failure point
- Open grid space reserved for merges and adaptation
- Battle results reviewed with one change per iteration
| Common Mistake | Why It Fails | The Fix |
|---|---|---|
| Filling the entire grid immediately | Blocks upgrades, merging, and adaptation | Keep open space for future plans |
| Unlocking every unit type | Spreads resources and upgrades thin | Build around a focused package |
| Ignoring defense while scaling | Strong theory, collapsed castle | Protect the core before greedy upgrades |
| Rebuilding after one loss | Hides the real cause of failure | Diagnose economy, placement, units, or timing |
| Spreading upgrades evenly | Creates several underpowered layers | Concentrate on the failure point |
Changing your whole build after a single loss makes it impossible to learn what actually failed. Adjust one variable, then battle again.
FAQ
Q: What is Gridlords async PvP?
Gridlords async PvP is an asynchronous player-versus-player system where your castle defends and attacks automatically. You prepare layouts, units, heroes, and upgrades in advance, and battles resolve without direct control or both players being online simultaneously.
Q: Do I need to be online when my castle is attacked?
No. Because battles are asynchronous and automated, your castle defends based on how you built it. This is why defensive layout quality — frontline placement, protected structures, and upgrade timing — matters more than reactions.
Q: What is the best build for async PvP?
There is no single best build, especially during Early Access. Aggressive pressure, defensive scaling, and balanced progression all work when built coherently. The strongest approach is aligning your hero, buildings, items, and unit package around one clear win condition.
Q: How many units should I unlock?
Unlock a small, focused package covering distinct roles — typically a frontline, a damage source, and a utility or defensive option. Broad unlocking spreads upgrades thin and weakens production planning.