Warzone 2100:
Make your artillery see.
Your strongest weapon may be the unit that does not shoot
Warzone 2100's sensors, artillery, commanders, and repair routes work as one system. Here is how to understand that chain in the current 4.7 release.
Those connections change how you should read a crowded battlefield. A mortar battery sitting behind your front line may have useful reach but no useful target. A fast vehicle carrying a sensor can provide the missing link. A commander can organize a fighting group, while a repair route keeps its experienced members from becoming expensive wreckage. These are connected jobs, not interchangeable buttons.
This is a practical reading of the official project documentation, not a report of a newly tested competitive build. The screenshots are archival examples from the project's own website and manual; their menus and graphics are not presented as fresh captures of version 4.7. The purpose is to make the game's enduring decisions legible before you commit to a long campaign or an online match.
01 / Build a target chain, not a pile of mortars
The release-tagged sensor guide explains the central mismatch: artillery has a built-in sensor range, but even basic artillery weapons can shoot beyond it. A sensor tower or a vehicle with a sensor turret supplies observation farther forward. The practical question is therefore not simply whether your artillery can reach the enemy. It is whether a suitable sensor is identifying a target that remains within the artillery weapon's range.
For a stationary defense, the documented arrangement is straightforward: build a sensor tower, then let artillery structures fire at targets the tower identifies within their weapon range. Mobile artillery requires an explicit assignment. Select the artillery vehicles and click the sensor. If you attach them to a tower, its automatic target selection directs them; if you attach them to a sensor vehicle, select that vehicle and designate the enemy you want engaged.
For a first practice exercise, keep this arrangement small enough to inspect. Position a few artillery vehicles behind a protected approach, assign them to one sensor, and watch which target produces a response. Do not change the design, the position, and the assignment simultaneously. If the battery stays quiet, check the information link before assuming you need another factory. This is a diagnostic exercise, not a claim that one formation wins every map.
02 / Keep the observer alive and the battery separate
Separating the observer from the weapons is the point of the system. Moving every mortar up to the enemy defeats that separation and exposes a support force to direct attack. The official artillery guide describes these weapons as effective against infantry and many structures, but less effective against bunkers and tracked vehicles. It also warns that most, though not all, artillery must stop to shoot and that artillery-equipped vehicles are vulnerable without protection.
A sensible beginner arrangement gives the observer an escape route and gives the battery a screen of fighting units. Think about the next position before moving the current one: if the sensor retreats around a ridge or the enemy changes approach, will your support weapons still have a useful target inside their own reach? Longer weapon range is not a substitute for a working observation position.
This also explains why more firepower sometimes produces no visible improvement. You may have added guns to a chain whose weakest link is one exposed sensor. Protecting or repositioning that sensor can matter more than buying another artillery vehicle. Conversely, identifying an enemy observer gives you a concrete target to consider instead of trading shots indefinitely with weapons you cannot comfortably approach.
03 / Counter-battery sensors change what firing reveals
Counter-battery equipment adds a second information system. The current guide says CB sensors detect enemy artillery launches and identify the firing units or structures in red through the fog of war. Your own artillery still needs sufficient weapon range to reach those targets. Detection does not make a shell travel farther, and a revealed enemy battery is not automatically a destroyed battery.
The important behavioral detail is priority: when active, artillery favors counter-battery targets over targets supplied by ordinary sensors. A battery changing its attention can therefore be responding to a different targeting source rather than ignoring your entire defensive plan. Before diagnosing a malfunction, check whether hostile artillery has opened fire and whether a CB target has appeared.
For a returning player, the lesson is to separate two decisions. Ordinary sensors help you acquire useful battlefield targets; counter-battery sensors help you answer hostile indirect fire. Build the second capability because you have that problem, not because the word sensor makes every device sound equivalent. When planning an attack, also remember that shooting can disclose information to a prepared opponent. A protected firing position and a plan for relocating are more useful than assuming distance alone makes a battery safe.
04 / Design around a job, then inspect the trade-offs
Warzone's unit designer combines a body, a propulsion system, and a turret. That last choice can be a weapon or a system: a sensor vehicle is a deliberate allocation of a chassis to information rather than direct damage. Start with the task you need performed, then choose the parts. Designing the most impressive-looking tank first and inventing a role afterward makes the research tree harder to understand.
Propulsion is a particularly clear example. The release's guide describes tracks as durable, with resistance to anti-personnel and artillery damage, but with higher cost, longer construction, slower movement, and continuing vulnerability to anti-tank weapons. Hover propulsion offers speed and water crossing, yet provides little durability and is poorly suited to extended frontline fighting. Those are different assignments, not a simple ladder from bad to good.
A scout that cannot escape, a frontline vehicle that arrives late, and an expensive support chassis that never uses its extra protection are different design failures. Compare the designer's cost and movement information before producing a large batch. Give useful designs names that identify their jobs, such as observer or support, so that your production decisions remain readable after several research unlocks. That naming convention is an organizational suggestion, not a hidden game bonus.
05 / Research should repair a weakness you can name
A technology tree becomes easier to navigate when each project answers a battlefield question. Are you unable to spot for artillery, losing vehicles before they reach a repair facility, or producing too slowly to replace losses? Those diagnoses point toward different capabilities. Chasing every newly available weapon can leave the supporting economy and logistics behind the force you are trying to improve.
The current research guide makes a useful distinction between power and progress. Each project needs power and time, and the power investment is not refundable. Research progress, however, is not lost when the facility is destroyed: the project can be assigned to another facility. That means the loss of a lab interrupts capability development without necessarily erasing all the work already done.
The manual also distinguishes campaign artifacts from the broader skirmish technology progression. In campaign play, recovered artifacts can unlock research opportunities; in skirmish and multiplayer, you work through the available tree. Avoid treating an early campaign inventory as a universal competitive opening. Write down what your next unlock is meant to change, finish the supporting design or structure, and then check whether the original weakness actually improved.
06 / An economy is a supply system, not a building collection
Power funds the structures, vehicles, and research that keep the target chain working. The generator rule is simple enough to check without memorizing a build order: each power generator serves up to four oil derricks. The official guide's example uses ten derricks and three generators. Additional generators beyond the capacity needed for the derricks do not create extra income by themselves.
That distinction discourages a familiar beginner mistake: responding to a power shortage by adding generators without checking the oil supply. Oil derricks belong on oil resources, while generators can be placed elsewhere. A protected generator cannot compensate for losing the outlying resources that feed your economy. Your map awareness therefore supports both combat targeting and the ability to afford replacement units.
Treat a forward expansion as a commitment to protect and maintain another part of that network. If every new derrick requires a larger escort than you can afford, a nominal increase in income may come with a difficult defense problem. There is no universal safe number of expansions; the useful habit is to connect each new resource to a realistic route, construction plan, and defensive response rather than counting structures in isolation.
07 / Construction time belongs in your plan
A researched upgrade and a completed structure are not the same thing. The manual explains that researched power modules must be built on generators, and research modules must be constructed on research facilities. Adding a research module pauses the facility's current project while the work proceeds. If you need a particular technology immediately, the timing of that interruption deserves attention.
Construction units also let you turn spare time into a more resilient position. Multiple trucks can assist with a building, and queued orders can give them a sequence of jobs. But a queue is only an instruction sequence, not a guarantee that every destination remains safe. A truck following yesterday's expansion plan into today's firefight can remove your ability to replace the very structures you are defending.
Before a planned push, review what must already exist: the observer, the support weapons, a repaired frontline group, and somewhere for damaged units to go. This is a more useful readiness check than looking at the army count alone. If one prerequisite is missing, either delay deliberately or change the scope of the attack. Do not discover the missing repair route only after experienced vehicles start turning back.
08 / Commanders organize a force, not just a selection
A commander is different from a numbered selection group. The current guide says assigned units receive accuracy, armor, and movement-speed benefits that increase with the commander's rank. To attach units, select them and click the commander; an attachment symbol confirms the relationship. Targeting an enemy through that commander directs the attached units toward the target with improved accuracy.
For learning, use a modest group whose membership you can recognize. A commander adds another system worth protecting and another place to check when orders do not behave as expected. Do not assume every unit standing nearby is assigned. Equally, do not assume that selecting one vehicle necessarily isolates it from its command group. The release-tagged detachment instructions say to right-click the individual unit, or hold Shift while selecting it, then issue a new order.
Repairs are part of the command relationship. The official guide says a unit retreating to a repair facility remains attached and returns to its commander afterward. That makes the commander's location important: a successful repair does not help if the returning vehicle travels straight back into an untenable position. Organize the force around a place it can survive, not merely a target it can reach.
09 / Give retreat behavior the same attention as weapons
The unit-orders menu controls more than attacks. It lets you choose a retreat threshold, including medium damage, heavy damage, or no automatic retreat. The release guide identifies the last option, Do or Die, as the default. If you expected damaged vehicles to preserve themselves without setting that behavior, the game may simply be following a different instruction than the one you imagined.
For a learning session, set a retreat threshold consciously and observe the route. A medium-damage retreat gives a unit more margin but also takes it out of the fight sooner. Waiting for heavy damage keeps it engaged longer but leaves less room for a dangerous journey. Neither option can make a repair destination safe, and neither is a substitute for noticing that the whole position has become unsustainable.
It helps to distinguish a local repair cycle from a general withdrawal. One vehicle leaving the line can be routine; every frontline vehicle leaving at once can expose the sensor and artillery behind them. Your support formation should not depend on the screen being permanently intact. The practical payoff is not a perfect automation setting, but fewer surprises about what the army will do when it starts taking damage.
10 / Campaign missions ask a different logistics question
Campaign play adds mission objectives, transport, and time pressure to the same underlying systems. The manual's transport interface makes the distinction visible: preparing a useful force for an away mission is not the same as leaving every available vehicle in a sprawling home-base army. Read the intelligence briefing and timer before deciding that another production cycle is worth the delay.
A good campaign habit is to review the force by roles rather than only by quantity. Which units can fight at the destination, which provide support, and which experienced vehicles need repair or replacement before the next commitment? That checklist is deliberately flexible because mission requirements and unlocked technologies change. It avoids pretending that a single transport loadout is correct throughout the campaign.
The current mission-timer guide also corrects an old waiting habit. With the Timer Power Bonus tweak enabled, which the guide identifies as the default, finishing early grants the power you would have accumulated by letting the timer run. Spare time can still be used for research, defenses, or recycling and replacement, but idling solely for that power is not the same necessity under the default tweak. Check your campaign settings before following advice written for a different balance setup.
What 4.7 changes for a returning player
The official website lists 4.7.0 as the current release at this article's October 27 publication date. It was announced on April 7, 2026—not today. Its Legacy & Lobby update adds the Pumpkin v1.10 campaign-balance option, intended to closely represent the original developers' balance, alongside improvements to the current campaign experience. Choose the balance deliberately before comparing old walkthroughs with your results.
The multiplayer changes are practical: players can share a GameId and join through it instead of finding a room in the list. The redesigned lobby adds connection methods and IPv4/IPv6 hosting support; some players behind difficult connections may benefit, but this is not a promise that every network configuration will work. Host options are collected behind the gear beside the Players and Spectators tabs, and a public web lobby shows available activity.
Those changes reduce friction around starting a session. They do not replace the tactical work once it begins. Agree on the version and match settings with friends, then use the first game to practice one information chain rather than to judge your whole ability from a chaotic defeat.
A first-session plan with a useful stopping point
Start from the official project site, which offers Windows, macOS, and Linux downloads, links to release packages, and checksum information. The project also points new players toward its tutorial. Check the package and system requirements that match your machine rather than assuming every installer supports the same operating-system versions. This guide does not require creating an account or installing an unofficial build.
After the tutorial, choose one manageable practice goal: make artillery respond reliably to an assigned sensor while keeping the observer and battery alive. Then add a commander or a repair cycle, not every advanced system at once. When something fails, describe it precisely: no target, insufficient range, broken assignment, exposed observer, interrupted research, or an unsafe retreat. Each description suggests a different correction.
The satisfying moment in Warzone is not always a larger explosion. It can be a battery firing from safety because another unit sees for it, an experienced vehicle returning from repair to the right group, or a research choice solving a weakness you had actually identified. Once those links are visible, the sprawling designer and technology tree stop looking like a wall of options. They become tools for building a force with a coherent job.
Comments
Post a Comment