Super Fantasy Kingdom changed too much in Patch #15 for its launch-week build orders to remain a dependable first-win script. Achievements no longer recruit units, the Trapper now opens the roster, spells and kingdom traits alter team construction, taxes arrive differently, and Patch #16 restored resource-paid daytime upgrades alongside coin-paid night promotions. A guide that still says “complete this achievement to unlock that unit” is describing an older game.
This guide targets the first major Human Kingdom victory against the Goblin King, not the final Early Access ending. It was checked on August 10, 2026. The latest publicly documented gameplay boundary in the official Steam news feed is Patch #16, build 0.7.072, released April 25, followed by the May developer roundup. Early Access can move costs, balance, and tutorial timing again, so the current unit sheet, Calendar, Fate choice, and building tooltip outrank any fixed number below.
The first victory is no longer an achievement-unlock route
Make one correction before starting: separate unlocking a unit from completing the achievement that shares its name. After Patch #15, catching the monster through the Trapper unlocks that unit. The old achievement condition remains useful as a permanent-stat objective, but it is no longer the recruitment gate. This distinction prevents the most expensive early mistake: bending the whole economy around four wells, a no-house run, or another challenge while expecting a defender to appear.
| Old guide instruction | Current action | Check before committing |
|---|---|---|
| Finish a named achievement to obtain its unit | Place the Trapper’s trap in the path of that monster and weaken it before contact. | The Fate screen marks whether the monster has already been caught. |
| Follow one exact tutorial build by day number | Follow the live tutorial gate, then close the active wood, worker, food, stone, or upgrade bottleneck. | The requested building and its displayed cost match the current client. |
| Choose a fixed “required” Cyclops/Crossbowman lineup | Recreate the jobs: something durable near the contact point, control or knockback, and damage that continues while the boss holds range. | Each recruit solves a missing job rather than duplicating the same fragile role. |
| Spend coins as soon as a shop appears | Reserve a night-promotion budget; use resources for a daytime upgrade when that avoids delaying a key building. | You know which unit receives the next meaningful rank. |
Patch #15 also prevents incompatible old runs from resuming after a large update. If a guide and your save disagree on the first recruit, church, portal, road, or tax behavior, do not try to force the old sequence. Start a compatible run and rebuild from the state checks below.
A morning succeeds when one bottleneck closes
The map offers more attractive tasks than the first economy can finish. Treat every morning as a short production contract: name the one state that must exist before night, assign only the jobs needed for it, and stop expanding when it is complete. “Gather more wood” is too vague. “Deliver enough wood to add a worker before the wave” is testable.
Use this priority order until the first boss is visible on the Calendar:
- Obey the live tutorial lock. Patch #16 changed the order of the first-unit and castle-repair lessons. If the interface is waiting for one of them, finish it before applying an older day plan.
- Create carrying capacity, not merely gathering jobs. A House or current worker source matters only when the added labor reduces the next bottleneck. Do not queue several buildings that all compete for the same tiny workforce.
- Secure the resource chain required by one defender upgrade. Wood and stone open much of the Human route, but the actual requirement shown on the chosen unit or building is the decision.
- Protect tonight’s meals. If recruitment makes the roster larger than the food supply, the new unit can make tomorrow’s army weaker rather than stronger.
- Spend surplus on permanent access. Roads and other persistent map progress are valuable, but not when their stone removes the upgrade that keeps the hero alive tonight.
Keep one carrier available before assuming production is complete
A resource beside its building is not necessarily usable at the Castle. The worker display distinguishes assigned jobs from the workers actually available; persistent over-assignment makes completion order hard to predict. If the counter shows that every worker is busy and the required wood or stone is sitting in transit, remove a low-priority assignment. An idle worker can deliver stock, turning a visually full production site into spendable inventory.
This is the failure signal to watch: the resource node has been processed, the top inventory has not increased, and the intended construction remains unaffordable. Adding another gathering assignment does not solve that state. Free a carrier, let the delivery finish, then restore the job only if daylight remains.
Place production for usable space and travel, not symmetry
Lumber and food buildings need access to the nodes they create or harvest. A neat edge plot with only a couple of usable adjacent cells can choke the building for the rest of the run. Before placing one, inspect the surrounding node spaces and future road lanes. For a first boss attempt, a short carrier path and enough open production cells are worth more than a decorative district.
Do not automate every special job merely because its toggle is available. Special workers consume coins when they perform tasks. If the star switches off or coin income disappears, decide whether the automated tree, road, or excavation is more valuable than the promotion you intend to buy at night. A silent automation bill is often the reason a seemingly healthy city reaches the Tavern without an upgrade budget.
Food is the combat stat that arrives one night late
Units eat after the defense. That makes food easy to postpone: the current wave looks safe, so every worker is moved to construction. The penalty appears the next day, when hungry units attack more slowly and the next wave is already stronger. Count meals against the roster you will actually field, not against the roster you had yesterday morning.
Run a food check before recruiting or promoting:
- One meal for every unit expected to fight tomorrow. If a bench unit has no role in the boss plan, do not starve a core damage dealer to level it.
- Best food reaches the unit that needs experience. Tavern order can change who takes the strongest meal. Inspect the return order rather than assuming the newest or weakest unit is fed first.
- Production is timed to delivery. A berry, fish, bread, or meat source that completes after the Tavern phase does not solve tonight’s count.
- Beer is a temporary combat tool, not a replacement for progression. An attack-speed boost can help one night; repeated hunger leaves the roster underleveled and makes the following check worse.
If the army suddenly loses a fight that looked numerically similar to the previous one, compare the hungry status and unit levels before blaming positioning. A missing meal can reduce both immediate speed and the experience that would have produced the next rank.
Build a team by jobs, then let the Trapper widen it
The store description advertises more than seventy units and eleven heroes in the current Early Access build. That variety is a reason to avoid a named shopping list. The first-boss team needs a small set of functions:
- Contact holder: the hero or a durable unit that keeps the boss and its escorts away from the back line.
- Control: stun, push, freeze, taunt, or another effect that reduces the time multiple enemies can attack together.
- Continuous damage: a unit whose range and target access let it keep attacking while the contact holder is occupied.
- Wave cleanup: area damage, summons, piercing, or fast attacks that prevent small enemies from surrounding the hero.
A launch route used Cyclops control with Crossbowman range. Treat that as an example of job coverage, not a mandatory roster. Patch #15 changed acquisition, kingdom traits, and unit balance; the Fate and Trapper rolls in the current run may offer a different pair that solves the same geometry.
Use the free trap on a planned target
The Trapper supplies the first trap of a run for free. Do not drop it wherever the first monster happens to walk. Open the Fate choice and pick a target that fills the missing team job. During the wave, place the trap on a lane the target must cross, then let your defenders reduce that monster’s health before it reaches the trap. The official Patch #15 notes state that catch chance rises as health falls.
The trap creates a positioning conflict: killing the target too early wastes the attempt, but letting it through at full health lowers the chance and threatens the hero. Move damage or use control so the target reaches the tile wounded and separated from the worst part of the pack. After the wave, verify the caught marker in the Fate/catalog interface. Do not assume the animation succeeded.
Take kingdom traits only when the units still form a team
Multiple units from the same kingdom can activate shared traits. That bonus is useful after the functional jobs are covered. It is not a reason to field three fragile damage dealers with no control or frontline. Compare the next trait threshold with the cost of promoting and feeding the extra unit; a smaller roster with clear roles can reach the Goblin King in better condition.
Choose how each upgrade is paid before entering the Tavern
Patch #16 restored two upgrade routes. During the day, many units can again advance with their listed resources. At night, coins can pay for promotions. The two routes make the economy flexible, but only if you avoid paying twice for the same marginal improvement while another role remains unbuilt.
Before ending work time, open the sheets for the contact holder and main damage unit:
- Read the resource requirement for the next daytime upgrade and the exact stat or ability it changes.
- Compare that cost with the building or food chain competing for those resources.
- If the resource upgrade would delay a required House, meal source, or road, preserve the materials and carry coins into the night.
- If coins are scarce because automation or merchants consumed them, take the resource upgrade now and stop optional spending.
- Promote the unit that changes the next fight, not automatically the lowest-level member.
Rickard’s current Patch #16 spell is Battle Cry, which temporarily raises the team’s attack speed. It solves a damage window, not a weak economy. Spells appear from the second run onward in the documented 0.7 series, and the first spell opportunity in a run is free. If the spell UI is absent on the tutorial run, that is expected; do not delay the first build looking for a church interaction from an older patch.
Read the Fate screen as a contract with the boss
The Fate choice is not just today’s enemy color. It tells you what type of pressure the run is accumulating and, in the current patch, whether a monster is already caught. Older references describe repeated physical choices leading to the Goblin King and magical choices leading toward Blobb. Use the live preview and Calendar to confirm that relationship before spending for a specific boss; a mixed sequence or later balance change can alter the result.
When the Goblin King is the displayed boss, stop opening new economic branches. The last preparation window should answer five questions:
- Can the frontline survive long enough for ranged or sustained damage to work?
- Can the team clear the accompanying goblins without every attacker abandoning the boss?
- Did every active unit eat after the previous defense?
- Is the next promotion assigned to a unit that will remain in range?
- If Battle Cry or another combat spell is available, is it ready for a stable damage window?
Patch #15 increased the Goblin King’s health and strengthened its minions relative to the previous public balance. That makes an old “move one named unit forward and the fight is over” claim unsafe. The current fight is a lane-control check: the boss holds its preferred range while escorts create enough contact pressure to pull attacks away from it.
Goblin King: stabilize the lane before spending the burst
Begin with the durable unit slightly ahead of the damage line, but not so far forward that it meets the whole pack alone. The desired first contact is narrow: escorts stack where control or area damage can touch several targets, while the boss remains reachable by at least one sustained attacker.
Watch the first few seconds instead of immediately casting:
- If the hero is being surrounded, move control toward the contact point or shorten the frontline. Damage that is pathing around a crowd is not contributing.
- If every ranged unit switches to small enemies, add wave cleanup or reposition so one attacker retains line and range on the King.
- If the frontline is stable and the King is exposed, use Battle Cry or the available combat spell. A speed burst has more value while attacks are already connected than during target switching.
- If a trap target is also present, do not sacrifice the boss defense to engineer a perfect catch. The first clear is the priority; catching can move to another run.
- If the hero’s health falls before the escorts thin, the failure is earlier than the boss. Reload or accept the cycle and fix food, promotion, or role coverage rather than repeating the same formation.
A first clear does not require maximum recruitment. Each extra unit adds a meal and may compete for a promotion. If four units cover frontline, control, boss damage, and cleanup, a fifth recruit is useful only when its trait or ability improves one of those jobs more than the food and coin it consumes.
Turn a loss into one exact change
| Failure signal | Likely cause | Next-run correction |
|---|---|---|
| Resources are visible but a build never becomes affordable | Everything is assigned; delivery to Castle is late. | Free a carrier before adding another gathering job. |
| The same roster clears one wave, then collapses the next day | Hunger or a missed Tavern level-up reduced the effective attack cycle. | Recruit fewer units and finish the meal count before construction. |
| The boss remains healthy while escorts die slowly | Too many single-target units are switching targets or pathing. | Add control/area cleanup and keep one ranged attacker connected to the boss. |
| The frontline disappears before a spell matters | Promotion went to damage while the contact holder lacked durability. | Use daytime resources or the next night promotion on survival. |
| The expected unit never unlocks after an achievement | The run followed the pre-Patch #15 system. | Find that monster in Fate, weaken it, and catch it with the Trapper. |
| Coins vanish before the Tavern | A special worker or optional transaction consumed the promotion reserve. | Disable the automation and price the night upgrade before shopping. |
Death is part of the cycle, but a repeated loss should buy information. Note the first failing state, not the final “defeat” screen. Permanent roads, starting resources, achievements, caught units, and other discoveries make later attempts broader; they do not repair an unclear production plan by themselves.
After the first boss, bank progress before expanding again
Take the boss reward that strengthens the team already on the board. Do not choose a relic solely because an old walkthrough paired it with a unit you did not recruit. Recount food, read the next Calendar marker, and spend Shards or Glory on permanent access only after tonight’s roster remains supported.
Achievements are still worth pursuing, but their post-Patch #15 purpose is a small permanent buff shared across both kingdoms. Treat the strange conditions as later run modifiers, not as detours inside the fragile first-boss economy. Likewise, the Endless Finale introduced in Patch #15 is a build test beyond this guide’s scope; a Goblin King clear proves the opening loop, not the entire Early Access progression.
Evidence date and official records
Steam’s listing for App 2289750 names Super Fantasy Games as developer, Hooded Horse as publisher, and October 24, 2025 as the Early Access launch. It also documents two kingdoms, more than seventy units, eleven heroes, and supplies the full-resolution JPGs displayed in this article. The developer’s Patch #15 post and Patch #16 post set the evidence boundary for the Trapper, achievement buffs, spells, traits, taxes, upgrade routes, and Goblin King balance. Launch walkthroughs contributed only enduring decision points; their fixed costs, unit unlocks, and daily scripts were left behind.