8 ms·
Something to note about the 90s-era is that the "death ball" of cheap units was *aggressively* mitigated in almost all strategy games. * Civilization 1, 2, and
by dragontamer 5y ago
Something to note about the 90s-era is that the "death ball" of cheap units was *aggressively* mitigated in almost all strategy games.
* Civilization 1, 2, and 3 had "stacks", but if you kill one unit in the stack, you kill ALL units in the stack. As such, "death balls" were incredibly fragile, one well placed attack kills the whole stack.
* Command and Conquer has infantry, which get rolled over and instant-killed by tanks. The overall "death ball" of tanks can eventually reach endgame proportions of death, but the cheapest units are fully ineffective at death-balling.
* Starcraft had a 12-unit selection cap. It required a lot of clicks (on purpose) to create a death ball, so only the highest levels of players (with high APM) could attack-move with a whole army effectively.
- systemvoltage 5y agoWhat’s a “death ball”?
- Arrath 5y agoA massive, monoculture blob of either the cheapest and fastest to produce, or a reasonably effective as far as cost/time/damage output unit, used to just roll over the opponent's base. So, a few hundred riflemen or dozens and dozens of tanks. The death part of it comes from the numerical advantage, if an enemy unit walks into range of many times its number it'll get blown to hell before it can inflict meaningful damage, even if it is a technologically superior or inherently stronger unit.
- teawrecks 5y agoNot always monoculture. The most effective deathballs have a balanced composition of units which complement each other.
- Arrath 5y agoAbsolutely, this can vary. IME at least in the old days, it did tend to be a single unit type (eg Red Alert Medium/Heavy tank rushes, or a well timed Zerg Rush) but it is by no means a hard and fast rule.
- dragontamer 5y agoAoE2 is usually a monoculture, due to the nature of its upgrade systems. If your knights are +2 armor and +2 damage, you'll probably want a mono-culture of knights. Futhermore, a singular upgrade (aka: Cavalier research) immediately applies to all knights. Your +2 armor / +2 damage Cavaliers are probably superior to your +0 / +0 archers from the Feudal age, even if those archers are theoretically useful against some units. Strictly speaking: its not a monoculture: Scouts + Knights is the common combination for cavalry civs, because Knights lose vs Monks/Archers, while Scouts win vs Monks/Archers. Furthermore, Scouts share the +2 armor / +2 damage upgrade with Knights. But still, the upgrade system almost "forces" a monoculture (or close to a monoculture): its far more efficient to only research one or two units, rather than researching many, many different kinds of units.
- dragontamer 5y agoA situation that arises rather often in Axis and Allies, Civ4, Starcraft 2. It results because of math. To defeat 100 units of equal strength requires *more* than 100 units (!!!). Take for example 100 Zealots (Starcraft / Starcraft 2 melee unit). If you send 1-Zealot vs the 100 Zealots, it will die before it deals much damage. In fact, even if you send 10 Zealots vs 100 Zealots, the 10-Zealots will almost certainly die before dealing any lasting damage. (All Zealots have a "shield" that regenerates. You probably won't even get past the shield). As such, 100 Zealots can perpetually kill 10 Zealots over-and-over again. Your 100 Zealots can kill 1000+ Zealots (as long as they only attack 10-at-a-time). ---------------- Same thing with Axis-and-allies infantry / tanks, or many other strategy games. The "strength" of a ball of units is the *square* of their size. That is to say: 100-Zealots is 100x stronger than 10-Zealots (!!), not 10x stronger as you may initially assume. As such, both players end up building a bigger-and-bigger death ball as a primary tactic (which is in fact, unfun and stale). In Starcraft: Brood War, your 100-Zealots could only be grouped into groups of 12, meaning you need 18 actions to attack-move the group. In Starcraft 2: your 100-Zealots can all be in a single group, so you only need 2-actions (one selection + one A-move) to attack-move the group.
- stickfigure 5y agoIt's been a long time, but IIRC you could still group units in SC1 and bind them to number keys. So maybe only 12 at a time, but you could still navigate multiple groups of 12 with just a few keypresses.
- dragontamer 5y agoYes, you can. But it still means attack-moving 108 units (aka: 9 groups, all labeled 1, 2, 3, 4, 5, 6, 7, 8, 9) requires 18-actions. That is: 1 (select group 1), then a, then left click on the attack-area. Then 2 (select group 2), a, left click on attack area. Etc. etc. That's a difference of 18-apm (Starcraft Brood War) vs 2-apm (Starcraft 2). Furthermore, that "Group 1" in SC2 could have 150-units or 200-units (or 400-zerglings, lol) in it. They pretty much made death-balls have 10% of the APM requirement in SC2 compared to SC:Brood War. I'm all for making the game easier and more accessible: but the death-ball tactic was a little bit "too obvious" and kind of unfun to watch, compared to the tightly coordinated groups of 12 that SC: Brood War was famous for. The groups were too big, numerical advantage was the biggest advantage in SC 2 IMO.
- teawrecks 5y agoLarge ball of units that you move into your enemy territory to cause death. They can be a lot of fun, but 20 years ago they presented a significant challenge to pathfinding algorithms on slow CPUs. As noted above, different games used different strategies to address them.
- dragontamer 5y agoC&C is a clear counterexample however: all units can be selected as a group. That is to say: pathfinding was fast enough that it clearly wasn't a problem in C&C. But they clearly wanted to nerf infantry-based death balls. And boy oh boy, are infantry-death balls nerfed. An occasional infantry unit still finds its uses in C&C. They're incredibly cheap after all, and tanks have a difficult job killing infantry with their tank-cannons. So as long as you have a wall of tanks in front of your infantry, their rockets can contribute heavily in combat.
- jbay808 5y agoI find that scattering rocket soldiers randomly about the map and one's base is a far better and cheaper anti-air defense than building dedicated SAM sites. A small investment makes aircraft almost useless. But I'm pretty inexperienced at the game.
- dragontamer 5y agoAdvance Wars has a very similar unit composition to C&C units: rocket troops are cheap and can effectively damage tanks (while rifle infantry are even cheaper and go 1-to-1 vs rocket troops). Advance Wars has a bit of a rocket-troop deathball problem however. Rocket troops are so cheap and effective, that large masses of rockets overpower any possible opposition. Its clear to me that C&C had designed the "instant kill squish" effect to mitigate this problem. Maybe in playtesting, they tried it out and realized that rocket troops are just too powerful. A singular unit that truly does everything at very, very cheap prices.
- 5y ago
- Aachen 5y agoIt's kind of clear from context, but still this is the first I hear the term (as someone who played those games) and DDG also doesn't come up with anything useful (top result, for example, is about some item in Dragon Ball). So I was also wondering if I got it right, especially when there's a hundred non-jargon and equally concise ways to say that, e.g. 'large group'. To me this seems like a valid question.
- dragontamer 5y agoMy use of the term originates from the Starcraft 2 culture. Search on "Protoss Deathball", which is a well known, highly effective "tactic"... if a bit obvious. I'm sure the other games have their own terminology for the evolution of this "tactic".
- zeven7 5y agoIt's a common term in modern RTS, and it's got more meaning attached to it than simply "a large group". For example, in StarCraft 2, a full army of zerglings wouldn't be considered a "death ball" because it'd be so easily defeated with a few Colossus and high templars (units that deal a lot of splash damage, which zerglings are particularly susceptible to). A death ball is an army so powerful it's virtually unstoppable once it's formed. Players can try to achieve a death ball to gain a victory, but it's often expensive and leaves you vulnerable while you're building one. Also death balls are usually slow, and the opponent can use faster units to attack vulnerable parts of their base while the player building a death ball is out of position.
- munk-a 5y agoAoE2 also uses this term extensively especially within the context of ranger infantry. A clump of forty arbs will chew through the armor of even intended counters (like knights). One of the more interesting applications of this term I've seen is in TW WH2 (Total War: Warhammer 2) where a faction like Vampire Counts gets a lot of utility out of death-balling even trash tier units like skeleton warriors - so that opponent infantry and cavalry gets mired in the mass of unit collisions to make it easier to get a clean spell targeting off. I think the term is pretty well established at this point as evidenced by the derivative usages that are now popping up.
- jtolmar 5y agoA large group of units, generally with ranged attacks, where the most effective positioning is clumping them up into a ball. They hit a certain tipping point where fewer and fewer things work to counter them. If both sides have a death ball, then the smaller one loses by a bigger margin the larger the death balls get. In a made up but typical RTS, one swordsman beats an archer, ten archers are an even match for ten swordsmen, and fifty archers beat infinity swordsmen. In a 10v8 archer battle, the bigger side survives with about 3 archers, but in a 100v80 archer battle, the bigger side survives with over 50. This game has archer death balls.
- munk-a 5y agoMost games will counter this effect with area of effect damage. AoE has onagers for this purpose - which can easily deal immense damage to clumped and unaware archers - SC2 actually gives a lot of units AoE which is what prevents marine deathballs from being nearly as strong as they might otherwise be. 10 zealots and a clossus vs. twenty marines will be a pretty one-sided fight that will get more extreme the higher the numbers go.
- hjek 5y agoIn OpenRA infantry has a chance when a tank tries to run them over; especially thieves are good at this.
- blueflow 5y agoDon't forget the rocketeers. I usually produce a 2:1 combination of riflemen and rocketeers (spamming if eco allows it), and support it with tanks and arty/v2. I rarely found occasion to use thieves, usually as raid into their ore patches to steal harvesters or as stationary vision-givers since they can cloak themselves.
- deleted 5y ago[deleted]
- X6S1x6Okd1st 5y agoDo you have a source for the 12-unit cap being a game shaping design decision?
- myhf 5y agoThere's some good analysis here: https://tl.net/forum/brood-war/526252-newbie-question-about-unit-selection-limit https://tl.net/forum/brood-war/526252-newbie-question-about-...
- X6S1x6Okd1st 5y agoThat speaks to it being a game shaping, but not being an intentional design decision. I'm familiar enough with SCBW to have played on ICCUP (albeit as a D player)
- dragontamer 5y agoNo other game in that time (C&C or AoE) had a selection cap. Starcraft / Starcraft BW is very unusual as far as early RTS systems go, capping at exactly 12 units. When all your peers allow for infinite selection, and then you come out with a design that only allows for 12-unit selections... its clearly an explicit design choice. From there, we need to reverse-engineer the reasoning behind the design choice. -------- I too was a D player on Starcraft:BW. So much training and effort and yet only got to the bottom ranks...
- munk-a 5y agoMy Civ 3 pikeman has something important it wants to say to that tank of yours.
- skhr0680 5y agoCiv2 added some absurd hidden bonuses to AI units to give them a chance in the endgame. My veteran armors will never forget getting mowed down by knights.
- avereveard 5y agomost total annihilation units couldn't shoot past each other, the one who could where large, slow, fragile or otherwise unable t effectively blob due high weapon spread or vulnerability to splash damage.
- shoo 5y agototal annihilation aircraft were pretty fun things to blob, although they were fragile and vulnerable to splash damage, particularly to the flak weapons that were added in the expansion. a glorious thing about total annihilation was the ballistics model: ground units without dedicated anti-air weapons could attempt to fire their guns at aircraft -- nearly all the time they'd miss, but occasionally a heavy tank could land a lucky hit and maybe take out a cluster of aircraft. my favourite highly blobbable unit for fooling around in single player was advanced construction aircraft. i guess if you've got enough resource income to support 20+ advanced construction aircraft rush building lines of long-range artillery, you've probably already won.
- ikiris 5y agospring is the equivalent TA continuance compared to this post about openra
- bradleypowers 5y agoGosh, I really miss TA. I never felt like another RTS matched TA for variability, even though I basically only ever played against one friend.
- wingmanjd 5y agoIf you're feeling nostalgic, GoG.com has it for sale: https://www.gog.com/game/total_anihilation_commander_pack https://www.gog.com/game/total_anihilation_commander_pack
- farmerstan 5y agoI just bought it on steam a few months ago. $5. On my 10 year old system I had I think there was thousands of individual units running at the same time. I downloaded the mid Escalation with amazing unit, and was playing against 4 AI. At one point there were thousands of units all running at the same time and the battles were epic. I would throw 500 Fidos (my favorite original unit) to the AI and they would slowly get mowed down, but then I would Keep sending them in waves. It’s still so much fun!
- k__ 5y agoWasn't the grenade infranry pretty good against tanks in C&C? I remember building them en masse. Also, in StarCraft you could save groups, with 1-5 you had 60 units. I remember building masses of the same unit in these games.
- dragontamer 5y ago> Wasn't the grenade infranry pretty good against tanks in C&C? Nominally, it was rockets were the anti-tank infantry. But both grenades and rockets get squished with alt-move. Tanks are faster than infantry, so the tanks get the squish rather easily. The infantry player can defend against the squish by spamming "X" (which scatters your units in random directions). But given that tanks are threatening a one-squish kill + have faster movement, grenades are a rather poor choice to "death ball spam". Furthermore: a dead grenadier explodes, causing damage to all other nearby grenadiers (causing __cascading__ explosions), often times wiping out your own "death ball". That is to say: a "death ball" made out of grenadiers end up killing themselves more often than not. Grenades are primarily anti-infantry and anti-building units in C&C. They serve the job well in that regards. But its incredibly dangerous to spam these units in C&C. ----------- "Death Balls" existed in C&C, but you had to use far more expensive tanks to be able to get there. The cheaper units (rockets, grenadiers) were simply ineffective. Nod arguably had a good death-ball strategy with bikes, but bikes were weak vs infantry (though they outran infantry pretty severely). Light Tanks was a more reliable Nod-based death-ball IMO. > Also, in StarCraft you could save groups, with 1-5 you had 60 units. Not like Starcraft 2, where you can save a singular group of 400 zerglings with Ctrl-1. Even then, Starcraft 2 has Psi Storm and area-of-effect damage (banelings, colossus). So its not quite as easy to construct an appropriate "death ball", unless you've scouted out your opponent's build. So its not a "Braindead" kind of death ball, but... still a death ball at the end of the day. > I remember building masses of the same unit in these games. Nothing quite like Advance Wars mechanized infantry (aka: rockets). That was truly a single-unit deathball game, lol.
- skhr0680 5y agoInfantry were semi-viable in C&C1 because it was a slower game, but became comically useless in RA
- 5y ago
- peder 5y ago> Civilization 1, 2, and 3 had "stacks", but if you kill one unit in the stack, you kill ALL units in the stack. As such, "death balls" were incredibly fragile, one well placed attack kills the whole stack. That's not how I remember things TBH. Only something like a nuke would kill all units on the same tile.
- dragontamer 5y agoUnits in the field would die as a singular stack (aka: stack kill). There were two exceptions, and one exception-to-the-exception. * Cities had units die one-at-a-time. This means that to siege a city, you were forced to build a stack (!!!). Attacking cities was always a dangerous operation in Civ 1/2 (though made easier in Civ3). * Fortresses had units die one-at-a-time, but were relatively difficult to build. IIRC, they also took up room, so no farms or mines if you build a fortress. Still though, they served as a "city-lite". Civ3 revamped the fortress system rather severely, so this only really applies to Civ1 / Civ2... and the top-tier fortress in Civ3 (lower-tier fortifications IIRC didn't defend vs stack kills, only provided a minor defensive bonus). The exception-to-exceptions was the nuke, as you pointed out. A nuke can stack-kill even in the stack-kill immune zones (cities / fortresses).
- skhr0680 5y agoI think the only improvement that can’t exist together with fortresses in Civ2 is the airbase, and that can be a nuisance because airbases are bugged and act as a farm even on mined squares.
- UI_at_80x24 5y agoCiv1, Civ2, Civ2 Call to Power, all suffered from stacked unit insta-kill glitch that OP mentioned. I have very unpleasant memories of a spearman somehow being hidden in stacks of tanks and losing them all to a crossbow or pike. This happened too MANY times to forget; and though enough time has passed that specifics have faded the pain and frustration never will. =) Yeah I'm still kinda bitter about that.
- 5y ago
- tomjen3 5y agoWhen the remastered Red Alert came out, I beat the AI by Zerg Rushing medium tank production and just send overwhelming numbers, aiming to take out key buildings with the first or second wave. It worked pretty okay too.
- suby 5y agoThat's an interesting observation that I hadn't thought about before. Another interesting thing, to me anyway, is that for Starcraft 1 allowed for upgrades which improved the utility of your early game units. In other words your early game units are some of the strongest units in the game, just not by default. For example the Zergling could be upgraded 3 times for a stronger attack, 3 times for stronger defense, once for movement speed, and late game an upgrade for increasing attack speed. But you can hardly have death balls because of the 12 unit selection cap you mentioned. Plus you wouldn't want to have death balls of a single unit because units were designed to work well together, ie: zerglings paired with defilers / lurkers.
- azemetre 5y agoThere are many things that went in favor of SC1 versus SC2. Your workers had different HP, acceleration, and speed; this made each races economy slightly different (you could get away with a different amount of workers). You had high ground mechanics, where units on the low ground had a 50% chance at missing their shot. The unit selection, as you stated. The units for each race WERE broken and unbalanced. Lurkers were insane, siege units were, reavers were insane, etc; but every race had strong powerful units so it "felt" fair. It was the culmination of all the little things that led to a great game that is still played professionally today, over the span of 20 years. In fact, there's a great tournament that just started recently called the Afreeca Star League. You can see the games on youtube (randoming jumping into the middle of one): https://www.youtube.com/watch?v=MpYBYN4fuA0#t=56m0s&ab_channel=AfreecaTVeSports https://www.youtube.com/watch?v=MpYBYN4fuA0#t=56m0s&ab_chann...
- chii 5y ago> The unit selection, as you stated i'm not sure the unit selection cap was a game design choice - i recall it was a technical limitation added to the game so that the AI pathing could work properly (if you had unlimited unit selection, the pathing could take too long to run). But it turns out, this limitation also made the skill-cap of the game higher, and more fun in competitive mode.
- 5y ago
- skhr0680 5y agoRA popularized plain old tank rushes though. They were somewhat mitigated by RA2 in that units other than basic tanks were actually worth spending money on. Finally, Generals brought in “death balls” of rocket soldiers.
- mactrey 5y agoStarcraft I also discouraged death balls of ground units with the terrible pathing..
- thrower123 5y agoStarcraft also had a really low unit-cap. I think it was 200 points, so aside from the zergling rush (zerglings counted for 1/2 a point, iirc), you just couldn't really human-wave anyway.
- Cthulhu_ 5y agoIsn't that part of where the "high APM" thing comes from - players having to micromanage their army movement?
- dragontamer 5y agoI dunno if that's an explicit discouragement though. Pathing in the 90s was all sorts of bad for all games except Civilization (because there's no collision detection in Civ, so... all units just walk on top of each other).
- Andrew_nenakhov 5y agoIn Civ 1/2 you definitely DID NOT kill all stack of units if you killed one. I played them both a lot (and actually prefer them to newer installments), so I know for sure.
- glenstein 5y agoAlso not how I remembered it, although my experience is from Civ 3 and Alpha Centauri. There are a bunch of people who don't have this experience so I wonder what's going on.
- dragontamer 5y agoYou're talking to a lot of players who likely only played on Chieftan AI levels: where the enemy AI would rarely meet you in the field and often times only retreat to cities. Even then, they would rarely try to stack-kill the player. It was always possible, but since the easy-AI never attacked in such a manner, the mechanic was basically irrelevant on easy/Chieftan mode. On more difficult AI levels (Prince or Emperor), the AI would meet you in the field, and you'd have to worry about stack kills. And also worry about cheating AIs who just had more resources than you...
- Andrew_nenakhov 5y agoI always played civ 1&2 only on hardest levels. Now, thinking of this further, i think I might misremember this because I've never let my stacks be attacked in the field. Best tactics is to drive tanks via railroads up to the city (sometimes building them in the fly using a ton of settlers in one move) and attack it with 20+ tanks and then move in 10 mech infantry for defence, and I used fortresses extensively.
- Delk 5y agoI'm pretty sure that in Civ 2 all units in a defending tile did actually get killed if the defending unit was defeated. Getting killed when attacking didn't have this effect, of course, nor did it happen if your defending stack was in a fort or in a city.
- OneTimePetes 5y agoTotal Annhilation replaced the deathball with automated death-streams, while the players focused on commando actions to sabotage the economic engines keeping the streams of death going.