Patch scope: This guide covers the playable Guildrun Demo on patch 0.5.3, still the latest official patch checked on August 9, 2026. If the client or official news feed shows a later patch, recheck every number below before spending on Funke.
The direct answer: choose The Detonator when groups survive Funke’s first cast, choose The Inferno when a boss or other durable target outlasts the team, and choose The Stoked only when the formation already produces enough Burn events to power a Mage engine. Patch 0.5.3 reduced Detonator’s output and strengthened Inferno’s boss timing, so an older tier list that always sends Funke down Detonator is no longer a reliable build plan.
Funke remains a ranged Mage built around coverage. Wildfire hits every enemy in range for 175 damage plus 200% of Magic and applies 12 Burn plus 66% of Magic. The developer’s balance notes describe him as exceptional in non-boss fights but weak against bosses. A good Funke build should preserve that wave-clearing strength without pretending one hero can cover every fight.
Match Rank B to the fight that is actually failing
| First visible loss | Rank B choice | What the next fight should prove |
|---|---|---|
| Several normal enemies remain after Wildfire | The Detonator | Funke casts while multiple living targets are still in range, and the added Burn ticks finish or heavily weaken the group. |
| Waves are stable, but a boss survives | The Inferno | The opening Burn lands and the frontline survives long enough for the Stall 15 application. |
| Burn already triggers repeatedly around one or more Mages | The Stoked | The Magic and Mana engine activates often enough to matter, including when Funke moves to reserve. |
| Funke dies before his first useful cast | Fix the formation first | He survives behind first contact without losing the targets Wildfire needs to reach. |
Do not buy a duplicate and then search for a reason to justify the offered specialization. Watch one comparable fight first. The useful evidence is the first event that goes wrong: early focus on Funke, grouped enemies surviving, or one durable target remaining after the wave is solved.
Make the first cast the formation test
Place Funke behind the unit taking first contact, then check target coverage before the battle resolves. Moving him to the safest-looking hex can still be a loss if important enemies leave his range. Moving him closer can also be a loss if melee pressure reaches him before Wildfire.
Judge the setup with three observations:
- First contact: the frontline, not Funke, should receive the opening pressure.
- First cast: Wildfire should occur while the enemies you need to hit are alive and inside his range.
- First survivor: identify whether the remaining threat is a crowd or a boss. That survivor tells you which Rank B branch or teammate the run lacks.
If Funke is hit before casting, change lane or spacing before adding slower damage. If he casts safely but misses the dangerous group, trade a little safety for access. Only evaluate the specialization after both conditions are true; otherwise the board is testing placement, not the build.
Detonator needs living targets, not more setup
The Detonator adds Burn-damage ticks to enemies in range whenever Funke casts. On 0.5.3, that effect is 7 base ticks plus 7 per rank, down from the old 10-plus-10 value. It is still the clearest branch when ordinary encounters consume too much health or leave too many bodies on the board, but the nerf makes it a job-specific choice rather than an automatic best specialization.
The branch succeeds when Funke gets a meaningful cast into a group. Cast acceleration or a cast-triggered Burn modifier can improve that conversion, but only after the formation creates the cast window. If waves become comfortable and the next boss still wins, stop feeding the same strength. Preserve the working Detonator package and direct the next board slot, item, or resource toward durability or boss damage.
Inferno buys range and a second clock
The Inferno gives Funke two additional attack range and applies Burn at combat start and again after Stall 15. Patch 0.5.3 corrected the displayed base application to 25 Burn and improved its scaling to one additional Burn per three Magic. That makes it the branch with the clearest long-fight and boss purpose.
The extra range helps Funke stay behind first contact, but the second application is not free damage: the team must still be alive at Stall 15. Watch the frontline before the timer. If it collapses early, add immediate protection. If it nearly reaches the trigger, a modifier such as Stall Certainty can move Stall effects six seconds earlier when offered. If the trigger lands and the boss still survives, the missing job is more boss damage rather than another layer of wave control.
The Stoked is a reserve engine, not emergency damage
The Stoked turns Burn damage events within a Mage’s reach into Magic for that Mage and Mana for Funke; its Mage effect also works from Backup. This can make the branch valuable in a Mage-heavy formation without requiring Funke to occupy an active slot. It does not create an immediate rescue when the board has too few Burn events or dies before those events repeat.
Use a simple reserve test. Move The Stoked off the active board only when the remaining formation can still apply Burn, then watch whether the Mages continue gaining value while the freed slot improves survival or boss coverage. If the engine stops or produces no visible difference before the fight is decided, return to the branch that changes the current fight directly.
Let the three Rank A and S offers repair the branch
Funke’s Rank A and S modifiers are random three-choice offers from the Mage pool. A guide cannot promise Arcane Destruction followed by Burning Casts, so read the trigger before comparing the payoff.
| Offer pattern | Useful when | Reject it when |
|---|---|---|
| Cast payoff such as Arcane Destruction, Burning Casts, or Burning Absorption | Funke already casts safely and the current branch benefits from more cast or Burn conversion. | The first cast happens after the formation has already failed. |
| Acceleration such as Fast Cast or Instacast | An earlier or additional Wildfire changes the wave or boss timing you just observed. | The team needs a living frontline more than another cast. |
| Positioning value such as Hermit | Funke can remain alone in the back two rows without losing protection or range. | The required spacing exposes him or removes important targets from Wildfire. |
| Stall value such as Stall Certainty, Stalled Heat, or Stalled Growth | The formation reaches the relevant timer consistently. | The trigger arrives after the tank or Funke is already gone. |
After choosing, verify that the icon or stat change appears on schedule. A powerful effect that never reaches its condition is a dead offer for the current board. Use the next position, item, relic, or S-rank choice to restore trigger access or cover a different job; do not build the entire run around a modifier name that may never appear.
Cover the timing Funke cannot own
A Funke formation still needs first-contact durability and enough sustain to reach the selected cast or Stall timing. Ming is one patch-current frontline candidate when offered: 0.5.3 improved the Act 2 scaling of his three specializations. He is not mandatory, and neither is any fixed portrait. The real requirement is that the chosen unit survives long enough for Funke’s branch to activate.
When waves are secure but bosses remain the wall, Karsu has the clearest developer-documented complementary timing. The same 0.5.3 notes describe her as strong against bosses and weaker in ordinary Act 2 fights—the inverse of Funke’s profile. Use Funke to keep the route stable, then add Karsu or another genuine boss performer only when the formation can protect both damage windows.
This is also the point to stop copying a universal item or relic tier list. Magic can improve Wildfire’s direct hit and Burn scaling; cast frequency can help Detonator or cast modifiers; frontline defense can buy the time Inferno needs. The correct offer is the one that activates before the current loss point and covers a job the team does not already solve.
Confirm the build across two comparable fights
Change one controllable variable, then watch first contact, Funke’s first cast, the chosen specialization trigger, and the health of the final survivor. Keep the change only if it improves the failure you named. On the next comparable fight, leave that correction in place and test the next missing job.
The build is doing its work when Funke survives to reach the intended group, the Rank B trigger occurs before the fight is decided, and the roster has a separate answer for whatever survives him. If a later patch changes the numbers, keep this observation order but rebuild the specialization decision from the new official values.
Patch history and the current game entry are available on Guildrun’s verified Steam page.