Ground vehicles remain planned in Bellum's latest development update; an implemented driveable ground-vehicle roster is not established as of November 2, 2026. Drones are already implemented, including faction-specific reconnaissance and attack equipment. They are not transports that carry your infantry squad across the map.
If you mean trucks, armored transport, or a dedicated driver role, do not buy on the assumption that those systems are already playable. If you mean remotely operated airborne equipment, Bellum does have that kind of capability. The distinction matters because a drone clip can be accurate gameplay without demonstrating the vehicle experience you want.
Read the current ground-vehicle status correctly
Ground vehicles appear as a development priority, rather than an implemented vehicle roster.
The latest roadmap names ground vehicles among major upcoming additions. It groups them with other high-impact systems and says they require further explanation because of their effect on the game. That establishes development intent, but it does not provide a completed list of driveable vehicles or an exact deployment date.
For a purchase decision, treat the present experience as infantry-centered. A future ground-vehicle update could change how teams move or support each other, but it should not be counted as an existing activity. The useful test is whether you would still want to play the game before that addition arrives.
Avoid turning the broader access schedule into a vehicle deadline. Standard weekly testing is planned to begin December 3, and the 24/7 launch target is Q1 2027. Neither milestone, by itself, confirms when ground vehicles become available. A date attached to access answers a different question from a date attached to a specific gameplay system.
Similarly, a priority category describes what development is focusing on rather than guaranteeing that every item in that category ships together. You should wait for explicit implementation details if your enjoyment depends on a particular vehicle type, passenger system, or crew role. None of those specifics can be safely filled in from a broad roadmap label.
Drones are playable equipment with different jobs
Bellum's drone equipment is a separate implemented system. The documented faction examples are the Ranger Hornet reconnaissance micro-drone, SATYR's FPV Strike Drone, and al-Zalaam's VT Bomber. Their purposes differ, so a statement that the game has drones should not imply that every faction uses the same platform in the same way.
| Drone | Faction | Documented purpose |
|---|---|---|
| Hornet | Ranger Regiment | Reconnaissance and situational awareness |
| FPV Strike Drone | SATYR PMC | One-way explosive attack |
| VT Bomber | al-Zalaam | Release munitions and return to its operator |
The Hornet gives its operator a way to observe without exposing that player in the same manner as direct personal observation. It supports information gathering for the team. It does not create a transport seat or move the operator's body to the camera's location.
The FPV Strike Drone is a one-way munition rather than a reusable passenger aircraft. The VT Bomber releases its payload and can return, but its munitions cannot be replenished under the documented equipment rules. Those differences affect how you interpret the footage: returning a drone is not equivalent to resupplying a helicopter or delivering a squad.
If remotely controlled equipment is the feature you are looking for, examine the available role and its purpose. If your interest is specifically driving or carrying teammates, the existing drones do not satisfy that requirement merely because they move through the environment.
Recognize drone control without assuming transport features
The documented drone controls include pitch, roll, yaw, thrust, auto hover, altitude hold, camera control, and camera zoom. This is a distinct input context rather than ordinary infantry movement with a different viewpoint. Understanding that distinction helps you identify what an on-screen clip is actually showing.
For example, W and S control pitch while Q and E control yaw in the documented drone layout. Left Shift and Z control thrust up and down. The camera can be controlled with Left Alt and the mouse, while the mouse wheel changes zoom. Tab or Escape exits drone control.
Some controls are explicitly faction-specific. The documented R camera-view change and G payload release or fire apply to al-Zalaam. Do not transfer those inputs to every drone or infer that every platform has a payload. A shared control table can contain actions that are conditional on the equipment being used.
These details establish that drone operation is real gameplay, while also showing its limits for a vehicle buyer. A flying camera, an explosive one-way device, and a bomber payload are different systems from steering a ground transport, carrying passengers, managing a vehicle crew, or conducting supply runs. Judge the feature by the task it actually enables.
Anti-tank equipment does not prove tanks are available
Bellum includes roles and weapons whose names refer to anti-tank duties. That terminology alone does not establish an implemented tank roster. Equipment can have a broader design purpose than the set of targets currently available in a build, and launchers also appear in the game's infantry and objective interactions.
For example, the documented Exploitation rules allow rocket fire to destroy Caches. Heavy weapons therefore have an objective-related use without requiring a driveable armored vehicle to be present. Likewise, descriptions of role responsibilities can refer to potential target categories without functioning as a current vehicle inventory.
The same caution applies to a weapon being shown near a parked object. A model in a scene does not demonstrate that a player can enter it, drive it, carry teammates in it, or use its weapons. Those are separate capabilities. A useful confirmation needs to show the feature you care about rather than rely on the object's appearance or name.
When comparing footage, look for the player's actual interaction. Drone controls prove remote drone operation. A rocket launcher proves a launcher exists. Infantry beside a vehicle-shaped object proves only what is visible in that scene. None of those observations should be expanded into a complete combined-arms system.
What movement means for the current infantry game
This in-game formation diagram illustrates infantry movement rather than ground transport.
Without treating future transport as available, evaluate whether you enjoy moving as an infantry element. The documented movement controls include walking, running, sprinting, crouching, going prone, and holding Spacebar to vault, climb, or drop. The relevant current experience involves the player character navigating with the squad rather than assuming a ride between every position.
The Area of Operation provides useful scale context. Although the broader terrain is described at a 4-by-4-kilometer map scale, the active AO is a smaller designated play space. The manual describes AOs ranging from around 250 meters to 1.5 kilometers wide. Do not use the full terrain dimensions to invent a precise required walking distance for every match.
Actual travel also depends on where the element is, where the objective lies, and which spawn options are available. The Forward Operating Base is the initial staging and backup location, while leadership and deployable positions support the team's spawn network. These systems matter when assessing downtime, but they are not evidence of an implemented transport vehicle.
If you dislike infantry repositioning regardless of distance, the current game may not be the right purchase. If the shared movement is part of the appeal, vehicles are an additional future consideration rather than a prerequisite. Watch ordinary movement and regrouping sequences before deciding which description matches you.
Assess transport claims with a concrete checklist
Vehicle discussions often combine several different claims. Break them apart before deciding that a feature is available. This avoids confusing a development intention, a visual asset, and a usable game system.
- Identify the category. Establish whether the subject is a ground vehicle, remotely operated drone, static scene object, or a general roadmap label.
- Establish the status. Look for explicit implementation rather than assuming that a planned system has already shipped.
- Match the activity. Driving, transporting infantry, supporting a squad, and carrying supplies are separate tasks that need their own confirmation.
- Check the timing. A game's testing or launch window does not automatically become a release date for every roadmap item.
- Decide whether the confirmed activity satisfies your reason for playing.
Apply the checklist to older footage too. Earlier discussions may describe expectations that are narrower, broader, or simply less current than the latest roadmap. A confident prediction about APCs or helicopters should not be treated as a final roster, an implemented feature, or a promise that those exact classes will arrive.
You do not need to resolve every future design possibility to make a useful decision now. It is enough to separate what you can presently evaluate from what you would have to wait for. That keeps the buying choice tied to an actual experience rather than an imagined later version.
Choose whether to join now or wait for vehicles
Join the current testing phase only if the existing infantry-centered experience is enough for you. The implemented drones may be an additional attraction, particularly if you enjoy team information or specialized remote equipment. They should add to your assessment of the current game rather than stand in for a missing driver fantasy.
Wait if your main reason for playing tactical shooters is operating ground transport or being part of a vehicle crew. In that case, the next useful milestone is explicit implementation with enough detail to understand the role. A general statement that vehicles are planned does not tell you whether the particular experience you want will be included.
For a group, compare requirements before buying together. One player may be satisfied with infantry combat while another primarily wants to drive. The same roadmap can be acceptable to the first player and insufficient for the second. Agreement about the present game is more useful than assuming everyone values the same future additions.
When ground vehicles receive a dedicated explanation or enter a playable build, reassess the actual roster, available interactions, and applicable access conditions. Until then, the clear answer is that ground transport remains planned, drones are already implemented, and the current decision should be based on infantry gameplay you are willing to play now.