Jujutsu Zero CT Buffs, Drop Buffs & New Codes

The official update groups its technique work into three named areas: Shrine, Limitless, and all Special Grade Cursed Techniques. That wording establishes a broad buff pass, not a universal ranking. It does not say that every move changed, that the same part of every kit improved, or that one technique is now best for every raid, boss, or PvP matchup.

Treat the patch title and bullet list as the source of truth for scope. If an older tier list, damage showcase, or farming route conflicts with your current client, the new client wins. Preserve the older result as a dated baseline, then compare one action at a time. This prevents a changed weapon, clan, passive, enemy, or server condition from being mistaken for a Cursed Technique buff.

Official media

Official title

[⛩️BUFFS] Jujutsu: Zero

Patch label

Balances + Fixes

Named CTs

Shrine + Limitless

Broader scope

All Special Grades

Loot changes

Gear + raid crates

Other work

Guidebook + performance

Start with the exact build you used before the update. Keep the same technique, clan, weapon, passive, stats, and familiar target when the live game allows it. Record the visible move description and any displayed cost or cooldown before entering combat. Run one short sequence twice, then change only the move or condition you are investigating. A repeatable comparison is more useful than a large damage screenshot with no baseline.

For Shrine and Limitless, do not assume the named buff applies to the move you care about. Inspect the current technique panel first, then test startup, recovery, area, resource use, and consistent output separately. For another Special Grade technique, use the same checklist instead of importing a conclusion from Shrine or Limitless. The phrase all Special Grades confirms coverage, but it does not prove identical treatment.

Avoid rerolling solely because a ranking published before August 19 places your technique below another one. A buff can improve reliability, farming comfort, or a specific encounter without changing the overall order. Save limited rolls until you have tested the kit you already own in the activity that matters to you.

1. 01
   Capture the live panel

   Record the technique name, visible descriptions, costs, cooldowns, and patch title before testing.

2. 02
   Choose one repeatable target

   Use the same encounter and starting position so enemy state is less likely to distort the comparison.

3. 03
   Run a stable baseline

   Keep gear, clan, passives, stats, and sequence unchanged for at least two attempts.

4. 04
   Change one action

   Test the move or condition you care about while leaving the rest of the setup stable.

5. 05
   Decide by activity

   Judge the result for your raid, farming, boss, or PvP goal instead of declaring one universal winner.

The official note says gear drop rates were heavily increased. It does not identify every eligible activity, name a new percentage, promise a drop after a fixed number of runs, or confirm that every gear item received the same change. Use the reward preview and result screen in your current client to connect an activity with the item you want before committing to a long farm.

Measure a complete loop: queue or travel time, clear time, reward claim, and return to the next attempt. Keep a simple log of eligible clears and visible gear results. That log helps you compare activities without turning a small sample into a global drop-rate claim. If the target item is absent from the current preview, stop and verify whether it moved, rotated, or requires another activity.

A heavier drop rate can make consistent clears more valuable than the hardest nominal option. Choose the route you can finish reliably, then compare total useful gear over total elapsed time. Preserve unfamiliar gear until you confirm its current use; balance updates can change which pieces support a technique or activity.

• Confirm the target gear in the current reward or collection interface.
• Track complete eligible clears, not only successful drops.
• Record time and result without claiming an official percentage.
• Recheck after a server change or hotfix.

Overworld Raid Crate drops are separately named as buffed in the official description. That wording is narrower than a promise about every raid, every crate, or every item. Confirm that the activity and reward in front of you are explicitly an Overworld Raid and its crate before applying the patch note to the result.

Open the live crate or reward detail when one is available and capture the full item list before farming. After a clear, verify the crate name and the actual inventory change together. If an older guide shows a different crate label, entry point, or reward pool, treat it as historical until the current interface reproduces it. Do not use this note to assign a new percentage or guarantee to a rare material.

For a group, agree on the same success condition before starting: one completed Overworld Raid, one correctly identified crate, and one recorded result. This makes reports comparable. A player receiving an item once confirms that the item can appear in that observed result; it does not prove the rate or that every difficulty shares the pool.

The official update says Guidebook rewards increased. It does not publish a table of old and new quantities or say that every Guidebook entry changed. Open the current Guidebook, identify the specific objective and displayed reward, then capture the claim result. Use that visible panel for planning rather than an older screenshot or remembered quantity.

Check completed but unclaimed entries before spending resources elsewhere. A reward increase can change the best order for early progression, but only the live objective list can show which rewards are available to your account. Do not claim that the Guidebook now replaces another farm unless a complete comparison includes requirements, time, repeatability, and the actual current payout.

If the displayed reward and the claimed result differ, preserve both screens and the server time. That is a useful bug report. Rejoining may place you on a newer server, but confirm that your objective state is saved before moving. Avoid repeated claims or automation while the discrepancy is unresolved.

Performance optimizations are part of the official scope, but the note does not promise a frame-rate target, device-specific gain, or fix for every crash and latency problem. Compare the same device, graphics setting, network, server size, and activity where practical. A smoother session is a useful observation; it is not evidence that every player will receive the same improvement.

If an ability, reward, or interface behaves unexpectedly, first confirm that the official game title reflects the buffs update. Save the exact screen or error, rejoin a normal server once, and repeat the smallest safe test. Do not spend additional rolls, materials, or crates merely to reproduce a suspected bug. Report the observation with device, time, server state, and the action that produced it.

Older Sukuna content remains available as a historical field file because its unlock routes may still answer a specific question. Its patch status has changed: use the current CT Buffs page for live balance, rewards, and codes, and use the older file only for Sukuna's Mark context that your current client still confirms.

• Match device, settings, network, and activity before comparing performance.
• Record the exact client response instead of labeling every failure a bug.
• Rejoin once, then stop if reproduction would consume scarce resources.
• Separate the live balance patch from the archived Sukuna patch guide.

The latest official game description lists CTBUFFS for 1,000 Cursed Crystals, 10,000 Lumens, and 50 Clan Rolls. It also continues to list 200KLIKES for 5,000 Lumens, 500 Crystals, and 50 Clan Rolls. The description says the next code is planned at 210K likes. These are dated official listings, not a guarantee that every account or later server will accept them.

Copy each code exactly into the field inside the official Jujutsu: Zero experience. Codes can be disabled independently of a client update. If an exact entry fails, read the full response, check whether it was already used, compare the current official description, and try one fresh official server before treating the code as unavailable.

The official description also continues to advertise double clans and a 30% luck bonus on weekends. It does not publish reroll odds or define every system affected by luck. Keep the bonus, the code rewards, and any banner probability as separate facts when planning rolls.

• CTBUFFS — 1,000 Cursed Crystals, 10,000 Lumens, 50 Clan Rolls
• 200KLIKES — 5,000 Lumens, 500 Crystals, 50 Clan Rolls
• Next like code announced for 210K likes
• Official listing checked August 20, 2026

Start by claiming any currently listed code through the official in-game interface, but leave scarce rewards unspent. Review your technique panel, Guidebook, current activity rewards, and gear goals. Choose one affected system and capture a baseline before changing the build. For loot, record complete eligible clears and actual result screens. For performance, compare the same conditions rather than two unrelated sessions.

Return to this field file after a visible hotfix or description change. A reliable guide should update the changed field and preserve the date, not silently turn an older test into a permanent rule. Until exact values are published or reproduced with adequate evidence, the official scope and your live client remain the strongest safe planning tools.

1. 01
   Confirm the update

   Look for the [⛩️BUFFS] title and current balance-and-fixes description.

2. 02
   Record before spending

   Capture technique, Guidebook, gear, and reward panels before using rolls or materials.

3. 03
   Test one system

   Choose CT balance, gear, raid crates, Guidebook rewards, or performance and hold other variables stable.

4. 04
   Use dated results

   Save the server date and patch context with every conclusion so a hotfix can be compared honestly.

5. 05
   Escalate discrepancies

   Preserve the exact panel and result when the current client contradicts the official scope or visible reward.