Everything is Crab Spines Reflect Build Guide

Core evolutions

• Spines
• Plated
• Shell
• Revenge
• Regenerative Tissue
• Robust
• Impervious

Genetics

• Patient
• Stubborn
• Chosen
• Highborn

Route phases

1. Do not invite contact until Shell, Plated, Regenerative Tissue, or another defensive layer exists.
2. Spines and Revenge convert mistakes into value, but the run still needs movement.
3. Use this route for reflect-style goals and contact-heavy challenge runs where durability matters.
4. Keep it separate from no-hit routes: inviting contact breaks Can't Touch This even when the damage becomes useful.
5. If reflect damage is too slow, add one real attack instead of taking more punishment.

Stat priority

• Plating
• Resistance
• Regeneration
• Max HP

Related achievements

• Brute
• Can't touch this
• Extinction 5

Decide whether receiving contact damage fits the goal

Spines is a contact-retaliation option: some contact damage is returned to enemies. Its practical tradeoff is the damage returned versus the health spent receiving hits. Do not read a retaliation effect as an instruction to stand still. Before relying on it, identify whether the next encounter leaves room to recover and move away. If that exchange is steadily losing health, taking more hits just to activate the effect repeats the problem rather than demonstrating that the build is working. Source: Spines contact-retaliation reference

Revenge is a different effect. Its description temporarily raises Physical and Ability after damage; that does not make it the same counter as damage returned by Spines. If you take damage, consider whether there is a safe opportunity to use the temporary increase through an attack. Repeatedly renewing the trigger without time to recover can leave no useful attack window. Keep retaliation, a temporary attack-stat bonus and ordinary attacks separate when judging which choice is contributing. Source: Revenge’s temporary damage bonus Source: Spines contact-retaliation reference

Highborn changes nearby effects and attack scaling separately

OddDreamsDigital’s Highborn explanation distinguishes Physical and Ability penalties from the general Damage multiplier: general Damage is not reduced by that effect. The explanation also identifies Spines and Toe Beans as examples that can use the larger nearby area. This is a reason to compare the main hit’s scaling and the nearby effect separately. An unchanged general multiplier does not cancel a reduction to the Physical or Ability stat that a chosen attack uses. Source: OddDreamsDigital on Highborn damage types

Highborn’s returned-damage unlock asks for over 2000 damage returned in one run. That question is separate from whether a Highborn setup improves a particular attack. Ordinary total damage does not prove how much was returned. Check the Codex progress for the stated goal after the attempt rather than using a large end-of-run total as a substitute. A stronger personal attack may keep the run alive while still contributing to a different damage measurement. Source: OddDreamsDigital on Highborn damage types

Be especially careful when using this contact-focused route for damage-restricted achievements. Can’t touch this forbids taking damage; Dove forbids dealing damage; Zen forbids both. Choosing to take a hit for retaliation conflicts with the first requirement, and damage returned to an enemy matters to the no-damage-dealt goals. Healing afterwards does not erase a hit that already occurred. Decide on an ordinary survival or damage goal before deliberately accepting contact, rather than discovering the conflict after a long run. Source: Steam achievement conditions Source: Spines contact-retaliation reference

FAQ

Is the returned-damage total the same as ordinary damage dealt?

No. The Highborn objective names returned damage, while the Brute series names total damage. An ordinary attack can enlarge a damage total without proving the returned-damage requirement. Keep the specific objective visible and check its relevant progress rather than assuming every number on the result screen describes the same event. Source: OddDreamsDigital on Highborn damage types Source: Steam achievement conditions

Does Highborn guarantee that this route is stronger?

The developer explains its tradeoffs, not a universal winning loadout. Compare how much of the planned attack depends on Physical or Ability with what actually benefits from the expanded nearby area. Spines and Toe Beans are named examples, but the explanation supplies no success rate or guarantee that every nearby-effect setup survives the next boss. Source: OddDreamsDigital on Highborn damage types

What should change when retaliation is too slow?

First reduce the health lost waiting for another contact trigger. Keep movement and recovery workable, and compare an attack you can use during a safe opening if the goal permits dealing damage. Adding a controlled way to finish the encounter answers a different problem from simply inviting more hits for the same slow return. Source: Spines contact-retaliation reference Source: Revenge’s temporary damage bonus

Common mistakes

1. Standing still because the build has reflect.
2. Missing food sustain.
3. Stacking armor without a way to end fights.