What we fixed

A MiniTroopers battle is a small Flash program, the game file, that a player called Ruffle plays in your browser, since browsers no longer play Flash themselves. BetterTrooper plays the very same game file as trooperstest.gued.es, with the fixes below, in its own copy of Ruffle, which has fixes of its own, and adds controls around the game, fixed here too when they went wrong. The battles themselves do not change: trooperstest.gued.es decides who wins, and we only show it better.

Each fix below says what went wrong, what we changed and what it changes for you. Where you can see it, the pictures and videos show the same moment of the same battle, Before and After the fix.

Battles that froze, or showed the wrong thing

Bugs of the game itself: trooperstest.gued.es has them too. Each one was found on a real battle, reported by a player or met while testing, then fixed in the game file.

Rounds refilled between waves

· in the game file

Between two waves, Rucksack and Munitions refill the rounds a trooper keeps outside his clip; the game forgot Rucksack's rounds, sometimes showed its number over the wrong trooper, and gave Munitions' rounds to a pilot's vehicle too, which the battle does not: a trooper's card now shows the rounds he really has.

What went wrong. A trooper's card shows, for each of his weapons, the rounds in its clip and the rounds he keeps in stock; every reload takes the rounds it loads from that stock. Two skills refill the stock between two waves, and the game's display did not do what the battle itself did. Rucksack fills the stock of the weapon in the trooper's hand: the display only showed the number of rounds over him, without adding them, so his card stayed short, and a later reload could even take it below zero. The battle also lists that number only for the troopers who got rounds, while the display handed the numbers out one per trooper in turn: when one of them got nothing, the next one's number showed over him. In battle 16591354, Nguers and Crakonmark use Rucksack at time 169; only Crakonmark gets rounds, 6, but the +6 rose over Nguers and a +0 over Crakonmark. Munitions refills every weapon of the troopers it reaches, but only their own weapons, not their vehicle's: the display filled a pilot's vehicle weapons too. In battle 12326642, Mr.Hagenberg's Light Tank showed 46 rounds in its machine gun's stock and 2 in its Cannon's, where the battle has 23 and none, until his tank was destroyed.

What we changed. Rucksack now fills the stock of the weapon in each trooper's hand, as the battle does, and shows its number over a trooper only when he got rounds, so that each number rises over the right trooper. Munitions leaves a vehicle's weapons as they are. A jump, which rebuilds the troopers from the battle's record, already gave the right stocks; watched straight through, they are now right too. The rounds in the clip, which the ammo bar over a trooper shows, were not touched by either skill.

For you. A trooper's card shows the rounds he really has, and Rucksack's number rises over the trooper who got the rounds. It was not rare: in 10 of our 54 recorded battles, a trooper's stock went wrong this way at some point, short after Rucksack in 8 of them, too high on a vehicle after Munitions in 5; it now matches the battle in all of them.

Before
After
Battle 16591354, between two waves (time 169), at half speed: Nguers (top right) and Crakonmark (left) use Rucksack; only Crakonmark gets rounds, 6.
Before Before: Mr.Hagenberg's card: his Light Tank's Cannon shows 2 rounds in stock and its machine gun a full row of 46, more than the battle gives them.
After After: Mr.Hagenberg's card: his Light Tank's Cannon shows no round in stock and its machine gun 23 of 46, as in the battle.
Battle 12326642, second wave, after Munitions: the card of Mr.Hagenberg, in his Light Tank, which Munitions does not refill.

Watch it in battle #16591354, from a few events before.

An empty ammo bar after reloading

· in the game file

A weapon that fires two rounds a shot, such as the Dual pistols under Nervous, can end a burst with shots that fire nothing; the game took a round for each of them anyway, so after the reload the ammo bar stayed short, even empty, though the trooper went on firing; it now shows the rounds he really has.

What went wrong. When a trooper reloads, a small bar over his head shows the rounds in his clip, one notch per round. Some weapons fire two rounds a shot: the Dual pistols, the Double-barrelled Shotgun, the Helicopter's Apache Cannon. The battle limits a burst to as many shots as there are rounds in the clip, not half as many, so the last shots of such a burst can come with an empty clip and fire nothing. Nervous, which makes a trooper fire his whole clip in one go, shows it best: with 8 rounds in his Dual pistols, he fires 8 times, and the last 4 shots fire nothing. The battle itself counts that right: the clip stays at 0. The game's display took a round for each of those empty shots anyway, so its count fell below zero, and every round loaded afterwards only filled that hole. In battle 16712052, Gaspard, Nervous, fires his Dual pistols 8 times at 1030 at time 557, then reloads 4 rounds: the bar over his head stayed empty at every round he loaded, and he went on firing from what looked like an empty clip. His next reload still left the bar short. The game file of trooperstest.gued.es does the same.

What we changed. A shot now takes a round only while the clip still has one, as in the battle itself. A jump, which rebuilds the troopers from the battle's record, already gave the right count; watched straight through, the count is now right too.

What only the server can fix. The empty shots themselves: a trooper fires his empty weapon for the rest of his burst, without a bullet leaving it. That is the battle's own rule, which trooperstest.gued.es decides; we show those shots as the battle has them.

For you. The ammo bar shows the rounds a trooper really has: after Gaspard's reload, 4 notches of 8. It was not rare: in 8 of our 54 recorded battles, a trooper's count fell short this way at some point, often below zero, once with the Dual pistols under Nervous, otherwise with the Double-barrelled Shotgun or the Helicopter's Apache Cannon; it now matches the battle in all of them.

Before
After
Battle 16712052, last wave, time 557: Gaspard, Nervous, fires his Dual pistols eight times at 1030, then reloads 4 rounds.

Watch it in battle #16712052, from a few events before.

Crybaby stood a knocked-down trooper up

· in the game file

Crybaby made a trooper lying on the ground get up to cry, though he was still down, and at his turn he dropped flat at once and got up again; he now cries on the ground, drumming his feet, and stays down until he gets up.

What went wrong. Crybaby makes its targets burst into tears: each one cries on his feet, fists on his eyes. The game played that cry on every target, even one lying on the ground, who got up to cry. A trooper knocked down (by a grenade, a Charge, a shotgun at close range) stays down until his turn gets him back up, and the battle's record keeps him down through the cry. On screen, though, he stood up after crying, and when his turn came he dropped flat on the ground at once and got up again. In battle 12326642, Huffas is knocked down by a grenade at time 1125, is one of the two targets of Kurnov's Crybaby at time 1183, and gets back up at time 1275: watched straight through, he stood all that while. Since our fix of 6 November (knocked down, yet standing after a jump), a jump into that moment showed him lying, as the record has him, so the same moment looked different depending on how you got there.

What we changed. The game had no way to cry lying down, so we made one from its own drawings: fists on his eyes and the tears of the usual cry, his feet drumming the ground like a child in a tantrum. Crybaby now plays it on a trooper who lies on the ground, and the usual cry on everyone else. It lasts exactly as long as the usual cry, so the battle keeps its pace, and it ends in the pose his fall left him in, from which he gets up at his turn.

For you. A knocked-down trooper whom Crybaby makes cry stays on the ground, crying there, until he gets up, whether you watch the battle straight through or jump into it.

Before
After
Battle 12326642, a jump to event 2350, just before Kurnov's Crybaby at time 1183: Huffas, knocked down by a grenade at time 1125, is one of its two targets; he gets back up at time 1275.

Watch it in battle #12326642, from a few events before.

Knocked down, yet standing after a jump

· in the game file

After a jump, a trooper who had been knocked down stood instead of lying on the ground, then, at his turn, dropped to the ground at once and got back up; he now lies there until he gets up, as when the battle is watched straight through.

What went wrong. A trooper knocked down by a hit (a Charge, an explosion, a shotgun at close range) flies a short way, lands on his back and stays on the ground until his next turn, when he gets back up: "gets back up!" in the battle log. Watched straight through, that is what you saw. But a jump (the timeline, the event buttons, a line of the battle log, a link that starts at a chosen moment, the next wave) rebuilds every trooper from the battle's record, and the game always rebuilt him standing, whatever he was doing. In battle 16591354, Ivowinho is knocked down by a Charge at time 190 and gets back up at time 451; after a jump to event 582, at time 430, he stood among the bodies, and when his turn came he dropped flat on the ground at once and got up again. The game's own space bar, which skips to the next wave, did the same on trooperstest.gued.es.

What we changed. The battle's record already says which troopers are down. After a jump, each of them now lies on the ground in the pose his fall left him in, and gets up at his turn, as when the battle is watched straight through. Watching straight through does not change.

For you. Wherever you jump in a battle, a knocked-down trooper lies there until he gets up. It is common: our 49 recorded battles have 174 "gets back up!" between them, in 24 of the battles. Played straight through, battle 16591354 has 393 moments a jump can start from; at those moments, 190 times a trooper free to move was lying down, and each one now lies after a jump too, while every trooper standing there still stands.

Before
After
Battle 16591354, fourth wave, a jump to event 582 (time 430): Ivowinho, knocked down by a Charge at time 190, gets back up at time 451.

Watch it in battle #16591354, from a few events before.

Propaganda from a helicopter

· in the game file

A trooper who spread propaganda from his helicopter, or from any other vehicle, froze the battle: the trooper he was winning over kept flashing between the two sides' colours, forever.

What went wrong. In battle 16233583, at time 800, Grego, flying his Helicopter, issues command #2 and spreads propaganda: the enemy next to him is to change sides. The game shows it in three moments: the propagandist goes up to his target and points at him, a short countdown starts once he has finished pointing, during which the target flashes between the two sides' colours, and at its end the target joins the propagandist's side. A helicopter has no pointing move: the game kept the helicopter's hovering move instead, and waited for it to end. But hovering never ends, it starts over every few moments, and each new start put the countdown back to its beginning. The target kept flashing, and the battle waited for him and for Grego forever. Every vehicle is in the same case: the Motorcycle and the Heavy Tank have no pointing move either. The game file of trooperstest.gued.es freezes at the same moment.

What we changed. When the propagandist cannot point, a pilot in his vehicle, the countdown starts as soon as he reaches his target, and he keeps flying or driving as he was; at its end the target joins his side, as always. A propagandist on foot points exactly as before.

What only the server can fix. A pilot should not spread propaganda from his vehicle at all: no vehicle can point, and the game was never drawn for it. But who spreads propaganda belongs to the battle itself, which the game's server works out: it picks any trooper of the other side standing next to the target, a pilot in his vehicle as well as a trooper on foot. Putting it right needs a fix on the server, which would leave the troopers in a vehicle out of that choice, so that only a trooper on foot spreads propaganda. Our game file only replays the battle the server decided, so it shows Grego spreading it from his helicopter, without pointing.

For you. Battle 16233583 plays to its end, 493 events instead of 171. We also played that moment with Grego's helicopter shown as a Motorcycle and as a Heavy Tank: the old game file froze each time, the new one goes on.

Before
After
Battle 16233583, second wave, time 800: Grego, in his Helicopter, issues command #2 and spreads propaganda to the enemy next to him.

Watch it in battle #16233583, from a few events before.

A dodged punch that still killed

· in the game file

A punch that a trooper dodged could still do him 1 damage, when his attacker had both Fists of Fury and Death Grip, and kill him; the game showed a plain miss, and the dead trooper lay there with his ring, as if alive.

What went wrong. In battle 15886121, Mike charges Jeffapp Knox, who is left lying on the ground with a single point of health, then stomps him. Jeffapp has Dodger and dodges the stomp, and the battle log of trooperstest.gued.es says so: "Mike stomps the enemy! — missed Jeffapp Knox!", then, at once, "Jeffapp Knox is killed!". In the battle itself, a dodged blow counts as minus one point of damage. But Mike has two skills for his fists, Fists of Fury and Death Grip, each adding one point to a blow with his fists, and the game adds them after the dodge: minus one, plus one, plus one, so the dodged stomp still does 1 damage, enough to kill Jeffapp. The game file only showed the dodge: "miss" and "Dodger", no damage. Jeffapp kept his point of health and his ring, and lay there like a trooper only knocked down until the next wave. A player reported it on the remaster's Discord; the game file of trooperstest.gued.es does the same.

What we changed. When a dodged blow still does damage in the battle, the game file now takes it off, as it does for any blow: the 1 shows above Jeffapp, his health falls to 0, he dies and his ring goes. "Miss" and "Dodger" still show, since he did dodge. A dodged blow that does no damage, which is nearly all of them, shows exactly as before.

What only the server can fix. A dodged blow should do no damage at all: the fists' extra points should only count on a blow that lands. That rule belongs to the battle itself, which the game's server works out. Putting it right needs a fix on the server, which would leave a dodged blow at no damage whatever the attacker's skills: Jeffapp would then survive the stomp, as "missed" says. Our game file only replays the battle the server decided, so it shows that battle's outcome.

For you. A trooper killed by a blow he dodged now dies on screen, as the battle's log says, and his body lies without its ring. The battle itself does not change, nor its events or its winner. In our 47 recorded battles, troopers dodge 2,262 times, and only two of those dodges still did damage, both stomps for 1: this one, and one in battle 12326642 that did not kill, where Edunnell now loses that point of health too. Every other dodge shows exactly as before.

Before
After
Battle 15886121, first wave: Mike charges Jeffapp Knox, who has 1 point of health left, then stomps him; Jeffapp dodges the stomp, which still does him 1 damage.
Before Before: Jeffapp Knox lies alone at the top left with his green ring at his feet, as a trooper only knocked down.
After After: Jeffapp Knox lies alone at the top left without his ring: he is dead.
The same battle, a few seconds later, when Mike walks off to charge Warden.

Watch it in battle #15886121, from a few events before.

A rat that wrestled from its own square

· in the game file

A rat that came back to its square, where the trooper it had just fought was standing, and wrestled him from there, froze the battle.

What went wrong. In battle 15663964, at time 855, Schusanov punches Rat #11 and knocks it back. The rat gets up and runs back to its square, which is exactly where Schusanov now stands, then wrestles him to the ground. A rat's wrestle has three moments in the game: the rat runs to its target, the target falls, then the rat lands on him and bites. The game checks the second one at its next step, once the rat is close; here the rat was already there, 1 pixel away, and its run ended before that check ever came. The wrestle skipped the fall, and kept waiting for a moment that had already passed: Schusanov stayed standing with his shotgun under the rat, and the battle waited for both of them forever. The game file of trooperstest.gued.es freezes at the same moment.

What we changed. When the rat's run ends before the fall has been shown, the fall is shown first: the target puts his weapon away, goes down and turns to the rat, then the wrestle goes on as always. A rat that starts farther away wrestles exactly as before.

For you. Battle 15663964 plays to its end, 137 events instead of 125: Schusanov goes down, gets back up and fights on with his fists, as the battle's log says. In our other recorded battles, rats wrestle 28 times, always from farther away: none of them froze, and they show as before.

Before
After
Battle 15663964, second wave, time 855: Rat #11, knocked back by Schusanov's punch, gets up, runs back to its square and wrestles him.

Watch it in battle #15663964, from a few events before.

Bodies that got back up

· in the game file

When a shotgun knocked a trooper down and Lucky Charm saved him from his fall or from a later pellet of the same shot, the game showed the hits in the wrong order: a body without its ring then got up, to celebrate the victory or to go back into the fight.

What went wrong. In battle 1945932, at time 675, 1030 fires his Double-barrelled Shotgun at Huffiwen, Vlad's ammunition man, who has 10 points of health left. The first pellet hits him for 9 and knocks him down, and the fall costs him 2 more; the second pellet hits him for 14. In the battle itself, the fall comes right after the first pellet: Huffiwen's Lucky Charm saves him from it with a single point of health, then the second pellet kills him. The game showed it in another order: both pellets while he flew through the air, then the fall when he landed. So it killed him in the air and took his ring away, then, when he landed, Lucky Charm gave his body its point of health back. The body lay there like a trooper only knocked down, and when Vlad won the battle it got up and walked off to celebrate.

The same mix-up worked the other way round when Lucky Charm saved the trooper from a later pellet instead of his fall. In battle 663711, at time 1600, Yosefuberg fires his Double-barrelled Shotgun at G.I.Ngukins, the doctor. The first pellet hits him for 7 and knocks him down, and the fall costs him 2; a later pellet hits him for 9, and his Lucky Charm saves him from that one. In the battle itself, the fall comes first, then the 9 that Lucky Charm stops: G.I.Ngukins keeps a single point of health and gets back up. The game showed the 9 while he flew, Lucky Charm leaving him his point of health, then the fall when he landed, which took that point away: he died there and lost his ring. Then, when the battle had him get back up, his body stood up and went back into the fight without its ring, until he was killed at time 1819. In battle 166976, a doctor even healed a trooper the game showed dead. Players reported these battles on the remaster's Discord; the game file of trooperstest.gued.es does the same.

What we changed. While a knocked-down trooper is still in the air, the next pellets of the same shot now wait until he lands, after his fall, when Lucky Charm is in his fall or in those pellets: the game shows them in the battle's own order. In battle 1945932: 9, then, when Huffiwen lands, 2 and Lucky Charm, then 14, which kills him; his ring stays at his feet until then, and his body stays on the ground at the end. In battle 663711: 7, then, when G.I.Ngukins lands, 2, then the 9 that Lucky Charm stops; he keeps his point of health and his ring, and gets back up alive. When Lucky Charm has nothing to do with it, the order changes nothing, and the pellets show as before.

What only the server can fix. The two pellets hit Huffiwen at the same moment, so his fall should come after both of them. But that order belongs to the battle itself, which the game's server works out: the first pellet, then the fall, then the second pellet. Putting it right needs a fix on the server, which would first apply the damage of the two pellets fired together, then the damage of the fall. In battle 663711, that order would change the outcome: Lucky Charm works only once, so it would already be spent on the 9 when the fall comes, and the fall would kill G.I.Ngukins. Our game file only replays the battle the server decided, so it shows that battle's order.

For you. A trooper that Lucky Charm saves stays alive, a trooper killed right after stays dead, and only the living get up, to fight on or to celebrate. The battle itself does not change, nor its events or its winner. In our 52 recorded battles, troopers are knocked down 463 times; ten times, the same shot hits the trooper again while he flies, and Lucky Charm is part of it four times, in battles 1945932, 663711, 166976 and 5686815: the other six show exactly as before.

Before
After
Battle 1945932, the end: Liamersen wins the battle for Vlad. Huffiwen, top left, was killed at time 675 by the second pellet of a shotgun, right after Lucky Charm had saved him from his fall.
Before
After
The same battle at time 675, in slow motion: 1030's Double-barrelled Shotgun hits Huffiwen for 9, which knocks him down, and for 14; his fall costs him 2, and Lucky Charm saves him from it.
Before
After
Battle 663711 at time 1600: Yosefuberg's Double-barrelled Shotgun hits G.I.Ngukins, the doctor, for 7, which knocks him down, and for 9; his fall costs him 2, and Lucky Charm saves him from the 9.

Watch it in battle #1945932, from a few events before.

A trooper's card, cut off

· in the game file

A trooper's card could open partly outside the battlefield: beyond its edge for a trooper far beyond it, below it for the first card of a battle and for a high-level trooper with many skills; it now always shows whole, wider when it has to.

What went wrong. A click on a trooper opens his card: his class, his level, his weapons and every one of his skills. The game slides it from the trooper towards the middle of the battlefield, and keeps it inside the height of the battlefield by the height the card has when it opens. That was not enough. The card of a trooper far beyond an edge ran off that edge. The first card of a battle gets its skills a moment later, once their pictures are loaded, and ran off the bottom when it opened low on the field. And a high-level trooper has so many skills that his card is taller than the battlefield: in battle 13449126, the card of Duncescu, a level 50 Comms. Officer, never shows whole, wherever he stands.

What we changed. A card now always shows whole inside the battlefield: it opens beside the trooper as before, and is moved just enough to stay inside. A card that would be taller than the battlefield is laid out wider instead, one more skill per row each time, until it fits.

For you. Every trooper's card can be read in full, the high-level ones' included, and the cards of the troopers beyond an edge too, which a click on their marker opens. Nothing else changes: the battle and its events are the same.

Before Before: Duncescu's card runs off the bottom of the battlefield: most of his skills cannot be seen.
After After: Duncescu's card, a little wider, stands whole inside the battlefield, all his skills in sight.
Battle 13449126: the card of Duncescu, a level 50 Comms. Officer, opened by a click on him, the first card of the battle.

Watch it in battle #13449126, from a few events before.

Pushed out of the picture

· in the game file

A hit could push a trooper beyond the edge of the battlefield, where he fought on unseen, and a jump put him back in sight; he now stays where the hits took him, and a marker at the edge gives his name and what he is doing.

What went wrong. Each hit pushes its trooper back a little, as many pixels as its damage, and nothing stops him at the edge of the battlefield: a burst of explosive shells at close range can push him out of the picture. In battle 13257422, Toddauer is pushed beyond the right edge by a Heavy Machine Gun at time 91, comes back to life with Survivor and, at time 301, throws a Gas Grenade from there: for whoever watches, a grenade thrown by nobody, at a fight that seemed over. And when you jumped to a later moment (the space bar, the timeline, an event), he was back in sight on his square: the push lived only on the screen, and a jump forgot it, so the battle did not look the same whether you watched it straight through or jumped. A player reported it on the remaster's Discord; the game file of trooperstest.gued.es does the same.

What we changed. A trooper standing beyond the left or the right edge now has a small marker at that edge, at his height: his name then ▶ on the right, ◀ then his name on the left. Under his name, a word tells what he is doing: Standing, Aiming, Firing, Reloading, Down… or what the game shows over him, the name of a skill he uses such as Survivor, a dodge; when he is hit, his health bar shows there instead, as over a trooper in sight. Click the marker and his card opens. When he walks back towards the field, his marker stays, reading Moving, until he is in sight again. And when he lies dead there, his name is dimmed and struck through in red. And the push is now worked out with the battle itself, the way the game draws it, along the bullet from the shooter's gun to where it hits, with the same few pixels of chance as before, now drawn from the battle's own seed instead of anew at every viewing: the pushes are the same every time you watch a battle, and a jump puts every trooper where the battle had taken him, out of the picture included.

For you. You can always tell who is fighting from beyond the edge, and where. A battle looks the same whether you watch it straight through or jump around in it: in our 43 recorded battles, the hits push 6 troopers out of the picture, 4 on the left and 2 on the right, and after a jump every one of them stands where the battle had taken him. Across all troopers, a jump now puts 6 % of them more than 12 pixels from where watching straight through has them, against 23 % before; what remains comes from the few steps the game takes on screen alone, such as a doctor walking to his patient. The battle itself does not change, nor its events or its winner. After the battle where it was reported, two more pairs show a test of ours where every hit pushes three times harder, before and after the fix, to see more troopers out of the picture: how they are pushed out, then what they do from there.

Before
After
Battle 13257422, time 301: Toddauer, pushed out of the picture on the right by explosive shells earlier in the wave, throws a Gas Grenade from there at Rossell, on the far left.
Before
After
A test of ours where every hit pushes three times harder, before and after the fix, so this scene never happened (battle 14525443): hits push Vexalvard, then Magnitt, out of the picture on the right. Before, they just vanish; after, their markers follow them, Magnitt's Lucky Charm saves him once, the next hit pushes him farther, and both fall.
Before
After
The same test, later in the battle: Alberoter fights on from beyond the right edge; a grenade blinds him, he switches weapons, then walks back into the picture. Before, nothing showed he was there until he walked in; after, his marker stays until he is in sight.

Watch it in battle #13257422, from a few events before.

Back from the dead, without his ring

· in the game file

A trooper brought back to life by Survivor stood up without the ring at his feet that every other trooper has; he now gets one back, in red.

What went wrong. Every trooper walks on a green ring, which goes away when he falls. Survivor brings a fallen trooper back to life at the end of the wave. In battle 131943, Nierilton, Vlad's saboteur, is shot through the heart by a Light Tank at time 533, then stands up again with Survivor: without his ring, while each of his teammates keeps his own. The game takes the ring away when a trooper dies, and Survivor, which puts him back on his feet, never gave it back. A player reported it on the remaster's Discord, with battle 129753, where a doctor came back the same way; the game file of trooperstest.gued.es does the same.

What we changed. A trooper brought back by Survivor now always gets a ring back, a red one: you can tell at a glance who has already come back from the dead. It follows him until he falls again, and it is there too when you jump to a later moment of the battle.

For you. In our 42 recorded battles, Survivor brings 128 troopers back to life, in 13 battles: each of them now stands on a red ring. The battle itself does not change, nor its events or its winner: only the ring is drawn.

Before Before: Nierilton stands without a ring at his feet, among his teammates on their green rings.
After After: Nierilton stands on a red ring, among his teammates on their green rings.
Battle 131943: Nierilton, Vlad's saboteur, top right, killed by a Light Tank at time 533, has come back to life with Survivor and walked back to his teammates.

Watch it in battle #131943, from a few events before.

A fatal blow stopped by Lucky Charm

· in the game file

When Lucky Charm saved a trooper from a fatal blow, the game showed only the weapon's few points of damage, without the fatal blow, while the trooper was left with a single point of health.

What went wrong. Lucky Charm keeps a trooper alive with a single point of health when a blow would kill him. In battle 8308247, Vega stabs Hugo in the heart: a fatal blow. Hugo had 28 points of health; Lucky Charm saves him with 1. He lost 27 points, yet the game showed only the knife's 3 above him, and nothing said that the blow had been fatal: only his health bar, falling to almost nothing, gave it away. The battle log of trooperstest.gued.es writes it the same way ("hit Hugo in the left torso for 3 dmg!"). A player reported it on the remaster's Discord; the game file of trooperstest.gued.es does the same.

What we changed. When Lucky Charm stops a fatal blow, the game now shows the blow as it was: "shot to the heart!" (or "headshot", "punctured lung", "gutshot", wherever it landed) above Lucky Charm, and the points of health the trooper really lost, here 27, instead of the weapon's damage. When the trooper had less health left than the blow's damage, that number is the smaller one, the points he really lost. A blow that was not fatal, but whose damage alone would have killed the trooper, is shown as before, with its damage and Lucky Charm.

For you. You can see why a trooper's health falls to a single point. The battle itself does not change, nor its events or its winner. In our 36 recorded battles, Lucky Charm saves a trooper 111 times, and 28 of those saves stopped a fatal blow: those 28 now show as such. The battle log under the game comes from trooperstest.gued.es and still gives the weapon's damage.

Before Before: Above Hugo: Lucky Charm and 3, while his health bar is all but empty.
After After: Above Hugo: shot to the heart!, then Lucky Charm, then 27, the health he lost; his health bar is all but empty.
Battle 8308247, time 331: Vega, in orange, stabs Hugo in the heart with a knife; Hugo's Lucky Charm keeps him alive with 1 point of health out of 28.

Watch it in battle #8308247, from a few events before.

Poison damage before the grenade

· in the game file

A poisoned trooper could take a point of poison on screen before a grenade aimed at him had landed; when Lucky Charm saved him from that point, he then died twice, at the grenade and again at the next point of poison.

What went wrong. Some troopers' grenades poison what they hit. The battle log says it in the right order: "Orbit throws Fragmentation Grenade … hit Vancenser in the right arm for 1 dmg! (Poisoned!)", then, a moment later, "Vancenser takes 1 poison damage!". The battle itself, decided by trooperstest.gued.es, happens in that order too. The game's display, though, let a point of poison go through as soon as its moment came on the clock, without waiting for anything, while the grenade still had to be thrown, fly and land: Vancenser lost his first point of poison more than a second before the grenade that poisoned him exploded. A player reported it on the remaster's Discord; the game file of trooperstest.gued.es does the same.

With Lucky Charm, the wrong order changed more than the timing. In battle 4737281, at time 0, Xandoley Lee, already poisoned by a shot of Diddy's CK-Magellan, is hit for 7 by Diddy's grenade, which leaves him a single point of health; the point of poison that comes right after would kill him, and his Lucky Charm saves him from it. In the battle itself, he lives on with that point until the poison kills him at time 35. The game showed the point of poison and Lucky Charm first, while the grenade was still in the air; then the grenade landed and killed him, and a moment later the poison killed his body a second time. Another player reported it on Discord: a trooper who died twice.

What we changed. A point of poison now waits until whatever another trooper aims at the poisoned one, a grenade, a shot, a blow or even a heal, has landed. While the trooper is busy with his own moves, his poison still runs on at once, as before. In battle 4737281: the grenade's 7, then the point of poison and Lucky Charm; Xandoley Lee stays on his feet until the poison kills him, once, at time 35.

For you. The poison shows up after the grenade that brings it, and a trooper that Lucky Charm saves from it stays alive. The battle itself does not change, nor its events, their order or its winner: only the moment the display shows a few points of poison moves. In the 29 battles we had recorded when we made the fix, 12 of their 572 points of poison waited that way, in 7 battles, for 1.8 seconds at most: behind 6 grenades, 4 shots, a rocket and a heal aimed at the poisoned trooper. A battle then ends at most 1.5 seconds later than before (battle 14113607), and 26 of the 29 end at the same moment or within a twentieth of a second.

Before
After
Battle 14525443, last wave, in slow motion: a Fragmentation Grenade thrown from the right lands by the two troopers on the left and poisons Vancenser, the lower one.
Before
After
Battle 4737281 at time 0, in slow motion: Diddy's grenade hits Xandoley Lee for 7; the point of poison that comes next would kill him, and Lucky Charm saves him from it.

Watch it in battle #14525443, from a few events before.

The helmet that came back

· in the game file

A trooper who lost his helmet got it back on his head in some of his moves, while it still lay on the ground.

What went wrong. In battle 12475703, at time 1436, Reyauer's pistol grazes Joner and knocks his helmet off: it falls to the ground and stays there. Yet Joner wore it again whenever he stood or took aim, and lost it again with each punch, until the end of the battle. A player reported it on the remaster's Discord; the game file of trooperstest.gued.es does the same. A trooper is drawn from parts, and a punch draws his helmet apart from his head. When he loses his helmet, the game takes it off the parts on screen at that very moment. Joner was still punching: his head, put aside for the punch, kept its helmet, and every move that shows that head showed it again.

What we changed. When a trooper's look changes, the game now updates every part of him, the ones put aside included, not only those on screen.

For you. A helmet that falls stays on the ground. Of the 190 helmets knocked off in our 30 recorded battles, 5 came back this way; none do now. Nothing else changes: the battle, its moves and every other picture are the same as before.

Before
After
Battle 12475703, the last two troopers: Reyauer's pistol knocks Joner's helmet off, then they fight on with their fists.

Watch it in battle #12475703, from a few events before.

A second Sniper, then white troopers

· in the game file

A trooper who picked up a second weapon of a kind he already had could freeze the battle; skipping the frozen wave with Space then turned every trooper white while acting.

What went wrong. Liamersen already carried a Sniper when he picked up a second one. In the battle itself, decided by trooperstest.gued.es, he then held the new one; the game's display only looked at the kind of weapon, and kept showing his first Sniper. Both look the same, so nothing showed it, until a Shock Grenade made him drop his weapon: the display dropped the first Sniper, the battle the second. Later, when he went to pick that second Sniper back up, the display could not find it on the ground: he waited for it forever, and the battle froze in its first wave, at time 821, without any error message. The game file of trooperstest.gued.es freezes at the same moment. A player reported it with a video.

The same player then pressed the space bar, which skips to the next wave: the battle went on, but every trooper who moved, fired, was hit or was healed turned all white while doing it, until the end of the battle. That white is a tool the game's authors left in: when an order has waited for about 12 seconds, it paints every busy trooper white, to show who holds the battle up, and it never goes away.

What we changed. The display now puts in a trooper's hands the very weapon he holds in the battle, not just one of the same kind: when he picks one up, switches weapons, dives for one or starts a new wave. The battle itself now tells the display which one, where it used to give only the kind. And the authors' white painting is gone.

For you. Battle 1334086 plays to its end, 1,403 events instead of 150. Should another battle ever freeze, the page now says so above the game, names the trooper it waits for when one holds it up, and records the battle so that we can fix it; the space bar still skips to the next wave, and the troopers keep their colours.

Before
After
Battle 1334086, first wave: Liamersen, bottom left, goes to pick up the Sniper he dropped.
Before Before: The battle was frozen; Space skips to the next wave, and the trooper who walks in is a white silhouette.
After After: The battle never froze; Space skips to the next wave, and every trooper keeps his colours.
Battle 1334086: the space bar pressed at the same moment on both sides, after 13 seconds of the freeze of the version before the fix.

Watch it in battle #1334086, from a few events before.

Shot in the heart, still standing

· in the game file

A trooper killed by a fatal shot that did no damage stayed on his feet until the end of the battle.

What went wrong. A fatal shot, "FATAL shot to … heart!" in the battle log, kills whatever its damage, and armour can bring that damage down to zero. The game showed a death only for a hit that did some damage: KongBlad lost his ring, dropped his weapon and never acted again, but stayed on his feet until the end of the battle. A player reported it on the remaster's Discord; the game file of trooperstest.gued.es does the same.

What we changed. A fatal hit plays the death animation even when it does no damage.

For you. The dead lie down. It is rare: of the 91 fatal hits of our 24 recorded battles, this was the only one without damage.

Before Before: KongBlad stands among the troopers, without his ring, although he is dead.
After After: KongBlad lies dead on the ground.
Battle 1777464, wave 2: KongBlad, the pilot, has just been shot in the heart.

Watch it in battle #1777464, from a few events before.

Rats in a black hole

· in the game file

A black hole grenade thrown at rats froze the battle: rats had no animation for it. They have one now.

What went wrong. A black hole grenade curls its targets up and pulls them into the hole, with an animation that every trooper has. Rats do not have it: on trooperstest.gued.es, the battle stopped there for good, as a player reported on the forum. Since the fix of the punched motorbike, below, BetterTrooper no longer froze, but the rats went into the hole stiff, in their standing pose.

What we changed. We made the rats their missing animation, out of their own drawings and the way the troopers' one is made: from the most stretched picture of their run to the curled-up pose they take when an explosion throws them, 36 pictures, played again and again on the way into the hole.

For you. Rats tumble into black holes like everyone else, and the battle goes on.

Before
After
Battle 6841660: Maxutt's black hole grenade on two rats, before the fix as on trooperstest.gued.es (slowed down twice).

Watch it in battle #6841660, from a few events before.

The dive and the weapon switch

· in the game file

A trooper who dived to pick up his weapon, then switched weapons at the same moment, froze the battle in its first wave.

What went wrong. A rocket missed Lukett, who has the dodge skill: he dived to pick up the weapon he had dropped. A dive that goes for a weapon waits for it on the ground first, and while it waited, the game thought Lukett was free: his next order, switching to his bazooka, started at that very moment. Then the dive started too, and threw away the switch's "I'm done" signal. The switch never ended, and the battle waited for Lukett forever, without any error message. The game file of trooperstest.gued.es freezes at the same moment.

What we changed. A dive marks its trooper busy from the start, as picking up a weapon already did: the switch waits for the dive to end.

For you. Battle 4372787 plays to its end, 2,509 events instead of 51. It only happened when a dive and the next order fell in the same split second: none of our other recorded battles froze there.

Before
After
Battle 4372787, first wave: a rocket misses Lukett, who dives to pick his weapon back up.

Watch it in battle #4372787, from a few events before.

The knife knocked out of hand

· in the game file

A trooper knocked down with a knife in hand was shown with his fists; from then on the game lost track of his knife, and the battle froze.

What went wrong. A punch knocked Aidenoop down while he held a knife. In the battle itself, decided by trooperstest.gued.es, a trooper knocked down keeps his knife; the game's display put it away and showed him with his fists. From then on, the two disagreed about his weapon. When a bullet made him drop it, a knife fell to the ground, but in the display's own records it was his fists that fell. When he rolled to dodge, the display handed him his rifle, which has no rolling animation: on trooperstest.gued.es, the battle froze right there; on BetterTrooper, which no longer freezes on a missing animation, he was left drawn all white, rifle in hand. And when he went to pick his knife back up, the display found no knife on the ground in its records: he waited for it forever, and the battle froze 56 events before its end. A player reported it with a video.

What we changed. A trooper knocked down with a knife keeps it in hand, as in the battle itself. With any other weapon, nothing changes.

For you. The right weapon is shown, and battle 13039664 plays to its end.

Before Before: Aidenoop is drawn all white, holding a rifle, his knife on the ground under him.
After After: Aidenoop looks as he should, his knife on the ground under him.
Battle 13039664, wave 9: Aidenoop, on the right, just after two dodge rolls.
Before
After
A moment later, Aidenoop goes to pick his knife back up, on the ground under him.

Watch it in battle #13039664, from a few events before.

The shattered decoy

· in the game file

The second pellet of a shotgun looked for a decoy that the first pellet had already shattered, and the battle froze.

What went wrong. A double-barrelled shotgun fires two pellets. Here, the first pellet killed a decoy, "bibi le clown", and decoys shatter and leave the field at once: they leave no body. The second pellet then looked for the decoy, found nothing, and the game stopped on an error, then again at every picture: frozen for good, 115 events before the end of a battle of 22 waves. The game file of trooperstest.gued.es freezes there too. On BetterTrooper, the End key answered "This jump is not possible.", which is how we found it.

What we changed. A pellet whose target has already left the field is skipped; the other pellets of the shot are shown as before.

For you. Battle 14525443 plays to its end. Other weapons with several hits look their targets up the same way: no battle has shown the problem with them yet.

Before
After
Battle 14525443, last wave: Toddlker fires his double-barrelled shotgun at the decoy "bibi le clown".

Watch it in battle #14525443, from a few events before.

The punched motorbike

· in the game file

A punch that missed a trooper on a motorbike asked the motorbike to dodge, an animation it does not have, and the battle froze.

What went wrong. When a punch misses, its target dodges, with a dodge animation. Edalone was riding a motorbike, and the motorbike has no such animation: the game stopped on an error and never went on, at event 189 of 309. The game file of trooperstest.gued.es freezes there too.

What we changed. When the game asks for an animation that a trooper or a vehicle does not have, it now keeps the one it was playing, and the battle goes on. That covers every missing animation, not only this one. The game file also tells BetterTrooper which animation was missing, in its anonymous measures, so that we can find the next ones.

For you. Battle 14113607 plays to its end.

Before
After
Battle 14113607: 初音ミク punches Edalone, who rides a motorbike, and misses.

Watch it in battle #14113607, from a few events before.

Faster and smoother

The same battles and, but for one small exception, the same pictures, with much less work for your computer. These fixes come in the order of their effect, the largest first. A picture has 25 thousandths of a second (25 ms) to be ready, for the 40 pictures a second of the game; the charts show what each fix saves, and the fixes in Ruffle alone take about a fifth off the time to prepare each picture of a long battle. Their values are approximate: averages over about twenty of our recorded battles when that makes sense, measured on one computer, at one moment, that yours will not match exactly; the gap between before and after is what counts.

Battles no longer slow down as they go on

· in the game file

Every gunshot left an invisible bullet trail behind, forever: the longer the battle, the slower the game.

What went wrong. Every gunshot draws a quick bullet trail. The game removes all its other effects when they end, but the bullet trails were forgotten: each one stayed, invisible, but still glowing, and Ruffle drew every one of them at every picture. 10 of them early in a battle, 48 later, and more and more: the longer the battle, the slower the game.

What we changed. A bullet trail disappears after 6 pictures, like the other effects.

For you. The game no longer slows down as the battle goes on. On our 7 recorded battles that last over a minute, the game managed about 35 pictures a second at the start, and only 17 fifty seconds later; with the fix, between 32 and 36 all along (it is made for 40).

Pictures per second during the battle (more is better; the game shows 40 at most)
The numbers
Battle timeBeforeAfter
0–10 s3536
10–20 s2835
20–30 s2232
30–40 s2036
40–50 s1733

Approximate values, measured on one computer at one moment: averages over our 7 recorded battles that last over a minute, their first 50 seconds.

The troopers' outline drawn once

· in the game file

The thin dark outline around every trooper was computed again 40 times a second, for every trooper on the field.

What went wrong. Every trooper, tank and helicopter has a thin dark outline that makes it stand out from the ground. The game draws it with a "glow" effect, and Ruffle worked that glow out again at every picture, for every one of them.

What we changed. The game already draws each picture of a trooper's animation once and reuses it; we add the outline to that drawing, once, instead of at every picture.

For you. The same outline, about 14 % less time to prepare each picture, and a fifth less work for the whole computer, graphics card included.

Time to prepare each picture (less is better)

Approximate values, measured on one computer at one moment: averages over 20 recorded battles, their first 30 seconds (the whole battle when shorter).

Hidden pieces left asleep

· in Ruffle

Thousands of hidden, motionless pieces of animation were checked three times at every picture; the player now lets them sleep.

What went wrong. The game keeps thousands of pieces of animation aside, off the battlefield: the parts of the troopers that are not shown at the moment, the drawings of their bodies. Ruffle, as Flash did, went over each of them three times at every picture, even when nothing about them could change: 1,500 to 5,400 pieces at every picture of our test battle.

What we changed, in three steps. First, Ruffle skips the pieces that are empty and motionless. Then it puts them to sleep: it no longer even looks at them, until something that could move them wakes them up. Last, it does the same for whole groups of motionless pieces. On 27 October 2026 we closed a rare case where a piece woken up in the middle of a picture could fall one picture behind. The same day we fixed a case that only pages showing several Flash games at once could meet: one game could take the wake-up call meant for another game's pieces, which then stayed still for up to 64 pictures. BetterTrooper shows one game per page, so its battles were never affected. The sleeping pieces also spare the explosions: each piece of debris starts its animation at a chosen picture, and each time Ruffle looks over the whole battlefield again, up to 50 times in one picture; it now looks at 580 to 780 pieces each time instead of 1,100 to 2,100. So on 1 November 2026 we removed the shortcut we had added for them in September, which looked at the started piece alone: it no longer saved anything we could measure, and it ran some of the game's instructions in another order than Flash does.

For you. Each step gives the same pictures to the pixel. The first one alone barely changed the time; the second and the third take about 8 % and 10 % off the time to prepare each picture of a battle that lasts over a minute, and the more pieces pile up as the battle goes on, the more they save. Explosions stay as smooth as with the shortcut: on our test battle, its busiest stretch of explosions takes no longer without it.

Time to prepare each picture (less is better; each step against the one before)

Approximate values, measured on one computer at one moment: averages over the 7 recorded battles that last over a minute, their first 30 seconds.

Bazooka rockets no longer slow everything down

· in the game file

The smoke trail of a flying rocket was blurred again at every picture, puff by puff: the slowest moments of a battle.

What went wrong. A flying bazooka rocket leaves three puffs of smoke behind at every step. Each puff is blurred, grows a little at every step and is blended with a "lighten" effect, so Ruffle blurred every puff again at every picture and drew a layer the size of the whole battlefield for each of them: up to 4,263 drawing passes for a single picture, where a quiet moment needs about 16. These were the slowest moments of a battle.

What we changed. The blur of a puff is drawn once for each of its sizes and reused, and the puffs are blended normally.

For you. The pictures slower than a tenth of a second, the hitches you can see, become five times rarer; at the worst moment of our test battle, 1,484 drawing passes instead of 4,263. The trail is a little greyer over light grass: the one change you can see among all our speed fixes.

Pictures slower than a tenth of a second, per 1,000 pictures (fewer is better)

Approximate values, measured on one computer at one moment: averages over 20 recorded battles, their first 30 seconds (the whole battle when shorter).

Before Before: A bazooka rocket flies over the grass, with a long white smoke trail.
After After: The same rocket, its trail a little greyer.
Battle 13449126: a bazooka rocket in flight. The only change you can see: its trail is a little greyer over light grass.

Animations that do not move are skipped

· in the game file

At every step, the game visited about 780 parts of animations, and 720 of them had nothing to do.

What went wrong. The troopers are made of parts, body, arms, weapon, helmet, each with its own little animation inside the others. At every step, the game visited all of them, about 780, to see whether they had something to do: about 720 had nothing.

What we changed. A part that has nothing to do is marked as resting, and the game skips it, with everything inside it, until something wakes it up.

For you. About 12 % less time to prepare each picture, with the same pictures to the pixel.

Time to prepare each picture (less is better)

Approximate values, measured on one computer at one moment: averages over 20 recorded battles, their first 30 seconds (the whole battle when shorter).

Fallen helmets and hit sparks cleaned up

· in the game file

Two more kinds of effects stayed in the game's lists after they had disappeared from the screen.

What went wrong. Two kinds of effects were never quite removed: the little effects that stick to a trooper when some hits land on him, and the helmets that fly off. Once gone from the screen, they stayed in the game's lists, and the game kept updating them: 236 of the first and 26 helmets by the end of one of our test battles.

What we changed. Both are removed with the effect they belong to, like every other effect of the game.

For you. Less work as the battle goes on, and about half as much extra memory for the browser by the end of a battle watched at ×16: about 500 MB instead of 980.

Extra memory taken by the browser by the end of a battle watched at ×16 (less is better)

Approximate values, measured on one computer at one moment: one measure each, on battle 13449126.

The battle starts right away

· in the game file

The game used to replay the whole battle in secret before showing its first picture.

What went wrong. trooperstest.gued.es decides the battle; the game file receives the armies and plays the battle again to show it. Before showing anything, it played the whole battle once in secret, as fast as it could, with the page frozen meanwhile: Ruffle is slower at this than Flash was, and a long battle froze the page for almost a second on our computer, about 4 seconds on one four times slower.

What we changed. The battle starts as soon as its first 40 events are known; the game works out the rest along the way, always 100 events ahead. We checked, event by event, that the battle is exactly the same.

For you. No frozen page before a long battle starts, and the battle shows up sooner: on a computer four times slower than ours, the battles that last over a minute appear after about 6 seconds of work instead of 9; short battles hardly change. A jump of the timeline to a part not worked out yet waits for it, under a loading bar.

Work before the battle appears, on a computer slowed down 4 times (less is better)

Approximate values, measured on one computer at one moment: averages over 20 recorded battles.

Smoke and shell casings drawn once

· in the game file

The blur of the smoke and the glow of the empty shell casings were computed again at every picture.

What went wrong. The smoke of explosions is blurred, and the empty shell casings that fly out of the guns glow. Each blurred or glowing thing costs Ruffle several drawing passes, at every picture, even when it only turns: once the troopers' outline was fixed, they were the largest share left.

What we changed. Their blur and their glow are drawn once, at the size they have on screen, into a picture that all the puffs or all the casings share, like a sticker; then only the sticker turns.

For you. The same look, a quarter fewer drawing passes, about 6 % less time to prepare each picture and 11 % less work for the whole computer.

Time to prepare each picture (less is better)

Approximate values, measured on one computer at one moment: averages over 20 recorded battles, their first 30 seconds (the whole battle when shorter).

Smoke puffs no longer pile up

· in the game file

Every puff of explosion smoke left an invisible copy behind, and the player kept looking after hundreds of them.

What went wrong. Each puff of explosion smoke is cut to shape by a mask, that the game put on the battlefield and never took away. The mask kept its puff alive, invisible: after 2,000 pictures of battle, 420 of each were still there, and Ruffle went over all of them at every picture.

What we changed. The mask leaves with its puff.

For you. About 6 % less time to prepare each picture over the first 30 seconds of a battle, with the same pictures to the pixel; the saving grows as the puffs pile up, about 13 % by the end of our longest test battle.

Time to prepare each picture (less is better)

Approximate values, measured on one computer at one moment: averages over 20 recorded battles, their first 30 seconds (the whole battle when shorter).

The graphics card's scratch space reused

· in Ruffle

Ruffle threw the graphics card's scratch surfaces away after every picture and asked for new ones, while its main supply only grew.

What went wrong. A blurred or glowing object is first drawn on a scratch surface of the graphics card. Ruffle threw these surfaces away after every picture and asked for new ones, 300 to 1,800 a second, and its main supply never gave any back: 42 surfaces at the start of a battle, 2,000 two minutes later.

What we changed. A scratch surface is kept and reused from one picture to the next, and given back after 4 pictures without use. Until 27 October 2026, the small block of settings that goes with each size of surface stayed for the whole battle, one more for every new size; it now goes back with its surfaces.

For you. About 37 % fewer surfaces asked of the graphics card, and about 5 % less work for the part of the browser that drives it. Since the correction, the graphics card also holds about 1,400 fewer buffers after a minute of our test battle, 29 % fewer in all.

Scratch surfaces asked of the graphics card for each picture (fewer is better)

Approximate values, measured on one computer at one moment: averages over 20 recorded battles, their first 30 seconds (the whole battle when shorter).

Buffers the graphics card still holds after a minute of battle (fewer is better; the correction of 27 October 2026)

Approximate values, measured on one computer at one moment: one run of battle 13449126 each, its first 2,400 pictures (a minute of the game).

A faster list of hidden pieces

· in Ruffle

Each time the game put a piece of animation aside, the player read its whole list of such pieces to avoid writing it twice.

What went wrong. The game puts pieces of animation aside all the time. Each time, Ruffle made sure the piece was not already on its list of pieces aside by reading the whole list, 1,000 to 2,000 entries long.

What we changed. An index tells at once whether a piece is on the list.

For you. That bookkeeping went from 0.56 % to 0.03 % of the browser's work: small, but free.

Share of the browser's work spent checking the list (less is better)

Approximate values, measured on one computer at one moment: one profile of battle 13449126 each.

Controls added to the game

What the replays of trooperstest.gued.es cannot do: built into the game file, for the buttons and keys of the player.

Pause and speed

· in the game file

A pause, and a speed from 16 times slower to 32 times faster.

What was missing. The replays of trooperstest.gued.es can be paused with a click on the battlefield, and sped up while a key is held, but not slowed down.

What we added. A pause and a speed from 16 times slower to 32 times faster, inside the game file: the game plays fewer or more of its own steps at each picture, so a slow motion stays smooth and a fast forward still plays every event.

For you. A close fight in slow motion, or a long battle in a few minutes; on a computer, the keys of the player are listed under its ? button.

Bugs that came with BetterTrooper

Bugs that trooperstest.gued.es never had, in what BetterTrooper adds: the jumps through a battle, the pause, the buttons and keys of its player.

A paused battle that stopped loading

· in BetterTrooper's player

A battle opened at a chosen moment could stop loading once paused; it now loads to its end.

What went wrong. While a battle opens, its simulation runs a little ahead of the picture until the whole battle is known. A link to a chosen moment sometimes left it stopped once it got there: on a paused battle, the striped end of the timeline stood still, and the rest of the battle out of reach, until play was pressed.

What we changed. The simulation always gets its usual pace back after such a link.

For you. A battle loads to its end, paused or not.

Watch it in battle #13449126, from a few events before.

Space and Page Up worked once on a paused battle

· in BetterTrooper's player

On a paused battle, Space and Page Up worked once only; each press now moves one wave and shows it.

What went wrong. On a paused battle, Space skipped one wave without showing it, then did nothing more, and Page Up kept going back to the start of the same wave (battle 17352995: wave 4, three times).

What we changed. Both now jump to the very start of a wave and show it, at every press. Page Up counts its quick presses: once, the start of this wave; twice, the wave before; three times, two waves before.

For you. Move wave by wave through a paused battle, forward or back.

Watch it in battle #17352995, from a few events before.

A held arrow key froze the battle

· in BetterTrooper's player

Holding the left arrow froze the battle, which kept going back for seconds after the key was let go; it now follows the key and stops with it.

What went wrong. A held key repeats about 30 times a second, and each repeat of the left arrow made a jump back of its own, which takes a tenth of a second or more. The repeats piled up: the battle froze, and kept going back for seconds after the key was let go, nearly a minute in our longest recorded battle.

What we changed. The repeats now add up into one jump per picture: the same distance, without the pile.

For you. Hold an arrow to move through a battle, paused or playing: the picture follows, and it stops when you let go.

Time the battle stays frozen once the left arrow is let go (less is better; the key held 3 seconds, the battle paused)

Approximate values, measured on one computer at one moment: averages over 20 of our recorded battles, each paused at 60 % of its events; the 12 shortest reach their first event before the repeats pile up.

Watch it in battle #17352995, from a few events before.

An empty battlefield after a step back while paused

· in the game file

On a paused battle, about one step back in six or seven showed an empty battlefield, only the rings left on the ground; the troopers now always show.

What went wrong. To go back, the game rebuilds the battlefield from a snapshot taken every few events, then plays on, out of sight, to the moment asked for. When that moment was a snapshot itself, there was nothing to play, and a paused game draws nothing on its own: the paused picture showed an empty battlefield, only the rings left on the ground. About one step back in six or seven did it (battle 17352995, paused at event 239, one step back).

What we changed. Such a jump now plays the one step the game would play next, which draws the troopers without moving the battle.

For you. Step back and forth on a paused battle: the troopers are always there.

Before Before: The paused battlefield is empty: no trooper, no body, no weapon, only pale rings on the ground where the troopers stood.
After After: The paused battlefield at event 238: the troopers, the bodies and the weapon on the ground, each in its place.
Battle 17352995, paused at event 239, then one step back with the back button of the timeline: event 238.

Watch it in battle #17352995, from a few events before.

Jumps to the end of a battle

· in the game file

Jumps close to the end could stall, and the End key replayed the whole last wave.

What went wrong. To jump anywhere, the game rebuilds the battlefield from a snapshot (see Jump to any wave or event). Every battle ends with a roll call of the troopers still standing, which our navigation took for one more wave, "wave 5 / 5" in a battle of 4 waves; a jump there landed without the dead of the last wave, and the battle stalled 3 events before its end. And the End key started from the beginning of the last wave and replayed all of it, which could take several seconds.

What we changed. The roll call is no longer a wave (30 September), and the End key starts from the last snapshot before the end (8 October).

For you. The end of every battle can be reached, and the End key gets there in 0.3 seconds on average instead of 1.1.

Time of a jump to the end of a battle (less is better)

Approximate values, measured on one computer at one moment: averages of 44 and 46 jumps over our 23 recorded battles; the battle that froze before the fix is left out.