A Fellwood run is ready to reset when the next permanent purchase will change the next run, not when a timer, level, or damage number tells you to stop. The game layers a temporary building economy over permanent Prestige progress, so a stalled run can come from three different places: too few trees to hit, too little collection capacity to sell what falls, or a damage setup whose level-up choices no longer reinforce one another.
This guide is bounded to the PC launch state checked on August 15, 2026. Steam identifies AppID 4632540 as Fellwood by Allerton Apps, released August 14, and the latest official note located for this review is Hotfix 1.0.1. The supplied 94-minute gameplay file was recorded in June and visibly reaches a "not available in the demo" lock, so it is used only to verify the core interface and reset loop. Its building ceiling, costs, and pacing are not treated as full-release values. The live store advertises 17 buildings, more than 80 permanent Prestige upgrades, and more than 100 level-up options.
Decide which loop has stopped paying you
Do not diagnose every slowdown as a damage problem. Fellwood has three connected loops, and an upgrade in the wrong loop can make the screen busier without making the run advance.
- Tree and projectile loop: Headquarters supplies trees, while attack buildings send axes, arrows, bolts, spells, blades, and later effects across the valley. This loop determines how quickly wood leaves the standing trees.
- Log and gold loop: fallen logs still need to become income. Collectors and Sawmill upgrades govern how many pieces can be moved, how quickly they are gathered, and how valuable collection becomes.
- Account loop: levels and ordinary building purchases power the current run. Prestige removes that temporary setup and opens permanent purchases that change future openings.
Use the battlefield as a diagnostic display. If the target side stays nearly clear and attacks spend most of their time waiting for new material, inspect tree supply before buying another damage percentage. If logs form a persistent pile while the gold total barely responds, inspect collectors, carry capacity, travel time, and Sawmill value. If trees keep falling and logs keep selling but every new purchase takes much longer than the previous one, compare the next reachable permanent upgrade with the cost of continuing this run.
The DPM display is useful only after you ask what it omits. It describes damage output, not whether a collector can reach the pile or whether the next tree exists. A higher DPM line cannot repair an economy whose sale step is the real bottleneck.
Build an economy floor before choosing a damage identity
The opening objective is not to own every visible building. It is to create one complete circuit: a tree exists, a projectile can bring wood down, a collector can move the logs, and the sale funds the next improvement. Check Headquarters, one attack building, and the Sawmill as a group before expanding sideways.
- At Headquarters, buy enough tree supply and population to prevent either side of the circuit from sitting idle. An extra tree is wasted when attacks cannot process the existing targets; another worker is wasted when there is nothing ready to collect.
- At the Sawmill, separate collector count from collector quality. More collectors increase simultaneous coverage, movement speed reduces travel, gather duration shortens the pickup, carry capacity reduces return trips, and log-value upgrades improve the result of each completed delivery.
- At an attack building, first secure reliable output. Count and attack speed usually change how often projectiles appear; damage and critical upgrades change what each hit does; pierce, ricochet, explosions, chain lightning, shatter, and embedding become valuable only when the matching projectile can actually trigger them.
A July developer balance note changed damage from multiplicative to additive because a single-building tunnel had become overwhelmingly efficient in the demo build. No later official note located for this review announces a reversal, but the launch client is still the authority. The practical consequence is to avoid importing an old "buy only one tower" script. Establish enough mixed coverage to unlock useful systems, then concentrate purchases only after the live tooltip and the DPM breakdown show which branch is producing a return.
A good expansion test is simple: buy one meaningful upgrade, close the panel, and watch a full production cycle. If tree downtime falls, the attack side improved. If the pile clears faster, collection improved. If neither visible state changes, stop repeating that purchase merely because its number is green.
Make level-up choices form a chain
Level-up cards are temporary run power. Their rarity matters, but a rare card for an inactive branch can be weaker than a common card that closes the missing link in the build you already own. Read each option as one of four jobs:
- Create attempts: add projectile count, worker count, attack speed, or another repeatable source of hits.
- Make attempts connect: add pierce, ricochet, chain chance, explosion chance, shatter setup, or another delivery mechanic.
- Increase the result: add damage, critical chance, critical damage, log luck, log value, or scaling that already has enough attempts behind it.
- Repair the economy: improve collection or another shared resource when damage is already producing more logs than the settlement can convert.
For example, ricochet scaling does nothing until an axe can ricochet, while more ricochet chance may still disappoint if too few axes are thrown. Chain-lightning damage needs lightning attempts and a chain trigger. A large critical-damage card needs a believable critical chance. Before selecting, name the prerequisite already present in the build; if you cannot, the card is a speculative detour.
Save rerolls and banishes for a real miss: three choices that do not create, connect, increase, or repair the current plan. Do not spend them only to chase a legendary border. The current achievement list includes selecting many legendary options, but that is a long-account counter, not a reason to weaken the run in front of you.
Launch-day developer replies said the level-up panel opened automatically and had no disable toggle at that time. Hotfix 1.0.1 then increased the delay before a choice can register to reduce accidental selections. When the level bar is about to fill, stop clicking the same screen area until the card panel settles. If a later patch adds a setting for this behavior, use the current setting rather than this launch-day workaround.
Prestige against a named purchase, not a vague slowdown
Open the trophy icon and read the Prestige panel before committing. The verified interface describes the reset as removing current buildings and level-up upgrades, then allowing permanent purchases. It also shows current and spent Prestige points separately and assigns costs by upgrade tier. Exact nodes and costs can change, so use the tree visible in your client.
Use this reset test:
- Choose the permanent node you want next and state what it will change: more starting resources, stronger early collection, better level-up control, access to a new tier, or another specific advantage.
- Check whether prestiging now can buy that node. Count points, prerequisites, and tier locks; do not assume that earning a point automatically opens the desired branch.
- Estimate the next run’s first bottleneck. Starting gold is useful only if trees, workers, and a projectile source can still form a complete circuit. More choices are useful only if the build can reach enough levels to use them.
- If the reset buys a concrete improvement and the current run is climbing slowly, prestige. If it buys nothing relevant and the run is close to a new building, mechanic, or tracked milestone, keep pushing until one of those states changes.
Permanent economy is usually the cleanest early target because it shortens every later opening. Starting resources remove dead time; broader level-up control reduces failed card sets; durable luck or value upgrades improve multiple branches. Damage-specific permanent upgrades become more attractive after you know which mechanic the current launch balance lets you sustain.
Do not stay trapped because the first gold purchase was wrong. In a launch-day support reply, the developer confirmed that you can open the trophy dialog and hold the Prestige button to restart even with zero points. That is the recovery path for an opening that cannot complete its production circuit; abandoning the save or idling a broken setup is unnecessary.
Respond to each random event differently
The last detailed official event note located before launch defined three events. Treat the live event text as final if a patch changes these rules, but the distinction between passive opportunity and manual task is the important part.
- Timber Rush
- Logs fall for a short period, with their tier based on the logs already in the pile in the documented build. The damage side does not need to create this wave. Watch collection instead: if the pile expands faster than it clears, Sawmill capacity is the limiting system.
- Fellstorm
- Lightning periodically strikes the pile and upgrades logs near the blast. The official note required at least 50 active logs for the event in that build. A perfectly empty field is therefore not always ideal; the event needs material present, but an uncontrolled pile can still overwhelm collection.
- Lucky Breeze
- Four clovers cross the screen and must be shot manually. Worker projectiles do not count. Each successful clover increases Luck for the rest of that run, ending at Prestige. This is the event that should interrupt idling: open the manual attack, lead the moving targets, and confirm the Luck change before returning to building panels.
The event lesson is not "always keep a giant pile." It is to know which loop the event rewards. Timber Rush tests collection, Fellstorm converts existing pile state, and Lucky Breeze tests player input. Buying damage during a collection event or remaining idle during Lucky Breeze wastes the specific opportunity on screen.
Use mechanic achievements as diagnostics
The public launch page lists 59 achievements. Many describe counters rather than hidden actions: pierces, ricochets, explosions, chain lightning, shatters, critical hits, sawblade embeds, druid effects, active-ability uses, total levels, workers, logs, gold, and damage. These counters are useful because they tell you whether a build is actually triggering the mechanic you think you purchased.
| Mechanic | Visible setup to verify | Failure signal |
|---|---|---|
| Pierce | A projectile tooltip explicitly shows pierce chance or count, with multiple trees available in its path. | Damage rises but the pierce counter does not; the projectiles may lack the trigger or have no second target. |
| Ricochet | Axe or blade upgrades show ricochet chance and a permitted bounce count. | Single targets die before a bounce can occur, or chance exists without enough projectile attempts. |
| Explosion, chain, or shatter | The matching fire, electro, or ice line explicitly exposes its trigger and effect. | Generic elemental damage was purchased, but the named trigger never appears. |
| Sawblade embed | The Sawblade building is unlocked and its tooltip describes embedding for repeated damage. | Blades ricochet or kill targets, but do not remain embedded long enough to advance the counter. |
| Critical hits | Both critical chance and enough attacks are present. | Large critical damage is visible, but almost no hits roll a critical result. |
Work on one missing trigger at a time. First make the counter move at all, then increase attempts, and only then scale the effect. This prevents a common waste: spending heavily on the size of an explosion, shatter, or critical hit that the build rarely produces.
The extreme damage achievements need a later-state plan. In a release-day reply about the one-quadrillion target, the developer called it a stretch and pointed to permanent upgrades, coherent level-up selections, and the correct end effect. That does not establish one universal build or a fixed number of idle hours. If growth has flattened, use the DPM breakdown and the relevant mechanic counter to decide whether the run lacks attempts, trigger chance, effect scaling, or another Prestige cycle.
Unlock active abilities inside buildings, then use the top-left menu
Active abilities are not ordinary level-up cards. The developer’s launch-day explanation says they must first be purchased inside certain buildings. Once unlocked, they appear in the small dropdown at the top left. Activating one creates a positive effect for a limited duration, followed by a cooldown.
If the menu is empty, do not search the keyboard for a hidden universal skill. Open the building panels, scroll through the locked requirements, and look for an ability purchase. If an achievement tracks active-ability uses, confirm three states in order: the building owns the unlock, the icon appears in the dropdown, and the cooldown starts after activation. Buying a passive percentage in the same building will not satisfy that chain.
On the launch interface, building panels also shared one dynamic dialog and could preserve the previous panel’s scroll position. If a newly opened building appears to be missing its first upgrades, scroll back to the top before concluding that the content is locked. The developer acknowledged this as a UI issue, so a later patch may remove the workaround.
Use the Ancient Offering as the soft ending checkpoint
Fellwood does have an optional goal beyond larger numbers. The developer places the soft ending in the Log Temple: unlock that building and complete the Ancient Offering. The public achievement description then confirms that finishing the offering awards Fellwood’s hidden crown. Play can continue after the soft ending.
The reviewed sources do not reveal the offering recipe, every prerequisite, or a reliable building-by-building route to the temple. Do not copy a demo lock or infer an ingredient list from the crown achievement. If the Log Temple is still locked, inspect its current prerequisite text and work backward through that exact chain. If it is open, follow the offering panel in the current client and verify each submitted requirement there.
This boundary matters because the supplied video stops inside demo progression and never verifies the launch offering. It can explain why a reset preserves the account loop, but it cannot prove how the full release ends. Until a readable current route exposes those steps, the honest actionable checkpoint is: reach the Log Temple, read its live requirements, complete the Ancient Offering, confirm the crown, and then decide whether to continue the endless scaling game.
Recover a run from the signal it is giving you
- You spent the opening gold and cannot get the circuit moving.
- Open the trophy icon and hold Prestige. The developer confirms that zero points are enough to restart.
- Logs cover the ground but income barely changes.
- Stop buying attack damage. Compare collector count, movement, gather duration, carry capacity, and Sawmill value, then watch one complete pickup and sale.
- DPM rises while a mechanic counter stays flat.
- Open the matching building. Confirm that the named trigger is unlocked, that it has enough attempts, and that the battlefield supplies a valid second target or effect condition.
- An active-ability achievement never advances.
- Find the ability inside a building, purchase it, open the top-left dropdown, activate it, and watch for the cooldown. A passive building upgrade is not an activation.
- Prestige feels available but pointless.
- Name the permanent node the reset will buy. If there is no relevant node, continue toward a prerequisite or milestone; if there is one, reset and test whether it shortens the next opening.
- The soft ending still has no route marker.
- Look for the Log Temple and its live unlock text. The verified endpoint is the Ancient Offering and crown, but the reviewed evidence does not support guessing the missing requirements.
Before holding Prestige, point to the permanent node the reset will buy and the bottleneck it will remove. If you can name both, start the next run. If you cannot, stay long enough to unlock a prerequisite, make a dormant mechanic counter move, or read the Log Temple requirement that gives the run a real target.