Yes. Bellum is designed around PvP: real players cooperate within a platoon to fight another player-controlled force. Teamwork with friends, medical support, reconnaissance, and shared objectives are parts of that competitive experience. They do not establish a separate PvE campaign or cooperative mode against AI enemies.
As of November 2, 2026, do not buy Bellum expecting an offline story campaign, a confirmed bot-only alternative, or a documented PvE mode. The useful distinction is between cooperating with teammates and choosing who controls the opposition. Bellum offers the former inside its PvP design; a verified alternative to human opponents is not established.
Friendly cooperation and competitive opposition
The diagram shows friendly squad organization; cooperation within the team remains part of the PvP design.
Bellum organizes players into fireteams, squads, and a larger platoon. This structure makes cooperation central to ordinary play. You might stay with a leader, help a wounded teammate, share information, or support another element. None of those actions changes the overall contest into PvE, because the other force is still playing against you.
This distinction matters if you are moving from a game where co-op usually means fighting computer-controlled enemies. A description such as tactical teamwork can sound familiar while referring to a different kind of challenge. In Bellum, the people opposing your plan can adapt, reposition, and respond as players rather than following a scripted campaign encounter.
If your group enjoys coordinating against other groups, that is aligned with Bellum's design. If your group mainly wants a predictable mission against AI, cooperation by itself does not satisfy that requirement. The presence of military objectives, leaders, or reconnaissance equipment is not proof of a campaign or an AI enemy population.
You can therefore assess the game with two separate questions: whether you like working closely with other people, and whether you want those people on the opposing side as well. Bellum's current identity fits players who answer yes to both.
The modes describe different PvP objectives
The documented modes vary what the two forces are trying to accomplish. They should not be interpreted as a list containing an established PvE alternative. Different objectives can create different pacing and responsibilities while remaining part of the same player-versus-player focus.
| Mode | Main contest | What cooperation contributes |
|---|---|---|
| Attrition | Control Influence or exhaust enemy Manpower | Staying together, preserving lives, and maintaining presence |
| Exploitation | Defend or locate and destroy supply Caches | Sharing intel and coordinating attacks or defense |
| Strongpoint | Defend or destroy a Combat Outpost | Organizing a defense or coordinating the assault |
| Skirmish | Attrition in a smaller AO with 36 slots | Concentrated teamwork between two squads per side |
In Attrition, the Area of Operation is the central scoring space. Influence depends on the difference in effective presence between teams, and position within the AO also matters. The round is not simply a personal kill race: the platoon must retain enough strength to control the relevant space.
Exploitation gives al-Zalaam Caches to place and defend while the conventional force searches for them. Intel gathered from fallen opponents helps narrow the search. The asymmetric objectives can make this feel more like an operation, but an operational structure is not the same thing as a scripted mission against AI.
Strongpoint reverses the broad attack-and-defense relationship, with a conventional Combat Outpost to defend and al-Zalaam attacking it. Skirmish compresses the Attrition format into a smaller AO. Its 36-player capacity describes that format's available slots, not a live count of everyone currently playing Bellum.
Choose a role for how you want to cooperate
The roster gives each player a defined responsibility within the team.
A group does not need every player to perform the same job. Bellum's role structure creates different ways to contribute to a PvP team, including riflemen, automatic riflemen, medics, leaders, and crew-served weapon teams. Choose according to the responsibility you want during a round rather than assuming that cooperation requires being a commander.
A Rifleman gives a new player a straightforward place within the fireteam. You still need to move with the element, communicate, maintain awareness, and help teammates, but you are not also accepting the full coordination workload of a Squad Leader. Starting here is a practical way to learn whether you enjoy the team structure.
A Medic concentrates more heavily on recovering casualties and maintaining the element's ability to continue. The role carries medical resources beyond the basic supplies available to other players and has a dedicated medical communication channel. It is a support role within contested PvP; it does not remove you from the opponent's ability to affect the squad.
Leadership roles direct movement, coordinate with other elements, and help manage the squad's recovery. Crew-served systems add another kind of partnership between a gunner and supporting players. If your group enjoys interdependent responsibilities, those systems are relevant. If everyone wants complete independence, role specialization may create friction rather than automatically improving the evening.
Joining alone is different from playing solo
You do not have to interpret Bellum's emphasis on teamwork as a requirement to arrive with an entire organized platoon. Its squad structure is designed to make coordination understandable even with players you have not met. The deployment menu lets you select an available squad and role, giving you a defined place within the team.
However, joining without friends does not create a separate solo mode. Once you are in a squad, the objective remains collective. The documented advice is to fill existing squads instead of forming numerous undersized elements. That helps the team maintain strength and access the assets associated with a more complete organization.
Before choosing a slot, look at the squad's composition and role responsibilities. Then ask where to assemble and what your immediate task is. These are sensible in-game coordination steps, not a requirement to know advanced terminology before participating. Clear information is more useful than trying to imitate a highly experienced leader.
A silent independent approach can miss much of what the systems are designed to support. If you cannot or do not want to communicate during a particular session, recognize that constraint before joining. A game built around squad information and mutual support may be a poor fit for that session even if you enjoy its shooting.
Communication supports cooperation at different scales
Bellum separates local, squad, leadership, and medical communication. The default local push-to-talk key is V, and the squad channel uses B. Leaders have access to the Platoon Net with N, while medics use their role-specific Medical Net. Those channels give different information an appropriate audience.
For ordinary friendly coordination, use proximity voice when the person you need is nearby and the squad channel when the whole element needs the information. Keep your message short enough that another player can understand and act on it. A clear location or status update helps more than continuous narration.
The documented voice system does not include cross-team communication. Do not assume that getting close to an opponent enables negotiation or a shared conversation. Similarly, death and unconsciousness affect what a player can communicate. Dead players speak with dead squadmates through their dedicated deployment communication rather than relaying fresh information to living teammates.
Those limits explain why Bellum's cooperation can feel demanding even though you are playing with friendly people. The team must work with information available through the game, and the channels have consequences. If your ideal co-op session relies on unrestricted conversation with every character or opponent, adjust that expectation before buying.
Limited lives give friendly support a competitive purpose
Read the displayed spawn condition before assuming that a return to the field is available.
Under the documented rules, conventional roles receive three lives and unconventional roles four. Lives belong to the role slot, and an exhausted role becomes unavailable for the remainder of that round. Joining midway through a match can therefore mean taking a role with fewer lives left than its starting allowance.
This makes mutual support relevant to the outcome. Helping a teammate survive preserves participation and team strength. Choosing to wait for help can have a different value from immediately seeking another spawn. The game is designed to make those judgments matter within the competitive round.
Reconstitution also connects respawning to leadership and squad conditions. Available options depend on faction and mode, and leadership cannot use the mechanic while actively wounded or in contact. If a spawn option is blocked, read the displayed condition rather than assuming the game offers a universal instant return to action.
These systems can appeal to players who like the tension of cooperative survival but want human opposition. They may be less appealing if your group primarily wants repeated low-consequence attempts at the same encounter. The distinction comes from the rules already present, so a future tutorial cannot necessarily remove it.
Avoid treating future plans as a PvE promise
The latest roadmap discusses further content and a planned Raid mode intended to provide a more operation-like experience. That wording does not establish an offline campaign or AI opposition. An operation can still be a competitive match, and a future mode name alone does not tell you who controls the enemy.
The same applies to onboarding. Tutorials, specialized classes, certifications, and video guides are being developed to help new players. Their presence on a roadmap should not be converted into a claim that a complete bot training environment is available today. A teaching tool and a PvE game mode solve different needs.
Ground vehicles and other substantial additions are also planned, but they do not change the current answer about opposition. Do not use an expanding feature list to infer a confirmed shift away from the core PvP focus. If AI missions are your deciding requirement, wait for an explicit implemented mode that satisfies it.
Access milestones should be read separately too. Standard weekly testing is planned for December 3, with Wednesday through Sunday sessions, while the 24/7 launch target is Q1 2027. Broader access changes who can participate and when; it does not itself announce a new enemy type.
Match the current design to your group
Before committing, describe what your group wants to do in plain terms. If the goal is to coordinate an infantry squad against other human players, Bellum's present focus is relevant. If the goal is a private story campaign against AI with no competitive pressure, the documented experience does not establish that option.
For a mixed group, discuss the responsibilities that remain even when someone prefers a support role. A Medic still operates within a contested match. A Rifleman still belongs to a fireteam. A leader has a larger communication workload. Different roles can accommodate different interests without turning the round into several unrelated games.
If you join alone, plan to cooperate with the squad you enter. If you join with friends, plan to fit that group into the larger team rather than expecting the whole match to revolve around your party. That is the practical meaning of Bellum's team focus: friendly cooperation is essential, and the competition comes from another force of players.