Repterra Base Defense Guide: Economy, Power, and Wave Recovery

Repterra does not usually break a colony at the first wall. It breaks the budget behind that wall. A perimeter can look finished while the power reserve is gone, the army is committed to one lane, and the next production building has already spent the money needed for repairs. The practical objective is to keep four things alive together: income, power headroom, time-to-kill at each approach, and a mobile reserve.

This guide is written for Repterra 1.0, released on August 20, 2026. The current game has three factions, seven replayable maps, permanent unlocks, a late-game Volcano map, and systems for breeding, taming, riding, heroes, and superweapons. The two supplied gameplay recordings are useful visual case studies, but both show Early Access version 0.14.15 from June 4. Version 1.0 added the Electric Faction and received substantial balance, interface, and quality-of-life work after those recordings. Use the live Codex, tooltips, adjusted runtime statistics, and wave display for exact costs and effects.

Start with the loss condition, not the build menu#

Before placing anything, identify what the map actually requires you to preserve and what ends the run. Then locate the next attack timer, current wave state, unexplored approaches, and the resource that is closest to its limit. A build is not safe because every button is available. It is safe when the next wave can damage the outer line without shutting down the economy or reaching the protected objective.

Use four readiness questions whenever the game is paused:

1. Economy: Can current income replace a destroyed wall section and the units stationed behind it?
2. Power: Is there enough unused capacity for the defenses and production already planned?
3. Coverage: Does every revealed approach have something that delays enemies and something that kills them?
4. Reserve: Is any useful force free to move, or has every unit been locked into a static line?

A single “no” gives the next construction order. This prevents the common mistake of buying the most exciting unlock while the colony is one breach or one power warning away from collapse.

Map the lanes before the colony chooses them for you#

Repterra maps use water, forest, rock, roads, bridges, and open ground to create attack lanes. Do not draw a large perimeter around fog and assume the border is closed. Send a cheap or mobile scout far enough to reveal where a horde can approach, where flyers or water units ignore a land choke, and where a wall would create a long firing lane instead of a blind corner.

Mark each approach as one of three jobs:

• Main lane: the broad route that needs layered delay and sustained damage.
• Leak lane: a narrow side route that needs detection, a cheap stop, and quick reinforcement.
• Non-wall threat: air, water, artillery, or another attacker that makes a solid ground barrier insufficient.

The mini-map is the fastest audit. If the base is expanding beyond the rectangle you routinely inspect, the new district has become a defensive obligation. Finish its connection, power, and retreat route before opening another edge.

Make the first economy loop pay for two defenses#

Early income has to fund the front that is visible and the front that has not been revealed yet. Build the smallest dependable loop that supports population, production, power, and one combat group, then let it run long enough to create a repair reserve. Expanding every resource patch at once produces a larger colony but also a longer wall, more exposed workers or buildings, and more travel time for the army.

Price an expansion as a complete package:

1. the economic or resource building you want;
2. the power and capacity it requires;
3. the path or territory needed to connect it;
4. the wall, tower, or mobile force required to hold that new edge;
5. one affordable replacement after the first serious attack.

If the colony can pay only the first item, the expansion is not affordable. Keep the resource node outside the wall until the whole package can be defended, or treat it as an expendable outpost whose loss will not switch off the core.

Dense economic districts are easier to protect than a ribbon of buildings following every deposit. Leave movement space between the economy and the wall. That space is not wasted: it is where reinforcements assemble, damaged units retreat, and an inner barrier can be added without demolishing the production line.

Build a three-ring base instead of a decorative perimeter#

A single continuous fence is a map border, not a defense plan. A useful base has three rings with different jobs:

• Outer delay: cheap walls, gates, terrain, or expendable positions that keep the horde exposed.
• Kill zone: towers, ranged units, abilities, and clear sight lines that do the actual damage.
• Inner keep: a short fallback around irreplaceable objectives, power, and core production.

Do not align the outer and inner gates. A straight opening lets the same push cross both rings before the reserve can arrive. Offset the second entrance, leave room to turn inside the first line, and keep important buildings out of the direct path. On wide ground, several short compartments are safer than one enormous enclosure because a breach opens one district rather than the entire economy.

Upgrade the section that is taking contact, not every wall segment merely to make the perimeter uniform. The rear edge needs warning and a fallback; the active choke needs durability. Visual symmetry is expensive and does not shorten the time enemies spend under fire.

Keep power headroom for the moment the wave arrives#

Power is a combat resource because construction pressure peaks just before and just after an attack. The Part 2 recording shows an insufficient-electricity warning while a mature base is still fighting. That warning is more useful than another speculative tower: it says the plan has consumed capacity faster than the grid can support it.

Set a simple rule. The last safe slice of power is reserved for emergency construction and recovery, not routine expansion. When the warning appears, pause the production queue, identify the newest large consumer, and restore headroom before adding another powered defense. If a generator or grid building is exposed, protect a second supply route or place replacement capacity inside the inner ring.

Version 1.0 exposes adjusted runtime statistics more clearly than the supplied recordings. Read those live values after faction bonuses, promotions, mounts, and upgrades. A plan based on the shop card rather than the running unit can misprice both power and damage.

Turn the attack warning into a repair schedule#

The direction marker is not merely a reason to move the army. It starts a short maintenance sequence. First inspect the named approach on the mini-map. Then trace the route backward from the outer wall to the core. Anything that would let the horde skip the kill zone is a higher priority than a new technology.

Readback	Immediate action	Do not spend on yet
Wall incomplete or damaged	Close the lane and restore the first delay layer	Remote economy expansion
Power margin near zero	Add protected capacity or cancel a nonessential consumer	Another powered tower
No mobile reserve	Pull one group off the quietest front	A second static line of the same unit
Air or water contacts visible	Verify a weapon can target that threat	More ground-only wall depth
One choke repeatedly fails	Widen the kill time with a bend, compartment, or fallback	Uniform upgrades around the whole map

After these checks, place optional upgrades. This order converts the warning into a deadline and stops a research purchase from stealing the only materials that can seal a breach.

Place damage where enemies must remain exposed#

A tower beside a wall is not automatically useful. Ask how long targets stay inside its effective area and what blocks its attacks. Place sustained damage behind the longest approach, not at the first tile enemies touch. Use bends, terrain, and staggered wall segments to keep a mass moving laterally across overlapping fire rather than hitting every defense at once.

Separate three roles. The front line delays. The damage line kills. The reserve answers whatever bypasses both. When all three are placed on the wall, area attacks or a single breach can remove the entire response. Keep expensive ranged pieces far enough back to survive the first collapse, but close enough that they begin firing before the horde reaches the gate.

Current 1.0 factions have different tools, so test coverage in the live interface. Check whether a weapon needs line of sight, whether it can engage air or water, and whether its adjusted range reaches the intended path. Official updates changed these rules during Early Access; remembered behavior from an older video is not a safe measurement.

Use mobile units as a reserve, not fence decoration#

Heroes, riders, tamed dinosaurs, and regular mobile units earn their value by changing fronts. A unit parked permanently behind a tower is functioning as an expensive piece of scenery. Keep a reserve near a central road or open rally area, then move it only after the attack direction is confirmed.

Give the reserve three assignments in order:

1. intercept anything that bypasses the wall or approaches from an unplanned medium;
2. focus the densest mass at the active breach without blocking tower fire;
3. chase survivors only after the core and power network are stable.

Upgradeable heroes respawn, but a respawn is not free time during a wave. Use their active abilities where they preserve the wall or buy a repair window. Mounted combinations can add specialized abilities; choose the pairing that repairs a missing defensive role instead of mounting every available dinosaur for spectacle.

Let faction identity change tools, not readiness tests#

Version 1.0 includes three factions with distinct units, perks, and heroes. Their economies and defensive answers differ, but the four readiness questions do not. A faction is not prepared until it has an affordable replacement, power headroom, coverage for the revealed threat types, and a reserve.

• Electric technology: use current Tesla, shock, and grid statistics to decide how much of the kill zone depends on power. Do not copy Early Access stacking or line-of-sight assumptions.
• Primal systems: breeding, taming, lookout, and riding can create flexible answers, but the breeding chain still needs a protected economy and time before a wave.
• Feral systems: nests, recycling, or massed units can turn battle debris and numbers into pressure. Keep lanes open so friendly mass does not trap the response behind its own wall.

The current Codex is the deciding source for exclusivity and costs. The official V0.16 update moved some buildings to faction-specific ownership and added or reworked several units before 1.0. If an older recording shows a building under a different faction, treat that as history rather than a workaround.

Spend each quiet interval in a fixed repair order#

Downtime becomes inefficient when the camera jumps between unfinished ideas. Sweep the base in the same order after every attack:

1. confirm the enemy counter has reached zero and no flyer or water unit remains off-screen;
2. repair the active choke and close any accidental path;
3. replace lost damage, detection, or anti-air coverage;
4. restore the grid and rebuild a protected reserve of resources;
5. replace the mobile force;
6. only then claim new ground, research, breed, or add a luxury upgrade.

This order deliberately delays expansion. A damaged base can look calm because the previous wave is gone, but it is carrying debt into the next timer. Pay the defensive debt first.

Recover from a breach without feeding the whole colony#

When the outer ring opens, do not rebuild the same tile under the full mass. Pause, select the reserve, and decide what can be abandoned. A resource outpost is cheaper than the core. A row of houses is cheaper than the only power supply. Pull units behind the next corner, close an inner choke, and make the horde turn while ranged damage continues.

Use this recovery sequence:

1. Contain: seal the shortest inner path to the protected objective.
2. Preserve: move mobile damage away from the collision so it can keep firing.
3. Power: cancel or disable nonessential construction if the grid is failing.
4. Thin: spend hero abilities or superweapons where the mass is most compressed.
5. Rebuild later: restore the outer ring only after the enemy counter and mini-map agree that the wave is over.

A breach is also evidence. If the wall vanished while the towers survived, add delay. If enemies stood at the wall while damage was too low, improve the kill zone. If air or water entered behind it, change coverage. If every defense worked until electricity ran short, fix the grid. Change the failed layer instead of duplicating the whole base.

Read the supplied videos as failure analysis#

The two public videos were independently verified as BMG OYUN’s Repterra Part 2 and Part 3 uploads. They correspond to the supplied local files and show useful examples of dense economic growth, wide perimeters, directional attack lines, upgraded defenses, and extremely large swarms. They are embedded because their title, channel, duration, and relevance were verified.

Part 2 shows a mature green-map colony using walls, towers, gates, power infrastructure, housing, and broad production. Near the end, multiple dinosaur groups are still being cleared while the interface reports insufficient electricity. The lesson is not to copy that building count. It is to notice that a colony can be physically large and still be missing operating margin.

Part 3 shows a snow-and-water map growing from a compact core into several defended districts. It demonstrates why frozen lakes, open water, and separated land approaches need different answers. Its late swarm pushes through developed territory while a later wave remains scheduled. The recording ends on a loading screen without a victory or map-completion readback.

Both videos display version 0.14.15 and were uploaded on June 4, 2026. They predate the V0.16 Electric Faction update and the August 20 release of 1.0. Use them to study spacing, lane pressure, repair timing, and failure signals. Do not use them as permanent build orders, exact faction rosters, current costs, or proof of a completed map.

Confirm a real clear before leaving the map#

A quiet screen is not the finish line. Before counting a map, difficulty, or achievement as complete, let the final wave resolve and read the result screen or returned map state. Check the wave counter, objective status, remaining-enemy indicator, and unlock or score readback. A save load, fade, or video ending cannot substitute for that confirmation.

If the map is still active, save the information that matters for the next attempt: which lane broke first, whether the grid entered deficit, what threat bypassed the wall, and which reserve arrived too late. Those four facts are more reusable than a screenshot of the final building layout. Rebuild the failed layer, keep the successful layers, and let the next wave test one change at a time.

Official game link#

Repterra on Steam