A good SLAYER clan reroll plan starts with a faction and a stop rule. The public-test roll screen has been observed displaying guarantees for Legendary+ and Mythic results, but exact thresholds, counters, costs and whether progress survives every kind of reroll must be confirmed in the current client. Read the visible pity text before spending anything.
Before the first reroll
Confirm whether the character is following the Slayer or Demon route. The rosters and passives are different. Open Slayer Clans or Demon Clans and choose three acceptable roles, such as safe learning, sustained pressure, squad support, low-health recovery or a specific matchup.
Record your current result, reroll count, visible pity message and every currency or token balance. If the interface separates Clan, Breathing and Demon Art rerolls, make sure the button you press consumes the intended pool. A code can grant several kinds of reroll at once, and confusing the counters is an expensive mistake.
Understand pity without guessing
A detailed October 19 public-test walkthrough observed text reading “GUARANTEED LEGENDARY+ IN 60 REROLLS” and “MYTHIC IN 180.” Those numbers are a dated observation, not a permanent promise. The current screen is the authority for your account and server.
Before relying on pity, answer four questions from the live UI: does the counter show remaining rolls or completed rolls, does any rarity reset it, is pity shared across faction changes, and do code-granted rerolls advance it? If the interface does not answer, spend conservatively until the behavior is confirmed.
Use a three-level stop rule
Immediate stop: the clan fits your intended route and you are still learning the game. A clear Rare passive can be more valuable than exhausting resources for a Mythical result you do not yet know how to use.
Conditional stop: the clan is useful but requires a playstyle you are willing to practice, such as parry follow-ups, sustained hit strings or party proximity. Keep it unless the remaining pity and resource cost make a planned upgrade reasonable.
Continue: the result has no documented buff and you have enough rerolls to continue without sacrificing progression, or the passive directly conflicts with your route. Even then, check the next pity threshold before pressing again.
Code rerolls
The public Codes card documents LUNARUPDATE with Clan, Breathing and Demon Art rerolls. Its live redemption status and exact counter changes need in-game testing. Redeem on the Codes hub route, then record each reroll pool before and after submission.
Do not spend the rewards immediately. Confirm that the correct counters increased and compare the current roster. A code reward is still limited if the code can only be used once per account.
Compare value, not rarity color
Ask how often a passive triggers in your real fights. A squad aura is weak when you always play solo. A player-kill passive is not a PvE farming answer. A low-health bonus can be dangerous for a new player. A simple skill-damage or first-hit defense effect may create more reliable value across the whole session.
Rarity is one input, not a complete ranking. Update-sensitive numbers and synergy assumptions make universal tier lists fragile. Keep the result that solves a repeated problem in your route.
Protect progression resources
Set a hard budget before rolling. Keep enough Yen or other currency for training, required activities and weapon progression. If the game uses separate paid products or Robux, read the purchase dialog and wipe status before spending. The current FAQ says a release wipe is likely but not confirmed with a date, so do not treat test progress as permanent.
Never give another player your account, cookie or authentication code for “lucky rolls.” Rerolling happens inside the official experience. A third-party tool cannot guarantee a clan and can compromise the account.
If you regret a reroll
Stop immediately and record the new result. Do not chase the previous clan with the rest of your balance. Re-evaluate the new passive, the current pity distance and the remaining route costs. If the result is workable, use it while rebuilding resources.
If a UI lag hides the result, wait for data to load or rejoin once before pressing again. Repeated clicks can consume multiple rolls. Capture the result and counter after each confirmed change.
A clean reroll record
For each roll, note timestamp, faction, previous clan, new clan, displayed rarity, pity before/after and resource spent. A short record reveals whether the counter behaves as expected and prevents false odds conclusions from memory.
Do not publish an odds percentage from a small personal sample. Current exact odds remain an in-game verification field. The useful decision is whether your next roll has a defined benefit and acceptable cost.
Sources and confidence
Roster roles come from the SLAYER public Trello. The observed 60-roll Legendary+ and 180-roll Mythic messages come from a dated public-test walkthrough and must be checked against the current live screen. Code reward wording comes from the Codes card; redemption and counter behavior need live testing.