Jujutsu Zero Clans

Start with function. Write down what your current combat plan needs: safer engagement, more reliable pressure, better control, forgiveness after a mistake, or another outcome you can observe. Then read the clan's live description and ask whether its stated effects contribute to that need. A prestigious label is not useful when its effect never appears in the situations you play.

Evaluate the clan alongside the cursed technique rather than in isolation. A technique determines much of the moment-to-moment kit, while a clan may modify or support the broader setup. The useful question is not which clan is best in general; it is whether this outcome makes your chosen plan more consistent under the current patch.

Finally, include your own execution. A theoretical interaction may require timing or positioning you cannot yet reproduce. Test the setup in the same activity several times, keep conditions as similar as possible, and record what changed. Consistency across attempts is stronger evidence than one unusually good result.

• Define the combat problem before judging the clan.
• Read the current in-game effect text, not an old summary.
• Compare the clan with your actual cursed technique and playstyle.
• Test repeated situations instead of one highlight attempt.

The official Roblox description listed two codes at the August 8, 2026 review. MAHORAGA included 30 Clan Rolls, while 190KLIKES included 35 Clan Rolls. Those entries verify the reward amounts and names at that time; they do not verify reroll odds, a pity system, or the value of any particular clan.

Before spending rolls, define an acceptable outcome and a hard stopping point. An acceptable outcome can be functional rather than rare: a clan whose live effect supports your current plan may be enough to continue progressing. A stopping point protects the remaining rolls for a future patch or for when you understand the system better.

Never infer probability from a small personal sample. A few rolls cannot establish a reliable drop rate, and an animation or ordering pattern is not proof that the next result is predictable. Unless the game or an official source displays odds, this guide leaves them unknown.

Describe both parts in plain verbs. What does the technique let you do reliably, and what does the clan's current text say it changes? Look for overlap that improves a repeatable action, or complementary effects that cover a known weakness. Avoid declaring synergy from matching names, rarity colors, or character associations alone.

Use a small test matrix. Play a consistent encounter with the same technique and current clan, record a few observable outcomes, then change only the clan if the game gives you a safe way to do so. Track completion consistency, resource pressure, and the mistakes that end an attempt. Exact damage comparisons require controlled capture; impressions should be labeled as impressions.

Recheck the pair after a balance update. The current official page highlights Ten Shadows Part 2 and names changes involving Mahoraga behavior, showing why patch context matters. A recommendation made before a named behavior change should not be assumed current even when the clan itself was untouched.

• Translate descriptions into observable actions.
• Look for repeatable overlap or coverage of a real weakness.
• Change one build component at a time.
• Date every conclusion with the current update title.

This page does not publish a complete clan list yet because the available official web source does not provide one. Publishing names, grades, bonuses, or roll odds from memory would make the page look complete while giving players no reliable way to tell which details still match the beta build.

A clan entry is ready for publication only after a current live capture or official source verifies the displayed name, exact effect wording, any grade label, and the date. If numerical effects appear, the capture must preserve units and conditions. A second observation should confirm that the entry was not a temporary tooltip or test-server state.

Until that evidence exists, use the evaluation method above on the clan shown in your own client. The absence of an invented catalog is intentional. It keeps search-friendly certainty from outrunning the evidence available to a player making an irreversible or scarce-resource decision.

When the game updates, first compare the official title and description with the date of your last test. Look for explicit clan, technique, stat, or behavior changes. Then open the live clan description and capture any wording difference before rerolling or changing the rest of the build.

Retest only the affected interaction first. If a technique changed but the clan text did not, keep the clan stable and see whether the old synergy still produces the same practical result. If the clan itself changed, use the same encounter and technique as your baseline. Controlled retesting is faster than rebuilding everything after each patch.

Downgrade old conclusions when evidence is incomplete. Mark an entry as needing review instead of keeping an assertive ranking. A dated uncertainty label tells players exactly what to verify and is more honest than a tier chart whose underlying effects no longer match the interface.

• Record the update title and test date.
• Capture current effect wording before making changes.
• Retest one affected interaction at a time.
• Remove or label claims that no longer have current evidence.

Should a beginner reroll immediately? Not without a reason. Learn what the current outcome does, test it with your technique, and preserve rolls until you can name an improvement you are seeking. The official codes can provide rolls, but a reward is not evidence that spending all of them at once is optimal.

Does rarity prove a clan is better for every build? No conclusion that broad is supported here. Rarity, if displayed in the live game, is an acquisition label. Build value depends on current effects, technique interaction, activity, and execution. Test the outcome you have against the goal you set.

Where are the odds and full tier list? They are intentionally absent until current, reproducible evidence supports them. Use a tier list only when it states its patch, criteria, and test method. This wiki will add catalog details when each entry can be traced to a current official source or documented live capture.