In mobile game Network Wars (Jim Rutt, 2021) you have one job. Conquer the network. But you’re competing against three AI players trying to do the same.
At first, I won a lot of games. And then, I lost some games. As I didn’t think I was developing much of a strategy, I began to view Network Wars as a slot machine rather than a strategy machine. As I couldn’t see how Network Wars executed each skirmish, I couldn’t extrapolate how a player might successfully plot against the AI.
Every game, I would plunge in with “some tactics” and win or lose due to circumstances apparently out of my control. What choice did I have anyway?
I’m afraid, Joel, you had all the choice in the world.
The Network Wars instructions are quite skimpy. Rutt might as well replace the in-game manual with the phrase “Fight Me”. Still, I’m much wiser now, mainly thanks to Frank Lantz.
Alright, each node carries a number; this is the number of armies on that node. You play the red network and always go first. You have a single verb in your vocabulary, and that verb is attack. When you send a node to attack a neighbouring node, the game uses a sequence of coin flips to determine who wins. Whoever loses a coin flip, loses an army. Network Wars keeps coin flipping until the attacker drops to one army or the defender is overrun. If the attacker wins, one army stays behind and the rest occupy the defeated node.
Once you’ve attacked all the nodes you want/are able to, you end your turn. At this point, new armies equal to the size of your largest node network are distributed across the front line of that network.
Then each AI gets their chance to shine with the same rules. The game continues until one faction controls 24 nodes – or you are wiped out.
That’s good, but it’s not enough to really know Network Wars. You need to figure out what impulse drives the AI’s assault. Going back to mobile favourite Slay (Sean O’Connor, 1995), I have a lot of advice for Slay players on how to avoid provoking the opponent AI:
Positioning peasants on your border is the idiot move as the AI cannot resist an easy kill. Unless it’s distracted elsewhere, it will actively send any available meat grinder to mince up the peasant, knowing it is obliterating hard-earned coin. If you can’t defend, then, for the love of dog, don’t give it a reason to attack.
In Network Wars, sometimes the AI left me alone and sometimes I was shanked hard and fast, and initially I had been unable to draw conclusions about why this was. Reading Frank Lantz’s writeup about Network Wars gave me the wisdom I sought. It seems the AI will only attack nodes of lower value; it won’t do something “smart” like a human would, such as using a weak node to soften up a target, then sending another node in to finish the job.
After this revelation, I began to appreciate how seemingly hopeless situations are actually salvageable. Now I take note of the length of my border as a short border intensifies reinforcements. Now I see the danger of lunging into enemy AI territory too early, because it can create a path of low-value nodes for the AI to follow back into the weak meat of your territory. Now I look for opportunities to encourage the AI to attack each other.
For all this talk of strategy and depth, the thing is, a Network Wars match is so short you could treat it like a clicker game. Move armies, you win. Move armies, you lose. If you don’t know what you’re doing, then moving armies is just an alternative to rolling dice. You can be done in a few minutes then start all over again… which was what I was doing until I read Lantz’s post.
Knowing that the AI always goes after low-value fruit is the crucial piece of information which allows you to get into the prediction business. I could probably have figured this out in time but the game executes AI moves quickly and it’s more difficult to unpack what has happened than you’d think. While you can ask the game to execute the AI attack phase more slowly, so many nodes change colour that it can be difficult to remember who did what to whom in an attempt to fathom why.
However, the key takeaway is that attacking is très dangereux. Attacks will leave a node with value 1 behind them and if that node is accessible to any AI opponents, your attack creates a weakness, like a flaw in the network material. And you can’t redistribute armies from node to node – remember, your only verb is attack. This simplicity makes for some difficult decisions. Sometimes the best move is to wait. Sometimes the best move is to bait.
In developer Jim Rutt’s podcast, Frank Lantz suggested to Rutt that not every level is beatable. Rutt refuted this because, being the developer, he has a power denied his players – to retry a failed level. He’s never encountered an impossible level. But what about all those coin flips? Rutt revealed a fascinating design detail: all players get the same procedurally-generated levels and even the same dice rolls. If Rutt has found a solution, that solution is there for all players to find.
Some of the levels present a hideous starting configuration and, invariably, I lose those games. So I don’t know if the solutions to tricky levels are buried in amber like those painful Slay levels where players have to mine for the correct sequence of bad decisions that establish an unexpected opening in the far future. Digging up the decision tree with a brute force shovel to find this is not interesting and you’re just back to dice rolls again. But Network Wars doesn’t have this problem because it takes away your brute force shovel. You’re never allowed to linger on a level that crumbles beneath your swipes.
What Lantz found exciting about Network Wars was how the AI are simple machines and not really intelligent. For him, the enemy is the game’s system of rules. Looking at it this way, every level is actually a puzzle with an unpredictable element. While the narrative paint tries to make you feel like you’re part of a conflict, what you’re really doing is solving a puzzle.
But Lantz goes further, highlighting that once a player can reduce their play to an algorithm, that’s when a deep game ceases to be. You’re no longer playing but executing the solution to a puzzle. I’d have to agree. The learning bit where you’re assembling strategy is the best bit of cerebral games like this. Figuring out the solution algorithm is the actual victory over your real opponent: a system of rules.
Although not exactly the same situation, I remember the euphoria of achieving something monumental after I had figured out how to solve all thirty levels of the Domination mode in Death Crown (CO5MONAUT, 2019). But that moment was simultaneously the death of the game. There are no more highs to be found unless you can boost the challenge. Such as, oh I don’t know, defeating the game in front of a live audience?
Despite the basic truth that mastering a game like Network Wars is about coding an algorithm to defeat an algorithm, I am still enraged whenever one of the AI enemies bores a tunnel through my nodes. Nothing can explain the hatred I have for that AI, which was just following orders. Sure. I’ve heard that one before.
In the algorithm war, I am, first and foremost, human.