A merge can raise a tier and still make the run worse. The receiving weapon gains the new identity, while a sacrificed weapon gives up its starred perks and becomes scaling material. The useful question is therefore not “can these two icons combine?” It is “which weapon must survive, and what value am I willing to erase?”
Current-build boundary: this guide was checked on August 12, 2026 against the Early Access store data, developer FAQ, official news through hot-fix v0.574, and the current developer-linked weapon data. Recipe rows below are an observed map, not a promise that every future patch will preserve the same inputs. The Steam recipe page is readable but displays a removed/incompatible warning; confirm an unfamiliar result in the in-game Codex and the merge preview before spending a developed weapon.
Name the recipient before opening the merge screen
Write the intended result as a one-line plan before buying the second input. That small pause prevents the most expensive error in the system: treating two developed weapons as interchangeable when only one identity survives.
- Choose the weapon whose attack pattern you need after the merge. That is the recipient line. If the build depends on a beam, mine field, aura, melee arc, or air strike, the final weapon must still produce that delivery pattern.
- Read every starred perk on both candidates. The developer states that starred weapon effects do not stack and do not transfer. A donor with a run-defining perk is not “free damage”; using it may remove the interaction you were building around.
- Check the final card rather than adding two old cards in your head. A merge transfers part of the donor’s stats and turns its damage into permanent Flat Damage, but it is not a simple sum of every displayed number.
- Keep a fallback. If the preview does not show the intended weapon or the Codex has not recorded the recipe on the current client, cancel. One skipped shop offer costs less than rebuilding a failed run.
A practical recipient test is uptime. Ask which weapon can apply an added point of Flat Damage most often to the targets that matter. A fast multi-hit weapon may use that bonus repeatedly; a slower weapon may justify the role only if its hit area, control, or boss uptime is stronger. Do not choose by a tier color alone.
Separate tier, damage transfer, and perk identity
Three things happen around the same confirmation, but they solve different problems:
| Layer | What changes | Failure signal |
|---|---|---|
| Recipe identity | The inputs resolve into a named higher-tier weapon or a special result | The result name is not the family you planned to play |
| Scaling transfer | Part of donor stats moves, and donor damage contributes permanent Flat Damage | The preview gives less useful damage than keeping both weapons active |
| Perk reset | The output uses its own perk set; starred donor effects disappear | The interaction that cleared waves is absent from the new card |
This distinction explains why a technically valid recipe can be a bad click. A heavily upgraded donor may contain excellent damage but also the only source of control, resource gain, or kill scaling in the current setup. If the new weapon cannot reproduce that function, delay the merge until another weapon covers it.
Upgrading and merging are also different commitments. An upgrade strengthens the existing card and may open perks. A merge replaces two active cards with a new weapon. Upgrade when the present attack pattern is already correct; merge when the new identity and the transferred damage together are worth the lost slot and perks.
Use five arms early, then compress with a deadline
The developer’s current advice is deliberately two-stage. Early in a Crusade, filling arms gives more damage sources, more shop options, and more possible recipes. Later, those same slots become a liability if they remain five unrelated projects.
| Run state | Decision | What you are testing |
|---|---|---|
| Opening offers | Take functional coverage, not five copies of one idea | Which attack keeps hitting while you move and which one controls the crowd |
| First duplicate or special pair | Check the recipe, but do not auto-confirm | Whether the result preserves the useful delivery pattern and perks |
| One weapon clearly leads | Mark that weapon as recipient; label weaker cards as donors or utility | Where additional Flat Damage will produce real uptime |
| Shop starts offering Tier 2 support | Collapse one pair and attach upgrades around the result | Whether the build has become a carry plus support rather than five starters |
| Boss approach | Stop refreshing for a fantasy recipe | Whether current damage, survival, and targeting can finish the actual fight |
Use a hard pivot signal: if the intended pair has not appeared and another weapon has become the clear damage source, fund the weapon that exists. Repeated refreshes are not progress. A run with a coherent Tier 2 carry and survival is stronger than a pile of half-funded cards waiting for one exact roll.
Reject upgrades that do not work with the weapon type
Element is only one filter. Delivery type decides whether Pierce, Bounce, Projectile count, Range, and control can actually express their value.
| Weapon type | Stats that naturally fit | Trap to avoid |
|---|---|---|
| Standard ranged | Projectiles, Pierce, Bounce, Range | Buying area-only support when the card needs better lane coverage |
| Melee | Range, Projectiles for shockwaves, damage, survival | Expecting Bounce to work like it does on a normal projectile |
| Vortex emitter | Pierce and Range to improve the orbiting damage field | Treating it as a direct straight-shot weapon |
| Air strike | Projectiles, Bounce, explosion support | Paying for Pierce even though the falling shot does not use it |
| Laser | Range and effects that benefit repeated line hits; Bounce can branch at contact | Building it as if travel time and ordinary projectile behavior apply |
| Grenade launcher | Explosion radius/chance, Projectiles, Bounce | Buying Pierce for an arc that resolves on ground contact |
| Mine launcher | Additional mines, Bounce-derived splits, explosion support | Judging it only by immediate shot travel |
| Aura emitter | Range and extra pulses from Projectiles | Spending on Pierce or Bounce, which the aura does not use |
Run the same filter on status. Fire adds burn based on the weapon’s damage; Electric applies a slow whose strength follows damage dealt; Holy lacks a status and instead fits critical-focused weapons. Frost can immediately stop ordinary enemies, while Stun fully disables them and makes hits critical. Bosses ignore Stagger, so a boss build that exists only to raise Stagger is missing a second job.
Observed Tier 2 recipes worth recording
The following rows were visible in the readable community recipe table and their result names match the current 65-weapon data. They are presented as a discovery ledger. The current-client preview is the final confirmation, especially because the recipe page carries a Steam compatibility warning.
| Input A | Input B | Observed Tier 2 result |
|---|---|---|
| Machine Gun | Machine Gun | Auto Cannon |
| Magnum | Magnum | Blaster |
| Scalding Crossbow | Scalding Crossbow | Blazing Crossbow |
| Shock Disc | Shock Disc | Chain Bolt |
| Shock Maul | Shock Maul | Electrohammer |
| Magnum | Flare Cannon | Detonator |
| Flare Cannon | Flare Cannon | Firestorm |
| Ember Sword | Ember Sword | Infernoblade |
| Holy Spear | Holy Spear | Lance |
| Sniper Rifle | Magnum | Laser Rifle |
| Sniper Rifle | Sniper Rifle | Longshot |
| Recharger | Recharger | Megacharger |
| Sniper Rifle | Recharger | Railgun |
| Sawed Off Shotgun | Sawed Off Shotgun | Shotgun |
| Twin Spark | Flare Cannon | Skystrike |
| Cutter | Cutter | Spinshot |
| Twin Spark | Twin Spark | Thunder Crossbow |
| Machine Gun | Sawed Off Shotgun | TwinBlast |
Two patterns matter. Identical Tier 1 weapons usually continue their family, while a few mixed pairs change the delivery type: Sniper Rifle plus Magnum becomes Laser Rifle, Sniper Rifle plus Recharger becomes Railgun, and Twin Spark plus Flare Cannon becomes Skystrike. A mixed recipe deserves extra scrutiny because the output may invalidate several attached stats even when the tier increase is correct.
Eight Tier 2 weapons begin at the Gunsmith
Do not burn shop refreshes trying to discover a Tier 1 pair for every Tier 2 name. The observed table separates eight weapons as Gunsmith unlocks with no recipe shown:
- Burning Pike
- Consecrated Mace
- Devastator
- Flamethrower
- Flarefield
- Freezing Blade
- Proximity Spark
- Voltfield
If one of these is absent from Prayers, diagnose the Cathedral first: verify it is unlocked in the Gunsmith, then verify the current hero/loadout and Prayer pool. A missing shop offer is not evidence of a secret merge. The v0.574 line specifically fixed an empty Wave 1 shop when no Tier 1 weapons were available, so update before treating an empty row as a recipe problem.
Tier 3 requires Ascension Protocol and two Tier 2 inputs
Ascension Protocol is the passive that permits Tier 2 weapons to create Tier 3 results. If two matching cards only yield a small stat improvement, check three conditions in order: both inputs must actually be Tier 2, the passive must be active for the current progression state, and the final result must appear in the live preview.
| Tier 2 input | Second input | Observed Tier 3 result |
|---|---|---|
| Spinshot | Spinshot | Aegis Cycler |
| Devastator | Devastator | Annihilator |
| Flarefield | Flarefield | Pyrefield |
| Burning Pike | Burning Pike | Blazing Halberd |
| Consecrated Mace | Consecrated Mace | Divine Crusher |
| Freezing Blade | Freezing Blade | Frostreaver |
| Auto Cannon | Auto Cannon | Gatling |
| Firestorm | Firestorm | Heavenfall Incinerator |
| Infernoblade | Infernoblade | Hellblade |
| Blazing Crossbow | Blazing Crossbow | Infernal Crossbow |
| Flamethrower | Flamethrower | Infernothrower |
| Railgun | Railgun | Ion Rail |
| Longshot | Longshot | Light Beam |
| Detonator | Detonator | Overdetonator |
| Lance | Lance | Sanctum Pike |
| Thunder Crossbow | Thunder Crossbow | Shockstring |
| Laser Rifle | Laser Rifle | Solar Rifle |
| Electrohammer | Electrohammer | Stormbreaker |
| Chain Bolt | Chain Bolt | Stormbringer |
| Skystrike | Skystrike | Stormfall |
| Voltfield | Voltfield | Stormfield |
| Blaster | Blaster | Super Blaster |
| Shotgun | Shotgun | Super Shotgun |
| Proximity Spark | Proximity Spark | Teslabringer |
| TwinBlast | TwinBlast | Trinity Blast |
| Megacharger | Megacharger | Ubercharger |
Do not read this as a Tier 3 shopping list. The two Tier 2 cards have already absorbed resources and possibly unique perks. Before combining them, compare the output with the value of two independent firing patterns. A Tier 3 card wins only when its identity, transferred Flat Damage, and freed arm together outperform both current weapons.
Build around a delivery pattern, not an element label
Use the recipe map to preserve how damage reaches enemies:
- Fast-hit carry: Auto Cannon into Gatling wants reliable on-hit value. Flat Damage has more chances to matter when the output keeps firing, but confirm that the sacrificed card is not providing the only useful perk.
- Long line: Sniper Rifle routes can become Longshot, Laser Rifle, or Railgun before continuing to Light Beam, Solar Rifle, or Ion Rail. Decide whether you want ordinary projectiles, a laser line, or the Railgun identity before attaching narrow support.
- Area control: Flare Cannon can continue to Firestorm, combine with Magnum for Detonator, or combine with Twin Spark for Skystrike. The correct pair depends on whether the run needs persistent fire, explosions, or guided backline coverage.
- Close pressure: Shock Maul, Ember Sword, and Holy Spear routes demand enough survival to stay in useful range. Their tier path cannot compensate for a hero that dies while the attack is reaching its target.
- Persistent field: Flarefield and Voltfield come from the Gunsmith rather than a listed Tier 1 pair, then continue to Pyrefield or Stormfield. Unlock access before planning an entire run around seeing them.
After each wave, compare three signals: which weapon produced damage, which effect prevented contact, and which card spent time without a target. Promote the weapon that keeps solving its assigned job. A theory build that cannot maintain uptime on the current map should pivot before the next expensive merge.
Use v0.574-era refunds and loadouts to test the plan
The Endless Ascent update changed the cost of experimentation outside the run. Prayer and weapon refunds are now 100%, presets/loadouts can save hero configurations, all 13 base Tier 1 weapons may be banished, and the Prayer pool has a current minimum of 60. Hot-fixes v0.572–0.574 corrected the minimum-pool count, hero preset unlocks, and an empty first-wave shop case.
Turn those systems into a controlled test:
- Create one preset around a specific recipient family rather than a vague element.
- Banish Tier 1 weapons that cannot produce the planned route, but leave enough alternatives to survive a poor opening.
- Run until the first meaningful merge decision, then record the previewed result, lost perk, and new Flat Damage.
- Refund the setup in the HUB if the route cannot generate reliable offers or solve the intended enemy pattern.
- Keep a second preset for a different delivery type so a balance patch does not invalidate every test at once.
The minimum Prayer pool prevents a perfectly deterministic shop. Banishment improves odds; it does not guarantee one recipe. A robust preset therefore needs at least one acceptable pivot and a survival plan that works before the target pair appears.
Diagnose a merge that did not create the expected weapon
| What happened | Most useful check | Next action |
|---|---|---|
| Two cards combined but the name did not change | Confirm both inputs are the required tier, not one developed Tier 1 and one Tier 2 | Cancel future attempts until the Codex/preview shows the named output |
| A Tier 3 recipe gives only stats | Check Ascension Protocol in current Cathedral progression | Unlock/activate the passive, then retry with two actual Tier 2 copies |
| The result is correct but damage feels worse | Compare lost starred perks and attack uptime | Rebuild around the new identity or keep the pair separate next run |
| A Gunsmith weapon never appears | Check its unlock and the current Prayer/loadout pool | Unlock it first; do not search for an unlisted Tier 1 recipe |
| Wave 1 shop is empty | Verify the client is at v0.574 or newer | Update; v0.574 specifically addressed this state |
| A web table conflicts with the client | Use the live merge preview and Weapons Codex | Follow the client and treat the web row as stale |
The stop condition is simple: if the current preview cannot show the promised result, do not supply your own missing rule. Early Access has already changed weapon pools, balance, and progression. Preserve the developed cards, take a viable build forward, and record the client behavior for the next attempt.
Current-build references
Identity and media come from the official Steam store. The merge-transfer, perk, type, and event rules come from the pinned developer FAQ. The update boundary is the Endless Ascent announcement plus the v0.574 hot-fix. Community recipe references were used as a discovery ledger only; the live Codex and preview override them.