Slayers 2 Patch Notes and Full Update History — 2026

What is the Slayers 2 update history so far?

Two balance patches are documented between launch on 2026-09-18 and 2026-09-23: v0.98 on 2026-09-21 and v0.110 on 2026-09-22. The three days in between and after produced no patch records at all. This table is the summary; each entry is expanded with its own confidence label below.

The launch date itself is well established, including the time. One source gives 16:00 EDT on 2026-09-18 with early access starting around 2026-09-11, and a video published at the time repeats the same two dates. Treat the early-access start as the weaker half of that pair, since it rests on one outlet plus a corroborating video description.

The gap in the middle of the table is the part worth internalising. Two days with no records and one day with a documented patch is not a quiet week; it is a week with no changelog. Read the “no record” rows as “nobody documented anything”, not as “nothing shipped”.

Why are all of these version numbers community sourced?

Because the developer does not publish a changelog. There is no patch-notes page on the Roblox listing, no developer blog, no Trello board and no public archive. Patch information is posted in the official Discord, which search engines cannot index, so nobody can link to the original announcement.

That has three consequences you can see in every third-party patch note, including this one. First, version numbers arrive as transcriptions, which is why the same patch is sometimes written as v0.98 and sometimes as v.09. Second, details arrive with inconsistent precision: one outlet will give exact frame values, another will describe the same change in words. Third, corrections are impossible, because there is no primary document to correct against.

The version numbers themselves are not the weak part, at least for v0.98. Four independent sources date that patch to 2026-09-21, including a video published that day with the version number in its title, two tier lists updated to the version, and a third-party meta page. When four sources with different incentives agree on a number and a date, the number and date are safe.

What is not safe is any individual line item. A detail reproduced by two outlets is meaningfully stronger than one that appears once, and this page marks the difference on every row rather than presenting the patch as a single confirmed document. That is the honest version of what a patch-notes page can be for this game in its first week. Our official links page explains why the Discord is the only first-party channel and what that means for verification.

To verify anything yourself, restart the game. Patches require a server restart to apply, so a client that has not reconnected is running the old build.

What did v0.98 change on 2026-09-21?

It was the larger of the two patches and it reshaped three Breathing Styles at once. Water gained a hard stun and approach invulnerability, Thunder lost the tools that made it dominant, and Flame and Wind both got faster startups. Temari and Arrow were adjusted on the demon art side as well.

Water Breathing

Water is the clearest winner of the patch and the reason several post-patch rankings moved it to the top of the list. The important detail is the strict stun on Whirl Pool combined with the ability to cast it while stunned: that is a defensive escape and an offensive opener in the same button. Our Water Breathing page covers the current form list if you want the practical version.

Thunder Breathing

Thunder was the patch’s loser, and the community reaction was immediate enough to leave a trail of videos with titles asking whether it had become the worst style in the game. The disputed startup row is the one to be careful with. Two sources agree on the direction and the value, a third describes the same skill moving the other way, and we have no way to break the tie from outside the game. Our Thunder Breathing page records both readings.

Flame Breathing

The Undulation change is the interesting one because it alters what the move is for. A counter that only answered basic attacks could be baited; one that answers skills turns every opponent ability into a risk.

Wind Breathing

Sound Breathing and Blood Demon Arts

The demon art changes are documented in less detail than the Breathing ones, but the ranking effect is visible: one outlet moved Arrow up to A tier and Tamari from C to B after the patch, describing the theme as targeting and tracking improvements. The full post-patch picture lives on the Blood Demon Arts tier list.

What did v0.110 change on 2026-09-22?

Four things: block regeneration was fixed, a PC indicator was added, Thunder was partially restored, and PvP gained a rematch button. A damage-over-time fix is the quiet fifth change. Every line below rests on one web source, so treat the whole patch as reported rather than confirmed.

The block fix is the headline because it is a bug fix rather than a balance decision. Block values that stopped regenerating during a stun made stun chains far more punishing than the designers appear to have intended, and removing the condition changes the value of every stun in the game.

The Thunder changes are a partial rollback of v0.98. Two skills got 20% faster cast times and longer stuns, which restores some of what Rice Spirit lost without returning the strict stun that was removed outright.

There is independent evidence that something shipped that day, even though nobody published it officially. A monitoring source recorded two game-place updates on 2026-09-22, at 14:05 UTC and 16:14 UTC, with no accompanying developer statement. That does not confirm the contents above, but it does confirm that the game was updated twice.

How to check whether you have it: patches need a server restart, so leave and rejoin. On PC, look for the block regeneration indicator in the bottom-left of the screen, and in PvP look for the rematch prompt when a match ends.

What happened to codes on 2026-09-22?

The code pool rotated. Three of the five documented codes changed status on that day: POINTSRESET was retired and replaced by SkillTreeReset, which performs the same skill-tree reset, and the two launch-day spin codes expired together, three days after release. Release26 stayed active.

The replacement code is the notable part, because it means the reset service never actually disappeared; only the string changed. Players who had POINTSRESET saved from a launch-day list found it dead, while the functionally identical SkillTreeReset was already live. The new code was added on 2026-09-21 according to one outlet, one day before the old one stopped working.

The two expired codes both paid spins, so their removal matters more than a typical rotation for anyone planning a reroll session. One of the two had a name implying a server shutdown, which suggests an outage happened around that period, but no matching patch note or announcement was found to go with it.

Current status for every code, including which ones have expired, is maintained on the Slayers 2 codes page. Nothing new was added on 2026-09-23.

Which days had no update at all?

Three days: 2026-09-19, 2026-09-20 and 2026-09-23. No version number, patch note or game update was found for any of them. One indirect clue survives for 2026-09-20, when Release26 was still reported as the only active code in the game, which at least tells us nothing had been retired yet.

The distinction between “no patch” and “no record” matters here. The developer patches without announcing, as the two unexplained game updates on 2026-09-22 demonstrate. A day with no patch notes could easily be a day with a silent fix, and a page that lists these days as confirmed quiet periods would be overstating what anyone knows.

What can be said with confidence is that no balance pass, no new content and no code change was documented on those three days by any of the outlets tracking the game. If something changed, it changed without leaving a trace in any indexed source.

For a game that launched on 2026-09-18 and had two balance patches in its first five days, that is a plausible rhythm rather than a suspicious gap. The first week of a Roblox launch is usually patch-heavy, and a two-day pause between hotfixes is normal.

How should you read version numbers like v0.98 and v0.110?

By date, never by the version number itself. Treated as decimals, 0.98 looks larger than 0.110, but v0.98 came first on 2026-09-21 and v0.110 came second on 2026-09-22. Read as separate segments, 110 sits above 98, and that ordering matches the release dates exactly, so sorting by date is always correct.

This is not a trivia point. A page that sorts these patches by version string will present the game’s history backwards, describing a block-regeneration fix as having happened before the Water buffs. The dates are unambiguous even though the numbering convention is not documented anywhere.

The convention appears to be a minor-version scheme where the middle segment increments, which is common in Roblox development but has never been stated by the developer. Whether v0.110 means the hundred-and-tenth build or something else entirely is unknown, and nothing about the game’s behaviour depends on the answer.

The practical advice is to record the date alongside any version number you save. If you are comparing two guides and one cites v0.98 while the other cites v0.110, the dates tell you which is more current. If a guide cites a version number without a date, it is not telling you anything you can order.

Which patch claims should you not trust?

Claims that carry precise numbers without a source, and claims that appear only on aggregator sites whose own pages contradict each other. One competitor’s update log has no version numbers and no dates anywhere on it, yet quotes specific values such as a Thunder dash increase and a Water hitstun frame change.

Those specific figures are the problem. They conflict with the sourced v0.98 values, they carry no attribution, and the same site published a second page contradicting its own patch coverage. A number that appears nowhere else and cannot be traced is worth less than no number, because it looks authoritative while being unverifiable.

Three categories are worth discounting outright:

• Unsourced percentages and frame values. If a page says a skill’s dash distance rose 15% and no other outlet repeats it, there is no reason to believe it.
• Version numbers with no date. After v0.98 and v0.110, a version string alone cannot tell you whether it is old or new.
• Confident chronology. Any page that presents these patches in version-number order is working from the string rather than the dates.

Rankings published in the same window need separate handling. Several outlets re-ranked Breathing Styles and demon arts after v0.98, and those rankings disagree with each other, especially on Wind and Insect, which swing between the top and bottom of different lists. That is opinion rather than fact, and it should be attributed to whichever outlet produced it. Our Breathing Styles tier list keeps the competing rankings side by side with their dates instead of merging them.

What is still unresolved in this update history?

Four things are genuinely open: whether the 2026-09-21 patch is called v0.98 or v.09, whether versions between v0.98 and v0.110 exist, what hour v0.98 landed, and whether v0.110 has a second source anywhere. None of these can be settled from outside the game.

The specific gaps, with what would resolve each:

• v.09 versus v0.98. Two pages write the September 21 patch as v.09 while every other source writes v0.98. It is probably a truncation of the same number, but a genuinely separate v0.9x patch cannot be ruled out.
• Any version between v0.98 and v0.110. Whether v0.99 through v0.109 exist is completely unknown. The two unexplained game updates on 2026-09-22 could be intermediate builds or could be v0.110 applied twice.
• The hour v0.98 shipped. Only the date is established. There is no way to tell whether a given player experienced the old or new Water on the evening of 2026-09-21.
• A second source for v0.110. Everything in that patch rests on one outlet. The independent evidence for two game updates that day is real, but it does not confirm any specific change.
• The Thunder startup direction. Two sources say one thing, a third says the opposite, and this is the only v0.98 line item where the sources disagree on direction rather than detail.
• God Speed’s exact form. A distance reduction from 80 to 50 and a reduction to normal running speed are not obviously the same change, and both descriptions are in circulation.

Given the pace of patching in the first week, most of these will be overtaken by events. The durable conclusion is structural: as long as the developer publishes only through Discord, every patch note in circulation, including this page, is a transcription. Treat version numbers and dates as reliable and individual line items as reported until a second source confirms them.

What is this page based on?

This page is built from Community Verified sources: AllThings.how, ProGameGuides, slayers2-game.wiki and slayers2wiki.com, cross-checked on 2026-09-23. The v0.98 version number and date are the strongest claims here, confirmed by four independent sources, while the v0.110 version number rests on a single outlet plus indirect evidence of two game updates that day.

Per-change confidence is marked on every row of the tables above. Cross-checked rows were reproduced by two or more outlets; single-source rows come from one; the Thunder startup row is the only one where sources disagree on direction. The demon progression and clan numbers used elsewhere on the site have separate evidence notes on their own pages.

The structural limitation is that no primary source exists. The developer posts patch notes in Discord, Discord is not indexed, and no outlet including this one can quote the original announcement. That is also why competitor patch pages tend to have no version numbers, no dates and no attribution, and why this page labels each row instead of presenting a single confident document. If you are reading this more than a few days after 2026-09-23, assume new patches have shipped that this page does not know about.