FIELD NOTES
Anatomy of a boss: designing the Rift Weaver
A spider-loom with 120,000 health that cannot be deleted by one lucky hit, and the design reasoning behind each phase.
PLAY FREE IN YOUR BROWSERThe end of Rift I used to be a crowned host with 40,000 health. It was a perfectly respectable boss for a game that grew its enemies with a formula, but it had one flaw that every boss built from the same machinery has: at some point, a strong enough build simply outdamages it. A boss that a strong enough build removes in a few seconds is not an ending, it is a speed bump. So in build 20261050 the end of Rift I became the Rift Weaver. This article walks through how it is built and why each piece exists, because a boss is a good example of a general problem: how do you make a fight that is hard in an interesting way, instead of one that is merely long?
The design brief
The brief had four goals.
- It must not be deletable. No single build, however strong, should skip the fight.
- It must punish standing still, but fairly. Every dangerous attack needs a warning the player can read and react to.
- It must have a rhythm. A boss that does the same thing for ten minutes is a chore. The fight should change shape as it goes.
- It must work for every rig. Gun rigs and the three melee rigs need to be able to win it, from different distances.
The theme came from the player. You play a robotic spider, so the end boss on the first map is a much larger violet spider-loom: a thing that weaves. That choice then drove the mechanics, because weaving gives you the vocabulary for every attack: webs, threads, cocoons, a brood.
Rule one: a cap on every hit
The Weaver has 120,000 health, three times the old end host, and it takes at most 0.8% of its health from a single gun hit and 1.4% from a single melee hit. Those two numbers do most of the work of the design. Without them, a very large single hit, from a Hollow Cannon shell or a boosted Lance beam, could remove the boss in a few shots regardless of what it was doing. With them, the arithmetic is fixed. At 0.8% per hit, it takes at least 125 gun hits to kill it, and at 1.4% per hit at least 72 melee hits, no matter how much damage your weapon claims to deal.
The interesting consequence is for builds. Against the Weaver, big hits stop mattering and the number of hits starts to. Under the cap, the most damage per second a gun can deal is its fire rate times 0.8% of 120,000, which is 960 damage per second for every shot you fire per second. A rapid-fire weapon, a pellet-heavy one or one with chains and extra projectiles does better than one whose strength is a single enormous shell.
The melee cap is higher, 1.4%, for a reason covered in the melee design article: a melee weapon hits less often, and holding it to the gun cap would make it unviable. The two numbers together mean a melee player and a gun player have a roughly comparable route to the end, with the melee player needing fewer, riskier hits.
Rule two: three phases built on a cocoon
At 75%, 50% and 25% of its health, the Weaver wraps itself in silk. This is the structural idea of the fight. For the duration of a cocoon it takes only 20% of normal damage, and it calls a brood of spinnerlings: six at the first cocoon, eight at the second, ten at the third. Silk threads visibly link the brood to the boss so you can tell which hosts are the ones that matter. Kill every one of them, or survive for 12 seconds, and the cocoon tears open with a ring of web bolts.
This does several jobs at once. It breaks the fight into stages, so there is a clear sense of progress at each threshold. It changes what you are doing: for the length of a cocoon you stop attacking the boss and start clearing adds, which is a different skill. It gives melee and area builds something to do, and it creates a decision, since the 12 second timer means ignoring the brood does not stall the fight forever but does let the cocoon tear open on the boss's schedule rather than yours. The brood size grows by two each time so that every phase asks slightly more than the last. And the bolt ring when the cocoon breaks makes sure the moment of victory over the adds is also a moment you have to move.
Rule three: every danger has a telegraph
When the Weaver is not cocooned, it has three attacks, and each one tells you what it is about to do.
- Web nova. A slow rotating ring of web bolts, fired every 3 to 4.6 seconds. The bolts are slow and the ring has gaps. The answer is to move through a gap or dash.
- Thread lash. Two pink lines appear, showing an aimed fan of fast bolts, half a second before it fires. The answer is to be somewhere other than on the lines.
- Silk slam. A dashed pink ring around the Weaver fills for a full second and then slams everything inside it. The ring is 175 pixels in radius. The answer is to be outside it.
The three attacks are deliberately different in what they ask. The nova asks for continuous movement. The lash asks for a short precise sidestep. The slam asks for distance, which is the one attack that punishes a melee player for standing next to the boss, and so creates a rhythm of closing in to attack and backing out when the ring begins to fill. A player who can read all three is rarely hit. A player who ignores them is hit constantly, and, since the warning is always visible, the game is never doing anything unfair.
Below 15% health the fight enters an enrage state: everything runs 1.5 times faster and the Weaver itself moves faster. The telegraphs are not removed, only compressed, so the last stretch tests whether you have learned the fight. In Endless mode a Weaver returns at waves 110, 120 and so on, with 700 more health for each wave past 100, and it always drops a legendary item with a 25% chance of a Mythical weapon.
The bug that made the armour useless
Here is the mistake we are happiest to have caught. The cocoon takes 20% damage, and the first version of that rule did exactly what it said, but at the wrong moment. The cap and the cocoon reduction are two separate adjustments to the same hit, so the order matters. We applied the reduction first and the cap second. Take a big hit of 10,000 damage against the cap of 960 (0.8% of 120,000). The reduction cut it to 2,000, which is still more than the cap, so the cap then clipped it back to 960: the same damage as outside a cocoon. Any build whose hits were large enough, which is exactly the builds the cocoon was meant to slow down, took no benefit from the armour at all. Only small hits were reduced.
The fix was to apply the reduction after the cap, so a capped hit is cut to 20% of itself, which is 192 damage or 0.16% of the boss's health, whatever the original hit was. We only found it because the test for the cocoon did not just check that the cocoon state appeared on screen. It measured the damage the boss actually took while wrapped in silk and compared it with what it took outside. That is the same lesson as in the testing article: a feature that is visible is not a feature that works.
Fighting it
With the structure in mind, the practical advice is straightforward.
- Spend the first phase learning the three telegraphs. Do not chase damage yet; no hit counts for more than 0.8%.
- At each cocoon, switch to adds. Area weapons, chains, blast and a melee ability shine here. Count the brood, not the boss.
- Keep out of the slam ring, always. It is the only attack you can fully avoid by distance, and it is the one that does the most.
- If you are a gun rig, favour fire rate and pellets over single huge shots. If you are a melee rig, wait for the ring to start filling, hit, and leave.
- Save your active ability for a cocoon opening or for the enrage. Both are the moments when a burst of damage, healing or invulnerability is worth the most.
One honest caveat. The Weaver has been run through automated tests, including forced-spawn runs with random input on several rigs, but it has not yet been balanced against a wide range of real builds. Its health, caps and attack timings are all single constants in the code, so they are easy to tune. If you beat it in under a minute or cannot get past the first cocoon, tell us your rig and your build, and we will adjust the numbers rather than the design.