Why this is a method, not a frozen image
Jujutsu Shenanigans tier lists disagree because they often rank different things. A duel specialist may value repeatable confirms and safe pressure. A public-server player may value mobility, area coverage, and the ability to disengage from third parties. Creator Clash adds custom-content uncertainty. A new character can look dominant while opponents are still learning its animations.
For those reasons, this page does not pretend one S-to-D graphic is universally current. It gives you a repeatable scoring method. Use it with the roster visible in your server, record the update date, and publish separate results for separate modes.
Six scoring categories
Score each character from one to five in six categories: neutral, conversion consistency, defense, mobility, team or crowd value, and execution reliability. Neutral measures the ability to create a safe opening. Conversion asks what the character gains from that opening in realistic latency. Defense includes reversals, escape-compatible routing, and the ability to reset.
Mobility measures more than travel speed; it includes angle changes and recovery position. Team value covers area control, interruption, and avoiding friendly disruption. Execution reliability asks whether ordinary players can reproduce the plan without a rare wall angle or perfect connection.
Keep access and patch confidence beside the score, not hidden inside it. An early-access or changing kit may be strong but uncertain. A public, stable character is easier to recommend to every player.
Separate the modes
Make at least three sheets: controlled one-versus-one, team modes, and open public servers. For duels, weight neutral, consistency, and defense most heavily. For teams, increase team value and safe area pressure. For public servers, increase mobility, awareness demands, and the ability to end a route early.
Ranked deserves its own version if the current rules, lives, arena, or matchmaking differ from casual duels. Do not carry a public-server judgment into ranked without testing. Similarly, Roulette can impose rules that temporarily invert normal strengths.
Custom movesets in Creator Clash cannot be ranked on the same sheet as standard characters unless the exact content set is fixed. Label the workshop item, version, and match rules first.
Collect useful evidence
Run multiple matches against varied opponents rather than counting one highlight. Record the matchup, mode, outcome, connection quality, and which interaction decided the round. Separate “the character could not answer this” from “the player did not know the answer.”
Test block behavior and miss recovery in a private server. A move that looks overwhelming on hit may be highly punishable when blocked. Track ragdoll escape use, awakening access, wall dependence, and whether a route survives ordinary latency.
Patch notes and community wikis are discovery tools. The live experience is the operational check. If a move changed, lower confidence until the relevant matchups have been retested.
Turn scores into tiers
After mode weighting, use tier bands with written definitions. S can mean “sets the mode’s pace with few exploitable gaps,” A “strong and consistent with clear counterplay,” B “competitive but matchup or execution dependent,” and C “requires more conditions for comparable value.” Avoid a trash tier that tells readers nothing.
Characters with close scores should share a tier. Do not manufacture precision by ordering them one through fifteen when the evidence cannot support that granularity. Mark provisional placements for new or incomplete characters such as a changing Sky Assassin build or a variable Register state.
Add a short reason beside every placement. “Strong” is not a reason; “reliable mid-range starter and safe reset in duels” is testable.
Personal selection versus competitive ranking
Your best character is often the one whose decisions you can execute. A theoretical top tier played without block discipline will lose to a familiar mid tier. Use the ranking to choose what to test, not as permission to blame every loss on the roster.
New players should prioritize clear feedback and a repeatable short route. Experienced duel players can value narrow confirms after proving they work under their usual latency. Team players should consider whether their effects obscure allies or start unwanted fights.
If two choices are close, pick the one you enjoy enough to practice. Familiarity improves recognition, spacing, and recovery management—all factors the raw kit score cannot supply.
A publishable tier-list checklist
State the game update or check date, server region if relevant, mode, rules, sample size, access assumptions, and whether awakenings are included. Show the weights. Label community claims separately from measured tests. Revisit provisional entries after opponents gain matchup experience.
Link each placement to a character guide or evidence note. Our Sky Assassin, Register, and Disaster Plants pages demonstrate the kind of version caveat that should accompany a rank.
A useful tier list helps a reader reproduce the judgment. If it only shows colorful rows and absolute claims, it is entertainment rather than a dependable guide.