Supersedes #12
From https://www.moddb.com/mods/openxcom-coop-mod/downloads/openxcom-co-op-mod-v170-full-release
Changelog 2026/03/30
...
4. It is now possible for a player to join a campaign directly from the main menu (New Battle), without needing a save file. The joining player cannot access their own bases or crafts, and cannot purchase items or equip soldiers while in a teammate’s base, but can still take part in Battlescape missions. In Battlescape, the host can give soldiers to a teammate. If the connection is lost, the joining player is returned to the main menu. Please note that this feature is still a work in progress and may change later.
The above feature has regressed in 1.8.4: Once a player joins on XCOM's side, without him having a save file, once he has pressed Ready and then presses Cancel, he is prompted to make a base. So the above feature is impossible. So the only way currently to not have a base is to play on the Alien side.
However. I was thinking of Total Warhammer 3 and how many campaigns I have played with my buddy. We may ally, we may be at war, but always, when a battle happens for either, the other player plays as AI. Yes, even if we are in alliance. As the goal is to have a fun/tactical combat experience.
Suggestion
-
Not bind the geoscape side/faction with the battlescape side/faction (they are disconnected in code anyway)
But next to the side column (XCOM/Alien), have a Base column, with 3 choices:
A. No Base
B. Shared Base
C. Duplicate Base (the default of this mod)
-
The XCOM/Alien column instead to have:
XCOM/Alien/Dynamic and unlike the bases column, to be changeable at any point in the geoscape. Dynamic is the default, where you are prompted at each battle of another player, which side to play as. XCOM automatically chooses XCOM side. Alien side automatically chooses Alien side.
Note: For the first suggestion, if a player selects Shared Base, and there are more than 2 players, other players shouldn't be able to select Duplicate Base. This is to avoid the code bloat, for a campaign ruleset which no one will ever choose: 2 players share 1 base, while the third player chooses a duplicate base. I genuinely don't believe this specific ruleset will ever be played, so might as well avoid making dynamic shared bases, so as whenever a base is synced (this is already implemented 🎉 ), it's always of the first/only player with a base. But I have no idea of the codebase so this restriction might not be needed.
Supersedes #12
From https://www.moddb.com/mods/openxcom-coop-mod/downloads/openxcom-co-op-mod-v170-full-release
The above feature has regressed in 1.8.4: Once a player joins on XCOM's side, without him having a save file, once he has pressed
Readyand then pressesCancel, he is prompted to make a base. So the above feature is impossible. So the only way currently to not have a base is to play on the Alien side.However. I was thinking of Total Warhammer 3 and how many campaigns I have played with my buddy. We may ally, we may be at war, but always, when a battle happens for either, the other player plays as AI. Yes, even if we are in alliance. As the goal is to have a fun/tactical combat experience.
Suggestion
Not bind the geoscape side/faction with the battlescape side/faction (they are disconnected in code anyway)
But next to the side column (XCOM/Alien), have a
Basecolumn, with 3 choices:A. No Base
B. Shared Base
C. Duplicate Base (the default of this mod)
The
XCOM/Aliencolumn instead to have:XCOM/Alien/Dynamicand unlike the bases column, to be changeable at any point in the geoscape. Dynamic is the default, where you are prompted at each battle of another player, which side to play as. XCOM automatically chooses XCOM side. Alien side automatically chooses Alien side.Note: For the first suggestion, if a player selects
Shared Base, and there are more than 2 players, other players shouldn't be able to selectDuplicate Base. This is to avoid the code bloat, for a campaign ruleset which no one will ever choose: 2 players share 1 base, while the third player chooses a duplicate base. I genuinely don't believe this specific ruleset will ever be played, so might as well avoid making dynamic shared bases, so as whenever a base is synced (this is already implemented 🎉 ), it's always of the first/only player with a base. But I have no idea of the codebase so this restriction might not be needed.