Abiotic Factor shield damage class and blocking guide
Match Light, Medium, and Heavy shields to incoming Abiotic Factor damage classes, and understand partial blocks, status risks, and Super attacks.
Original combat comparison
Compare incoming attack class with shield coverage before relying on a full block. Source basis: the references listed on this page, checked for game version 1.4. This original planning diagram is not to scale and is not copied game or wiki media.
Compare class, not appearance
The official Damage Types reference sorts attack strength into Light, Medium, Heavy, and Super classes. A shield can fully block attacks at its own class or below. An attack above the shield's class is not fully blocked, and the source says the player can still take reduced damage and receive status ailments carried by that attack. Super-class attacks cannot be blocked by any shield.
This gives a simple hierarchy:
| Shield class | Fully covers | Does not fully cover |
|---|---|---|
| Light | Light | Medium, Heavy, Super |
| Medium | Light and Medium | Heavy, Super |
| Heavy | Light, Medium, and Heavy | Super |
Do not estimate class from shield size, weight, color, or crafting tier. Use the current item or Damage Types entry.
Use the reviewed shield table
The current Damage Types table places Plastic Shield, Heater Shield, Hexwood Shield, Lodestone Shield, and Plasmatic Shield in Light. Charge Shield, Kite Shield, Hardlight Shield, and Clamp Shield are Medium. Riot Shield is Heavy.
| Class | Shields in the reviewed source | Route implication |
|---|---|---|
| Light | Plastic, Heater, Hexwood, Lodestone, Plasmatic | Confirm expected attacks are Light before relying on a full block |
| Medium | Charge, Kite, Hardlight, Clamp | Covers Light and Medium attacks |
| Heavy | Riot | Covers through Heavy, but not Super |
This table is a blocking reference, not a universal equipment ranking. The Off-Hand Armaments page lists other differences such as durability, weight, and item-specific behavior. A higher blocking class may impose a different carry or progression cost, while a lower-class shield can have another property that serves the route.
Diagnose damage through a raised shield
When a block does not behave as expected, check the chain in order:
- Confirm the shield was equipped and actively blocking when the attack landed.
- Identify the exact enemy attack, not only the enemy name.
- Find the attack's documented class.
- Compare that class with the shield table.
- Check whether the attack carries a status effect that can remain relevant during a partial block.
- Check shield condition and any item-specific resource requirement on the current armament page.
If the incoming attack is stronger than the shield, some damage is compatible with the documented rule. Do not call it a bug before checking class. If the attack is Super, plan avoidance, interruption, distance, or cover rather than a shield-only response.
Build a pre-route blocking matrix
Use one row for each dangerous attack expected on the objective. Leave the class unknown when a current source does not identify it.
| Enemy and attack | Source class | Current shield | Full class coverage? | Alternative response |
|---|---|---|---|---|
| Exact name required | Light, Medium, Heavy, Super, or unknown | Exact item | Compare hierarchy | Dodge, range, cover, interrupt, retreat |
The alternative response is mandatory for unknown and Super attacks. It is also useful when a shield technically covers the class but repeated blocking would consume too much durability or prevent another necessary action.
Use the damage relationship reference for outgoing weapon choice. Do not put enemy weakness in the shield coverage column.
Account for off-hand control tradeoffs
The Off-Hand Armaments page says blocking takes priority over other Alt-Fire actions on held weapons, including examples such as blunt power attacks and ranged zoom. A shield can be equipped, but may need to be holstered to use those actions. This is a loadout interaction, not just a defensive statistic.
Before the route, test the intended weapon and shield together in a safe area:
- confirm the block input raises the shield;
- confirm whether the weapon's alternate action remains available;
- practice the holster or swap needed to use that action;
- verify the inventory and weight cost of carrying the fallback;
- decide which enemy attack triggers a retreat instead of another block.
The test should confirm controls and equipment state. It should not be used to invent a hidden damage reduction value.
Treat status effects as a separate risk
The official off-hand guidance warns that stronger attacks may still apply status ailments while partially blocked. Therefore, “I survived the hit” and “the shield fully covered the attack” are not equivalent observations. Record damage and status outcome separately.
| Observation | Likely next check |
|---|---|
| Damage taken, no status | Compare attack and shield classes |
| Reduced damage plus status | Stronger attack or status-bearing hit; verify source |
| No block against Super | Expected class limitation; switch response |
| Alt-Fire unavailable | Blocking priority and holster state |
| Result changes between attacks | Confirm exact attack, angle, timing, and equipment state |
Bring a response for the status hazard when the route source confirms one. Shield coverage alone should not replace environmental protection or recovery items.
Choose a shield for the objective
Start with the strongest confirmed incoming attack that you plan to block. Select a shield whose class covers it, then compare item-specific weight, durability, progression access, and special behavior. If no available shield covers the attack, change the combat plan rather than describing a partial block as full protection.
A lower-class shield remains a valid choice when all planned blocks are within its class and its other properties fit the route. The word “Light” describes blocking class in this table; it does not automatically mean poor equipment.
Recover from a failed block plan
If the player takes unexpected damage, move to safety and record the exact enemy, attack animation, shield, and status. Check current Damage Types and Off-Hand Armaments entries. If the attack class is missing, mark the matchup unverified and use an avoidance-first plan on the next attempt.
Do not change shield, armor, weapon, and position at the same time when testing the correction. A single controlled change makes the next result interpretable. Avoid publishing exact absorbed damage from one hit because armor, body part, and attack variation may affect the observation.
Completion condition
A shield plan is ready when every intended block has a documented incoming class, the selected shield covers that class, a non-block response exists for Super or unknown attacks, status risk is handled separately, and the player has tested the shield-and-weapon controls safely.
Recheck the linked tables after a patch that adds shields or reclassifies attacks. The hierarchy is easy to audit: exact attack, exact class, exact shield, then a fallback for anything the class cannot fully stop.
Sources & References
Shield classes, blocking hierarchy, stronger-attack behavior, Super-class limits, and off-hand interaction are checked against the official Damage Types and Off-Hand Armaments pages plus the Weapons and Ammo category.
Editorial contribution
Turns the official shield class table into a pre-route blocking matrix, with explicit handling for stronger and Super-class attacks and for actions displaced by block controls.
- abioticfactor.wiki.gg: Damage Types →
- abioticfactor.wiki.gg: Off Hand Armaments →
- abioticfactor.wiki.gg: Weapon →
Sources support factual claims. Route choices, comparisons, and recovery guidance are editorial synthesis and may change with game updates.
Author
The editorial desk maintains source-backed Abiotic Factor route notes, item checks, and practical decision guides.
About our editorial team →