- Gridlords async PvP pits your castle against other players' layouts in automated battles without live opponents
- Your castle fights alone: layout, units, and upgrades must work without direct control
- Focused unit packages outperform scattered unlocks in both attack and defense
- Defense wins seasons: protect economy and production structures before greedy scaling
- Review every battle result and change one priority at a time
How Gridlords Async PvP Works
Gridlords, the fantasy pixel-art castle autobattler from Sphere Studios and Goblinz Publishing, centers its competitive mode on asynchronous PvP. You never fight a live opponent in real time. Instead, your developed castle attacks another player's defensive layout, and other players raid yours while you are away. Both sides are resolved by automated battles, which means every decision you make in the building phase is the battle itself.
The core implication is simple but demanding: your grid layout, defensive structures, unit composition, and Lord Ability timing all have to function without your input. A castle that requires mid-battle micromanagement is a castle that loses.
Video Highlights:
- See how automated castle battles resolve in the official Early Access trailer
- Overview of grid-based building, heroes, and unit deployment
- Visual reference for castle layouts discussed in this guide
The Three Pillars of Async Battling
| Pillar | What It Governs | Key Decision |
|---|---|---|
| Castle layout | Where economy, production, and defense sit on the grid | Protect the core, leave upgrade space |
| Unit package | Which units you unlock and upgrade | Small complementary roles over broad access |
| Development pace | Aggressive, defensive, or balanced scaling | Match hero, buildings, and items to one win condition |
In async PvP you are building a machine, not commanding an army. Evaluate every placement by asking: does this still work when I am not watching?
Attack Strategy: Reading and Breaking Castles
Attacking in Gridlords is about analyzing an opponent's layout before committing your unit package. Since battles are automated, your preparation does all the work.
| Opponent Pattern | Weakness | Recommended Counter |
|---|---|---|
| Dense frontal wall | Slow coverage on flanks | Bypass pressure plus protected secondary damage |
| Exposed economy on outer edge | Fragile high-value structures | Early pressure units aimed at the core |
| Even, unfocused defense | No layer is strong | Concentrated damage window with a single push |
| Heavy defensive scaling | Weak early tempo | Aggressive openings that arrive before upgrades land |
Attack Preparation Flow
Scout the layout
Identify where the enemy frontline, damage, economy, and support structures sit. Look for the weakest covered path rather than the strongest entry point.
Match your package
Choose a unit package that targets the identified weakness: durable units into weak fronts, burst damage into exposed cores, utility into predictable patterns.
Time the push
Aggressive plans must connect before the opponent's scaling finishes. If you cannot end it early, maintain enough economy to keep operating after the first window fails.
Review the result
After each attack, determine whether the failure point was composition, timing, or placement. Change one variable at a time before the next attempt.
Do not change your entire build after a single loss. Most failed attacks stem from one specific gap: wrong target priority, mistimed push, or a unit package solving a problem the opponent does not have.
Castle Defense: Layouts That Survive Alone
Defense is the more permanent half of async PvP. While attacks are chosen, your castle sits exposed to every raider, so layout quality compounds over time.
Defensive Placement Principles
| Principle | Rule of Thumb | Example |
|---|---|---|
| Establish the frontline | Durable units and defense meet pressure first | Compact front row with protected damage behind |
| Protect vulnerable structures | High-value support in the inner grid | Ranged damage on protected sides, not corners |
| Upgrade the failure point | Fix what collapses first, not everything evenly | Stabilize the front before scaling damage |
| Adapt to attack patterns | Shift coverage toward the exposed side | Keep a central core, reposition support outward |
Order your development as: economy foundation, basic unit production, protection for key structures, then focused upgrades. Expansion and structure merging come last, only after the core is stable.
Defending Against Common Attack Patterns
Dense Assaults
- Layered, compact defense
- Area damage on likely paths
- Reinforce the first contact line
Flank Bypass
- Protected secondary positions
- Flexible coverage, no dead corners
- Avoid committing everything to one wall
Early Rush
- Enough day-one defense
- Durable frontline units early
- Delay greedy upgrades until covered
Placing fragile damage dealers on the first contact line because of higher attack values is one of the most common defensive errors. Damage belongs behind the front, not on it.
Heroes, Lord Abilities, and PvP Synergy
Your hero and Lord Ability choices shape how the castle performs in automated battles. Since opponent information in async PvP may be limited, flexible choices tend to outperform narrow specialists.
| Role | Best When | PvP Application |
|---|---|---|
| Frontline hero | Castle collapses early | Absorbs opening impact, buys time for damage |
| Damage hero | Defense survives but cannot finish | Converts stable fronts into decisive wins |
| Utility hero | Positioning and timing decide results | Interrupts the attack pattern that threatens you most |
| Flexible hero | Opponent unknown | Supports both pressure and defense adaptably |
Use Lord Abilities to reinforce your composition's main win condition. Defensive effects belong before the frontline is overwhelmed, offensive effects should support a concentrated damage window, and control effects should interrupt the pattern that most threatens the castle. Waiting until the frontline is already lost wastes the ability entirely.
Build around coordination, not isolated upgrades. The hero reinforces the castle plan, buildings support the unit package, and items cover the weakness created by your chosen pace.
Pre-Battle Checklist
Before Every Ranked Push:
- Confirm economy and production buildings sit inside the defended core
- Check defensive coverage against likely attack paths, including flanks
- Verify your unit package covers frontline, damage, and utility roles
- Match hero and Lord Ability timing to the current win condition
- Set one clear adjustment priority for reviewing the next battle result
Gridlords launched into Steam Early Access on October 7, 2026, and balance changes are frequent. Unit costs, defensive structure strength, and hero values can shift between patches, so re-test established compositions after each update and follow the official Steam community discussions for current values.
FAQ
Q: What does async PvP mean in Gridlords?
Asynchronous PvP means battles are automated and resolved against other players' castle layouts without live, real-time opponents. You attack prepared defenses, and other players raid your castle while you are offline, so your layout and unit composition must function without direct control.
Q: Is offense or defense more important in async PvP?
Defense is the more permanent investment because your castle stays exposed to every raider between sessions. A stable defense protects your economy and production core, which in turn funds stronger attacks. Build defense first, then specialize your attack packages.
Q: How many units should I unlock for PvP?
A small, focused package of complementary units performs more consistently than broad unlocking. Aim for a frontline option, a damage option, and a utility or defensive option, then upgrade the units you expect to use across multiple matches.
Q: Do Gridlords balance changes affect PvP strategy?
Yes. As an Early Access title, Gridlords receives balance adjustments to units, heroes, structures, and progression. Re-test established compositions after each patch and prioritize flexible layouts that remain useful across changes.