Field guide · 11 minute read
Fader Preparation Guide: Ashlands Arena and Recovery Plan
Fader is the current public-release progression endpoint. The encounter combines heavy pressure with the Ashlands environment, so the boss kit must be backed by a stable beachhead, repeatable food, and a recovery route that works after the main equipment is gone.
Make the boss kit replaceable
The strongest available weapon is not ready if its food, ammunition, Eitr supply, or repair station cannot support a second attempt. List every consumable used in a practice run and stock at least two complete sets. Keep one set at the beachhead and one outside the Ashlands in case the local portal network fails.
Upgrade the primary damage path and the defensive item that supports it. Avoid splitting rare materials across several experimental weapons immediately before the fight. Test the chosen combination against fortress and open-world enemies so stamina cost, reach, and crowd control are understood under pressure.
Prepare the approach and external portal
Clear spawners and roaming groups along the approach before carrying every summon or combat resource. Mark a route that avoids narrow ruins and persistent fire. The portal should be protected outside the arena’s normal movement but close enough that a controlled reset does not become another expedition.
Build the recovery chest around the character that will exist after death, not the one wearing the best gear. Include fire-safe travel protection, food, a usable weapon, armor, and any visibility or movement item required by the route. Confirm the portal name and remote connection before starting.
Read the ground as part of the attack
Area attacks can turn a familiar section into a temporary hazard. Move before the safe route disappears, then re-establish the loop instead of attacking from a burning or blocked position. Keep enough stamina to cross one dangerous zone even after a short damage window.
Camera position and terrain matter during large attacks. Fight where visual cues remain readable and avoid backing into ruins or elevation changes that hide the next path. If additional enemies join, control them or rotate away before returning to boss damage.
Sustain damage without exhausting the run
Melee plans should use short openings and leave with stamina. Ranged plans must budget ammunition and maintain clear shots without standing in hazards. Magic plans need enough Eitr food and regeneration to preserve a defensive option after the attack cycle. Every style fails when it spends the resource needed for escape.
Use healing after creating space, not as a substitute for leaving a dangerous position. Watch food, resistance, Rested, durability, and ammunition together. A reset while the portal route is open preserves progress; a final greedy sequence can place the corpse where the recovery kit cannot function.
Record the endpoint and prepare for change
After victory, record the loadout and game version that produced it. Fader is the current endpoint, but the official 1.0 release will add Deep North progression. Keep the Ashlands production base intact and avoid treating preview information as a finalized preparation list.
When a new public release arrives, recheck food, equipment, boss rewards, and progression order before reusing this plan. The site’s patch workflow should update current records only after public release and source review, preserving a clear boundary between preparation and speculation.
Before you leave
Expedition checklist
- Two complete food and consumable sets exist in separate locations.
- The primary weapon and defensive path are tested against Ashlands enemies.
- Approach spawners and roaming threats are cleared before the attempt.
- A protected arena portal and separate external recovery portal are active.
- The recovery kit can traverse the route without the lost main equipment.
- Food, fire protection, Rested, durability, and ammunition are checked together.
Sources and scope
This independent guide is reviewed for the public game version shown above. Strategy recommendations are practical defaults, not official rules. Preview-build details stay excluded until they reach the public release and pass review. Report a problem through the corrections page.