Guild Boss is a shared PvE damage activity described by current community guides. One earlier-update guide discussed a named boss, multiple difficulties, keys, a multi-day window, and statue-style rewards. Those details are useful clues but remain version-bound until the live guild panel confirms them.
Confirm the current boss
Open the guild activity and record the boss, difficulty, health or phase structure, active window, key or access cost, contribution rules, attempts, and rewards. Check who is allowed to start the encounter.
Do not consume a shared key until the planned players and decks are ready.
Build sustained damage
Use attackers that maintain output across the boss duration and supports that visibly activate. Verify stack limits, domains, summons, round rules, traits, and equipment. Save the guild boss loadout separately.
Benchmark it on another durable target when possible, then compare actual guild boss damage after the attempt.
Coordinate difficulty
Choose a difficulty the guild can complete or meaningfully advance under the current rules. Higher is not automatically better when it wastes access or produces no reward. Leaders should explain the target and expected attempt order.
Members should report limitations before the key is used, not leave silently after entry.
Record contribution
Stay for the result panel. Record personal or guild damage, phase reached, attempts, confirmed currency or reward, and any remaining boss progress. Do not convert a single result into an official threshold or drop rate.
Use the evidence to change one deck variable or account goal before the next attempt.
Claim and spend rewards
Check the guild screen, inventory, Card Index, and shop. Determine whether rewards are immediate, milestone-based, claimable later, or purchased with a currency. Compare all current uses before spending.
Preserve a reserve if another guild system uses the same resource.
Improve between windows
Farm permanent upgrades, a boss attacker, compatible support, artifact, or trait that addresses the observed gap. Use Raids and World Boss as related boss benchmarks without assuming identical rules.
Return when the improvement is visible. More attempts with the same unexplained failure do not help the guild.
Protect group resources
Never share Roblox credentials or let another player log in to “do your damage.” Use normal platform tools, coordinate through trusted channels, and report scams. Consult Trello and Discord for source safety and Updates when the live boss differs from a community guide.
Use a guild boss worksheet
Record the current boss, difficulty, active window, access item, group size, personal deck, contribution measure, and confirmed reward. Add the server date. This separates the live activity from an earlier community guide that may show another boss or cost.
For each attempt, record only one intentional deck change. If several members change at once, use the personal damage measure when available rather than attributing the guild result to one card.
Plan keys and attempts
Identify who owns or can activate a key, how it is earned, and what happens if the group fails. Schedule the attempt only after required members confirm. Keep one lower-risk difficulty as a fallback if the current rules allow it and the higher target would waste limited access.
Do not activate a timed boss potion until the encounter has loaded and the correct deck is present.
Troubleshoot missing rewards
Stay through the complete result and claim flow. Check personal inventory, guild milestone progress, shop currency, and any delayed event screen. If an expected reward is missing, capture the contribution and result before rejoining.
Avoid another key until the guild understands whether the first attempt recorded. A fresh server can solve stale interface state, but it cannot recreate unrecorded evidence.
Set the next improvement
Choose one of four routes: replace an incompatible support, strengthen a sustained attacker, obtain a relevant artifact or trait, or raise an account stat that affects the fight. Test the change on a repeatable boss before the next guild key.
When the event boss changes, start a new baseline. Preserve the old record for its named boss rather than carrying the damage expectation into a different encounter.