Summary of gameplay in a minimum KS environment

INovaeKeith · May 10, 2018, 4:48am

Alright this is a more thorough followup response to the Stations orbiting the planets thread. To recap, I mentioned in a recent post that players will incrementally fight for control of a solar system by duking it out within successive “battlescapes”. A battlescape is defined as a single anchor celestial body, most likely a planet, along with lesser supporting celestial bodies such as moons, asteroid fields, planetary rings, etc. Some people read this and got rather upset, believing that we are unnecessarily reducing the scope of the game or were previously being misleading about the gameplay. Here I will attempt to clarify.

The game we pitched during our Kickstarter was the game we wanted and hoped to build - the minimum cost of building that game we estimated at $2.5 million. Obviously, we came nowhere near that and instead barely made it past our absolute minimum of $300k. There is a gaping chasm of a difference between having $300k and $2.5 million, so, what does that mean for Infinity: Battlescape? We priced our minimum Kickstarter at the point where we believed we could build something that was at least in the spirit of the full vision.

While planets and solar systems are really cool they present a significant problem from a game design perspective. Given their incredible size how do you populate all that “space” with interesting content? Since our game is multiplayer-only the most obvious answer is you cram as many players as possible on a single server. This is why, on our Kickstarter page, we mention “semi-persistence” for the full vision of Infinity: Battlescape. You can interpret “semi-persistence” as “miniaturized psuedo-MMO”. In practice this meant that we would spend significant engineering effort trying to support as many players on a single server as possible because we felt that would be critical to providing a good experience.

Unfortunately, populating the solar system with enough interesting content isn’t the only problem. We have to balance how much firepower it will take to destroy various pieces of infrastructure within the game. Can a single interceptor destroy an entire factory in any reasonable amount of time? What if we require the equivalent firepower of at least 1 cruiser or a full squadron of bombers? If 10 players are on a server only a couple of them will ever be able to attack any one installation at any point in time. In an entire solar system there will be many pieces of enemy infrastructure so not only will it potentially take you a long time to destroy all of it by yourself but the likelihood you ever run into an enemy player will be slim until you have destroyed the majority of their bases.

So, we successfully raised our minimum Kickstarter, we can’t afford to spend the engineering time required for a proper MMO scale server, what do we do? The idea we originally came up with prior to launching the Kickstarter, as we figured it was much more likely we only raised $300k vs $2.5 million, is to artificially reduce the areas of conflict within the solar system. What this means, as described above, is that all “interesting” content that pertains to the outcome of a single “match” will be concentrated around a single planet. The entire solar system is still seamlessly explorable - it’s just that the other bases etc will all be temporarily hidden so you are incentivized to stay within a more confined space. This dramatically increases the likelihood you will run into other players and have more interesting and enjoyable experiences. How do these other battlescapes get unhidden? When a server starts up the battlescapes within a solar system will have their ownership split up among all of the teams. Each battlescape represents a single match in a tug of war for control of the entire solar system. When a battlescape is conquered the match ends and another one begins at a new battlescape until one team has conquered everything. Another way of thinking about it is that each battlescape is a capture point and whichever team captures all of the points wins the war and the server then resets.

Another potential solution to our problem is AI. On a server with few players compelling AI could fill in the gap and still create a rewarding experience for the human participants. Since AI consumes considerably less bandwidth than human players we could conceivably have 100’s or thousands of AI players on a server that can only support a few hundred human players and that would go a long way toward resolving our problem. Those of you who’ve been paying close attention may have noticed that we originally promised no AI for Infinity: Battlescape. This is because good AI takes a lot of engineering effort and given the choice between the two we’d prefer to spend our limited time on player driven interaction. Coincidentally, we now have AI anyway however that was more or less an accident. Flavien needed some simple bots to test out weapons and he kept incrementally making them slightly smarter until we realized we actually had a halfway decent AI that did in fact create a richer experience.

What does all of this mean for Infinity: Battlescape over the near future? We spent the better part of last year working on our networking code and arrived at a result we’re pretty happy with. Thus far we believe we should be able to get up to ~500 players without too much of a problem on respectably powerful hardware, not to mention there’s still plenty of room for optimization. If we end up ever having the time to implement any of those optimizations we think it might be possible, with somewhat specialized high end hardware and a 1gb connection, to go well over a thousand players on a single server - that would be huge.

Since we accidentally have AI we’ve decided we’re going to try and continue making incremental improvements to it and hopefully by release it’ll be something that’s good enough. The hard part about making AI isn’t building bots that can win - it’s building bots that can convincingly lose. For Alpha, as we’ve mentioned before, our goal is to build a single battlescape. We will use this to balance weapons, ships, and infrastructure while implementing the rest of our core gameplay. During Beta we will begin to build the rest of the battlescapes. Fortunately, testing an entire solar system-wide war is fairly straightforward - we just enable all battlescapes all at once - and we may play around with that before fully committing to a “capture point tug of war” set of matches for final release.

Of course, if any of you have suggestions as to how we could support an entire solar system of seamless conflict we’re always open to hearing your ideas. With our current cash flow we have ~1 year of development runway left and it’s getting to the point where we’re going to have to start making some hard decisions. If we’re lucky our sales will increase after Alpha and Beta and if that happens we’ll have more flexibility to tinker with some of these things. Otherwise, we’re going to do our best with the time we have left. While I understand some of you really have your heart set on a seamless, continuous solar system-wide conflict I ask you to please keep an open mind about this “tug of war” system. If, during the Alpha, you find yourself enjoying the game within a single battlescape then perhaps, while not ideal, it won’t be so bad in the end. If everybody ends up hating it then honestly we probably have bigger problems than worrying about whether or not we’re using an entire solar system all at once. Either way, we’ll be engaging with all of you every step of the way.

Lomsor · May 10, 2018, 7:13am

Thanks for writing this up. This makes it a lot clearer.
We have seen this problem coming.
The proposal sounds somewhat alright. I’m worried about the reset. If you just spawn near the new battlescape it won’t be seamless at all.
One alternative would be to reset or cut/divide the funds of a player as well as having global and battlescape stats seperated but still leaving the players in their ships. They can then proceed to the new battlescape. (I know there’s nothing really “there” inbetween these battlescape but even EVE has some sense to make it look like you are moving somewhere)

Also, deep space outpost or faar flanks that take minutes to respond would be interesting and aren’t mentioned… but details.

Here the thead with ideas about this problem, it sounds different but is essentially simmilar:

And my idea in it:

Not much different than your plan really. What I find important is that the System should still be fully visible in map view and maybe incentive could be tried instead of disabling bases or as Sab1e mentioned ways for players to (temporarily) enable bases.
Handling player numbers is indeed important.

Sab1e · May 10, 2018, 7:14am

Okay, thanks Keith.

So, I’m envisioning a solar system that is broken up into a kind of strategic map of zones (what you describe as the various planet/moon Battlescapes). Having read your post, I do think it’s reasonable to conquer these one at a time if we can make it feel organic.

I’m just going to throw out a few thoughts about what you’ve said and see if any resonate:

Could there be activation conditions for each battlescape?
Perhaps the team that wins that zone gets to vote on which one to go to next? It doesn’t necessarily mean they will win the next one.
If a different team then wins, could they choose to revisit a previously captured battlescape?
Might previously won battlescapes be reinforced with strong NPCs from that team?
At a stretch, perhaps each team could have a previous, reinforced zone that is attackable if you have the strength, but the main goal is to attack the next neutral zone (though this would require more active zones at once). Breaking a team’s hold would be a raid-level challenge and weaken the targeted team’s position in the solar system.

I do actually agree that a whole solar system is likely to spread players out too much. There’s nothing wrong with focusing the action if it’s done well! The current battlescape alone is a good size.

cybercritic · May 10, 2018, 7:22am

I think you should decrease the number of teams from three to two before you go and start disabling battlescapes. That cuts down the required team assets by a third and it huddles players together without actually changing the game in a significant way.

Argopeilacos · May 10, 2018, 8:50am

I think this is a reasonable solution, and people that are worried that surprise attacks won’t be possible forget that currently we have a single battlescape… The game would still be perfectly possible on a single planet with lower warp speed!

If we assume a Sol-like system, battlescapes are going to vary widely in size:

How do you plan to distribute battescapes?

Lomsor · May 10, 2018, 9:58am

Nice image.

I think the ammount of POI (Bases, Stations, Factories etc.) will be more important than distance.
Additionally Carriers will decrease the importance of distance.
And nearly forgot, gravity influence to warp could make the effective travel time comparable between Battlescape even thoigh they have different sizes.
I don’t like the idea of unrealistically placed Bodies for gamplay reasons by the way, make warp faster if travel time should be shorter.
Problem with differing warp speed is that the player will have a hard time comparing actuall absolute distances. Sense of scale will be hard to achieve, I don’t think we can do without that though.

So if the ammount of POI per Battlescape stays adequate for the current ammount of players the density should rooughly stay the same.
Altough a bit of variance could be interesting. As well as different POI density on certain Bodies.

Sab1e · May 10, 2018, 11:15am

If there’s less bodies, we can have the stations/bases more concentrated. The warp already works in a way that different arena sizes don’t matter too much.

This’ll work, done right!

INovaeKeith · May 10, 2018, 1:15pm

This is already being actively discussed.

hrobertson · May 10, 2018, 2:14pm

I’m busy at work so I don’t have time to compose a proper response which I will do tonight, but I’ll outline my suggestion of how to tackle the issue.

The issue I think people have is losing the seamlessness that the I-Novae engine does so well. It’s all very well saying that technically the system is still seamless and you can travel everywhere, but if there are no facilities there until such time as one battlescape is ‘won’ and the server spawns the bases at the new battlescape, that’s quite jarring and you lose the notion that it is one seamless environment.

What I’d like is:

Facilities exist throughout the system at all times. [Instead of facilities only existing in the ‘active’ battlescape]
The fight for a solar system happens in one continuous match. [Instead of the fight for each battlescape being a match]

This has the potential issue of players spreading out rather than focusing on one Battlescape. So to tackle this:

Have two teams, not three.
- Where previously there would be three team-team ‘front lines’ (Red/Blue, Blue/Green, Green/Red), there is now only one ‘front line’ between the two teams. This naturally focuses players to 1 place rather than 3.
Limit the top speed of ‘warp’ to a speed that facilitates easy travel within a battlescape but makes travelling to another battlescape take a boringly long time.
- ~66kkm/s would mean travelling twice Titan’s orbital radius would take 30 seconds, but travelling from Earth to Mars at their closest approach would take 20 minutes. Saturn to Jupiter at closest approach would take 2.7 hours.
- Give capital ships an even slower warp speed
Carriers and the other capitals have a ‘jump drive’ which is used to travel from one battlescape to another.
- This jump drive only becomes active once the ‘current’ battlescape is ‘won’
  - By capturing/wining a battlescape, the team secures the resources required to power their jump drives and jump to the next battlescape
- Jump drive can be totally automatic with no extra interaction mechanics if dev time is tight
- The team that ‘looses’ the battlescape cannot jump, they must respawn at the battlescape that they have been forced back to, that the winners are about to jump to.
Players can still chose to slowboat to another battlescape
- They will find facilities there [So won’t experience the shattering of the seamlessness]
- The bases will be very well defended by NPCs - more so than in the active battlescape
  - Explain by saying most NPCs retreat from the ‘front line’ battlescape - the players are the vanguard
- Players won’t be able to respawn there because their carriers are back at the currently active battlescape
- If enough players slowboat across together and manage to defeat the defenders against the odds, that counts just the same as if they had won it while it was the ‘current’ battlescape.
Arrange the solar systems in so the battlescapes are chained together and there is a tug of war which can move back and forward as the teams win & lose battlescapes.
- I’ll put together some diagrams to demonstrate this tonight.

INovaeFlavien · May 10, 2018, 2:20pm

Another important thing: if there are facilities at other battlescapes, are these active or not ? As in, do factories in other battlescapes generate resources/credits ? Do haulers spawn and haul resources between bases ? Can a player respawn at one of these locations, or only in the “current” active battlescape ?

If factories in other battlescapes do generate resources, then as the game progresses as “tug of war”, less and less resources will be available in every match. I don’t think that’s desirable; in fact you could probably argue the opposite, where you’d like the “final” battlescape to be epic & grandiose with bigger battles…

If haulers transport resources at other battlescapes, all of these will consume server performance for no good reason ( we start to enter the “technical issues” that Keith was mentionning earlier ).

Just food for thought.

HBO · May 10, 2018, 2:51pm

wise though flavien.
Aslo https://www.eugdpr.org/the-regulation.html are active now , your delaware company term do no apply anymore.

Seuche · May 10, 2018, 3:17pm

I would like to see them be active in the sense of visible NPC activities without giving any points / resources towards any team until the battlescape gets activated / captured (insert game mode here ).

To make battlescapes active you could have to scout for the factories, bases, etc first. And if the server resources aren’t enough for full simulation, maybe limit the NPC activities in these neighboring / not “active” battlescape to a certain minimum.

The concern about thinning out the action to much with a to wide play zone is a valid point. But there’s always the possibility of introducing bonuses / extras for players that fight in a specific battlescape. So, if you help fighting in the current designated “main” battlescape you get extra resources / more stuff for your team / yourself.

Bate the players into the place you want them to be, this will be seen as something positive instead of limiting their movement which always looks negative.

More food.

Playbenni · May 10, 2018, 3:58pm

I also don’t really like the idea of having the server basically decide where the action happens.
That said, concentrating players on one, maybe two, locations will probably be critical to enable proper gameplay.

What I would propose is the following:

One match/war consists of two teams fighting for control over the entire solar system, these matches can last hours/days
During this match/war so called “conficts” happen, basically another word for a usual match as it is known from other games, a “conflict” has a start where a message pops up telling everyone where the conflict is at (new conflict at Eupraxia Station, Rethe Prime) and the personal kill scores are reset
where a conflict arises is entirely dependent by the players actions!
to start a conflict, a sizeable group of players have to launch an attack at a station or base (the size scales with numbers of players on the server, for example to start the conflict at least 70% of one team have to start the attack on the station/base), this is done by the players destroying the “automated defense guard array” of the station
the “automated defense guard array” is basically an exposed station module that generates the stations/bases shields, as long as the “ADGA” is up, the station has an infinite shield that can’t be penetrated, flying inside the shield is deadly because the stations weapons just obliterate you (super increased station weapons damage ->instadeath)
the durability of this “ADGA” station module is dependent of the player population, with this you can scale the needed player numbers to start the match. Only with the firepower support of capital ships you will be powerful enough to destroy the “ADGA”
once the “ADGA” is destroyed, the stations shields go offline and players can start to destroy the structure. As soon as the stations “ADGA” is destroyed the station will start to manufacture a new “ADGA”.
defender bots might only spawn once the stations shields are down
once the conflict started the attacking players either destroy the station, or the stations team can defend the station till the time the new “ADGA” is ready to be deployed
is the station not dead within this time, the new “ADGA” is deployed. Once it is deployed, the stations shields immediatly go up again and are impenetrable for some arbitrary time span, attacking then will be completely useless
when either the new “ADGA” is deployed or the station is destroyed the “conflict” is won/lost, players will then get rewards depending on their personal performance (kills, deaths, etc.) and the team that lost/won has either lost a station or defended it
the time it takes the station to manufacture a new “ADGA” is dependent on how much damage it is receiving, for example if the attacker group arrives and destroyes the “ADGA” and then immediatly leave, it takes the station only a very short time to rebuild it, if however after the “ADGA” is destroyed the station receives heavy continued fire from cap ships, it will take the station longer to rebuild it
the “match” ends when all stations/bases of one team are destroyed and no more spawn locations are avaílable to the losing team
the winning side the gets a fat personal credit/item reward, even if they are offline at that moment

Team credits and bots

Team credits are accumulated by bots harvesting resources, they are not team wide but each station has its own credit account
each base has one super armored freighter that carries resources from its planetary base to the station
only when the botfreighter arrives at the station the station receives the credits
the stations credits are used up by spawning capital ships (needed to start conflicts) and rebuilding its “ADGA”
each station has a maximum amount of credits it can hold, when the stations credits are empty it can no longer spawn capital ships or rebuild its “ADGA”
when the maximum amount of credits of the station is reached, the amount that is then gained will be delivered “to the home world” (lore explaination)
as the match progresses, naturally resources will dwindle and one side will slowly gain the upper hand, I expect the match to progress quicker and quicker by the end because the odds will start to shift dramatically

Pros:

only one bot per base needed, if there is one or two bases per planet/moon, the number of freighterbots stays quite low
no defender bots needed outside of conflict zones, because the enemies facilities are protected by their super powerful shields
every planet can have bases and stations
players decide where to attack by bringing a fleet with capships to the conflict location
by scaling the needed firepower it needs to start a conflict, the conflicts can only happen at one location each per team (two active conflicts at a time, one attacking and one defending conflict for each team basically)
players play relatively short “conflicts” that earn them their personal rewards, similar to the usual matches from other MP games
scouting will be a natural element of the game, because the locations where the conflict should start must be pretty devoid of the opposing team to start the conflict
small side activities like trying to intercept the enemies freighterbots become a natural part of the gameplay and will help with winning the match by starving the enemy of team credits
the game will have a somewhat persistant feeling to it, because one conflict doesn’t win the war for the solar system, and good planning and scouting will help win the war/match

Cons:

You tell me

Sab1e · May 10, 2018, 4:20pm

I would keep everything gameplay-relevant focused on the active battlescape. However, I would certainly like to see bases/stations exist at all times.

An active battlescape can function largely as it does already, a distributed selection of bases for each team.
A conquered battlescape could be flooded with NPC defences for that team, making it extremely difficult to return there, but doesn’t actively generate any more resources outside its own zone. There may be conditions where this could be retaken if the other team wins a zone.
An unconquered, inactive battlescape could have neutral “civilian” stations/bases that are then commandeered by the teams when the battlescape becomes active (probably passively, or through scouting?) Until then, there would be very few neutral NPCs that could act as a little target practice if someone bothers to go there. If you want real action, go to the active battlescape.

I think only spawning in the active battlescape would keep it tighter.

And if 2 teams works better than 3, then go for it!

Weps · May 10, 2018, 6:11pm

I must say, I too initially understood that a match will feature a conflict spawning the entire solar system, with players deciding when and where attacks are carried out, not an algorithm.

Even if free roam remains available across the entire system, I feel that the game loses its uniqueness and advantage on the market if players are restricted to playing in the vicinity of a planet at one given time. What would be the point of a seamless solar system if the exact same gameplay could be achieved with instances/maps/sectors just like in most other space games?

For the issue of keeping players together, I feel that the game can “cheat” in a number of ways to incentivize players to congregate, without forcing them to do so if they feel like going Geronimo outside of the intended active battlescape. How about terrifying AI wings to take out lone kamikaze players who attack the wrong spot, or credit rewards only for the players who follow the “orders” of attacking in the intended battlescape?

For the server performance issue, I’m asking myself why there can’t be simply less assets altogether? Must each battlescape consist of a minimum number of assets because of other gameplay reasons?

For the resource generation problem, I don’t see how diminishing returns for the losing side at a battlescape level is any better than the same on a solar system level.

INovaeKeith · May 10, 2018, 7:33pm

Resources would be reset for every battlescape.

Tjafaas · May 10, 2018, 7:51pm

OK, so there probably was a miscommunication somewhere, as I’ve understood the same as most of the other users for the gameplay: a battlescape IS the solar system.

I’ve never quite caught the “semi-persistent” state promised at the high-end KS goal. Now we see better on your initial intents, although some of your words need more accurate definitions.

No, I don’t. MMO means what it means: Massively Multiplayer Online (game). And so far, you’ve done great work: hundreds of players can battle among themselves. An MMO doesn’t always have to have a virtual economy, nor any “persistence” beyond personnal stats / customization.
In this regard, consider PUBG / Fortnite as specific subsets of the MMO genre.

While I completely agree with this idea, I disagree with your proposed method. We’ve already got the “sandbox mode” to freely explore the system. If the battlescape can last very long period of times (hours / days if I understood) and is only set to a planet and its immediate surroundings, then the rest of the system is pure cosmetics. Which would be a shame, in my opinion, not to fully exploit it and set yourself apart from most other space MMOs.

Now, I see that you’re worried about some technical and gameplay issues, should all the bases be available.
Well, I think you’ve provided the answer yourself!

That’s it! Keep all the bases as uncaptured, save for two bases that will serve as starters for each team (or three, if you intend to keep 3 teams).

Unclaimed bases can be captured, or destroyed if a “scorched earth” tactic needs to apply. The greater the player’s number and the bigger the ship’s tonnage, the quicker.
Claimed bases can be captured with the desctruction of whatever defensive module you’ll imagine. Of course, destroying the production is also an option, at the risk that when captured, the base doesn’t serve much in generating resources…
The players decide themselves how best to organize tactics and which objectives / bases to pursue.

As for the minimal threshold of players for the gameplay / game experience to be interesting, and its mitigation or solutions, well… many contributors have suggested a lot of different views, both here and in previous threads.

Kichae · May 11, 2018, 1:23pm

Or don’t, because PUBG/Fortnite aren’t considered MMOs by most people in the industry. They’re large arena combat FPS games. MMOs almost always have persistent worlds; it’s become a defining aspect of the supergenre.

There’s a potential issue here, which I do think should be A/B tested rather than just assumed: If the whole system is conquerable at the start, it actually encourages players to fan out at the start of a match and, basically, see nobody for the gods know how long. If that’s something Keith and Flavian explicitly want to avoid, because they’re trying to sell the large fleet battles, then it makes sense to not incentivize early-game spread.

Personally, I’m all about the haunting loneliness and emptiness of space, but that doesn’t seem to be the focus of Battlescape.

hrobertson · May 11, 2018, 4:01pm

Sorry for the lack of follow up post last night. I got kinda busy.
I was going to write about the disappointing and frankly concerning manner of the communication regarding this issue, but let’s just crack on with the solution …

Continuing to add to the mechanics explained in my above post …

Example of tug-of-war 'chain' of battlescapes

Match starts with both teams fighting over a shared battlescape half facilities red, half blue
— — — — — —
Red win leaving a few facilities red, other facilities destroyed.
— — — — — —
Red win leaving a few facilities red, other facilities destroyed.
— — — — — —
Blue win leaving a few facilities blue, other facilities destroyed.
— — — — — —
Blue win red only had a few facilities as most were destroyed in the earlier fight in this battlescape. Blue destroy them all leaving no active facilities in this battlescape
— — — — — —
Red win the battlescape with no remaining facilities is skipped
— — — — — —
etc etc…

Separate scenario in which a group of blue players slowboat and win a battlescape ‘out of sequence’:
— — — — — —
Group of blue players take the next red battlescape while the fight for the initial battlescape continues
— — — — — —
Blue win the initial battlescape, the next one is already blue-controlled so the fight is now in the one after that:
— — — — — —

Respawning

Players would be able to spawn at:

Player carriers, which could be anywhere in the solar system
NPC carriers only in the active battlescape
Facilities in the active battlescape
Facilities in a battlescape controlled by their team which has enemies currently detected within it

Player resources

Players’ personal pot of resources are not reset. They retain their resources when they move between battlescapes, whether they respawn or jump.
Players only gain resources from the battlescape they are currently in.
- While a player is in the vastness of interplanetary space they receive nothing.

Facility resources

All factories in all battlescapes would generate resources even when not the focus battlescape, but when there are no players anywhere near there is no need for the haulers to actually exist with their associated performance costs - the server can just ‘simulate’ the resource gain. If a player comes within some appropriate range then the hauler can spawn.

Resources generated in a battlescape would be shared between the facilities and players in that battlescape. (How they are divided out is up for discussion & testing)
Facilities would use the resources to spawn new NPCs and to repair themselves. NPCs themselves would gain resources in the same way that players do and would spend them on repairing, rearming and respawning.

Battles getting progressively bigger

As a match progresses along the tug-of-war chain of battlescapes, the battles get bigger and bigger:
If we say the red team win the first battlescape, they force the blue team back into a blue-controlled battlescape.
The facilities in that battlescape have been accumulating resources for the duration of the fight for the first battlescape so have more resources at their disposal. (Up to a limit, as @Playbenni also suggests) These resources can be distributed to the blue players and NPCs resulting in more ships and more capitals on the ‘retreating’ blue team.
As for the ‘advancing’ red team, as they are attacking a blue-controlled battlescape they have no existing facilities in the battlescape, but they bring a load of NPCs from the previous battlescape and the players retain their personal resources (which on average would be more than the defeated blue players).
With their initial concentration of numbers, the advancing team should gain a foothold in the battlescape by capturing a facility and starting to gain resources there.
With a little fine tuning this should result in a reasonably balanced situation so the advancing team does not snowball getting more and more powerful, but both teams get bigger and bigger as the match gets closer to either end of the tug-of-war chain.

In our imaginary scenario, if the blue team defeat the reds in this 2nd battlescape, the battle moves back to the 1st battlescape where there’d be a bunch of destroyed facilities (not generating any resources) and a bunch of red facilities (either originally red or captured).

This gives more consequence to whether a facility is captured or destroyed.

If the next active battlescape would be one in which all the facilities have been destroyed, then that battlescape is skipped and the next one in the tug-of-war ‘chain’ becomes the active one. This reduces the likelihood of the tug-of-war going back and forwards indefinitely.

And breath. Actually I spent over an hour on this with plenty of thinking and breathing time

Tjafaas · May 11, 2018, 6:39pm

I know that most people won’t agree with my affirmation, but I’d also like to remind that the original MMOs were linked with RP. Persistence was kind of pre-requisite, both for consistency and enhanced gameplay / functionalities. It doesn’t mean that the absence of persistence automatically excludes a game from being a subset of MMO definition.

Fair enough, although your assumption mostly depends on the current and maximum players allowed.
OK, then for two teams, keep an odd number of total available bases (like 5 or 7) with one bases allocated for each team. And randomize the available bases, so that each restart won’t feel the same.