Guildrun Synergy

How to interpret the collected evidence

The two article sources agree on the core mechanic summarized in the direct answer. Their shared wording is consolidated here rather than counted as two independent confirmations. Community strategy can explain a decision, but it does not turn that decision into an official rule.

A ranking or recommendation is strongest when its patch, mode, specialization, and sample are visible. Extracted game data can confirm a listed effect, while a player run shows how that effect behaved in one sequence. When those evidence types differ, preserve the difference instead of forcing a universal conclusion.

A practical decision framework

Start by identifying the active patch and the exact search question the page is answering. Read the offered specialization, item, relic, class condition, and timing window before committing resources. Test whether the current frontline survives long enough for the intended damage or support engine to work.

Check the same plan against the next boss and against the longer scaling demands of Endless. Align hero rank, class tags, items, relics, and positioning around one coherent win condition. Keep a safe pivot because random shops and rewards can prevent an exact recipe from appearing.

Gameplay evidence from a complete run

The caption track follows a Triple S Shard build. Tilly converts Attack Speed into repeated Shard generation, Zuri uses Poison and regeneration as the main Tank, and Dragomir can either consume Shards for permanent Crit and Omnivamp or add Vanguard with a Backup aura. The creator explains ranked shop heroes, campfire retraining, Rush and Stall timing, boss Auction Houses, class relics, item placement, and team-size progression. After the final boss the run enters Endless, where Rewind is disabled and rewards arrive every three rounds.

It ends at Endless 10 after missing the strongest Shard-triggered relics. The video should be treated as a worked example from one patch and one random sequence. Its strongest value is the visible chain of decisions: the creator reads the current offer, checks timing and class conditions, assigns an item to a specific holder, observes the fight, and changes the plan when survival or damage falls short. It supports explanations of mechanics and decision-making, but it does not by itself establish a universal ranking.

A second run as a cross-check

The caption track documents a Crit-and-Poison run from the first draft through Endless. Yuuna ranks early, gains Stealth and Crit interactions, and works with Pollen's Poison field. Zuri becomes the frontline and receives defensive purchases. At 08:17 a Backup hero is evaluated by its reserve-only effect; at 09:08 a campfire ranks Pollen; at 20:47 Yuuna reaches S rank; at 22:04 the creator checks whether duplicate relics combine; and after the final boss the team enters Endless.

The run finishes with leaderboard rank 91, demonstrating both the upside of a coherent engine and the danger of generalizing from one high-roll run. The video should be treated as a worked example from one patch and one random sequence. Its strongest value is the visible chain of decisions: the creator reads the current offer, checks timing and class conditions, assigns an item to a specific holder, observes the fight, and changes the plan when survival or damage falls short. It supports explanations of mechanics and decision-making, but it does not by itself establish a universal ranking.

Official scope

The official Steam store describes Guildrun as a single-player PvE roguelike autobattler. Players draft, level, and respecialize a guild, arrange heroes on a hex field, and combine more than 300 relics with more than 100 items. It advertises 25 heroes, 180 specializations, eight difficulties, Endless play, weekly updates, and mid-run saves.

How to verify the recommendation yourself

Identify the active patch before comparing a guide with your current game. Inspect the offered specialization, item, relic, class condition, and timing window instead of relying on a label alone. Test whether the frontline survives and whether the damage engine still works against the next boss. Record the exact difficulty, team, ranks, items, relics, and formation when a result looks unusually strong or weak.

Keep a safe pivot because random shops and rewards can prevent an exact recipe from appearing. Do not turn one creator run or one community observation into an official rule. A build is coherent when rank, class tags, timing, equipment, relics, and positioning support the same win condition. A recommendation becomes weaker when it depends on an unrecorded patch, an unknown specialization, or a perfect shop sequence.

Any unsupported number, name, reward, or release claim remains 待确认. Before combat, state which hero or effect is expected to provide survival, damage, and utility. After combat, separate a positioning failure from a rank, item, relic, or timing failure. Compare the value of an immediate upgrade with the cost of waiting for a more specific connection.

Check whether an item is on the hero that actually scales from its stats or trigger. Check whether a relic fires often enough for the current team rather than only in a perfect future setup. Treat Rush and Stall as different timing plans instead of mixing them without a clear payoff.

Prepare for the next known encounter before optimizing only for a distant Endless ceiling. When two sources disagree, keep both version and mode labels visible instead of averaging the claims. Use successful runs to form a testable hypothesis, then verify it across different shops and rewards.

Frequently asked questions

Sources used

• gguildrun.wiki — source
• guildrun.nicop-db.com — source
• www.youtube.com — source
• www.youtube.com — source
• store.steampowered.com — source

Research collected August 14, 2026. Community and creator evidence is identified as non-official; unsupported details are marked 待确认.