Once Human SN700 Finale Nerf and Reverb Guide

The SN700 Finale adjustment in Once Human Version 3.0.2 is easy to describe and easy to misunderstand. Reverb now reaches a maximum of 4 stacks instead of 5, while the damage bonus at each stack increases from 4% to 5%. Players who only compare the old theoretical maximum with the new theoretical maximum may call it a buff or a nerf too quickly.

At the top of the stack table, the old version provided 20% total bonus at 5 stacks. The new version provides 20% total bonus at 4 stacks. That means the maximum listed bonus is equal. The change is therefore not primarily about the final ceiling. It is about how quickly the weapon reaches that ceiling, how long it stays there, and how much value is lost when a fight interrupts the stacking cycle.

This matters because real encounters are not stationary spreadsheets. Targets move, phases end, reloads happen, players dodge, and objectives force the team to stop attacking. The new SN700 can feel better in one encounter and worse in another without either result being contradictory.

The Number Change in Plain Terms

Reverb state	Previous bonus	New bonus	Practical question
1 stack	4%	5%	How quickly does the first bonus matter?
2 stacks	8%	10%	Does the rotation reach this before movement?
3 stacks	12%	15%	Is the target still vulnerable?
4 stacks	16%	20%	How much of the fight is spent here?
5 stacks	20%	Not available	Did the old rotation require a fifth stack?

The most obvious gain is that the first four stacks now give more damage than before. The most obvious loss is that the fifth stack no longer exists. If an encounter ends shortly after the fourth stack, the new version may be more efficient. If the old weapon stayed at five stacks for a long uninterrupted phase, the new version does not offer a higher maximum to compensate for the missing layer.

This is why a final screenshot of the damage number is not enough. You need to measure the path to the number.

What Counts as a Real Nerf

A change is a practical nerf when it reduces the weapon's performance in the content you actually play, even if one part of the theoretical table looks equal. The most likely loss appears in fights where the fifth stack was maintained for a long time and where the player's rotation did not suffer from frequent interruptions.

A change can also be a practical buff when the first four stacks are reached faster and the encounter repeatedly resets before the old fifth stack would have become reliable. Short elite fights, moving targets, and mechanics with frequent invulnerability windows can favor earlier value.

For a mixed account, the correct answer may be “sidegrade.” The SN700 can remain strong while requiring a different rotation or a different attachment priority. Do not use the words buff and nerf as a substitute for testing.

The Rotation Question

Start by writing the old rotation in simple actions: fire, reload, activate an effect, reposition, fire again. Mark when each Reverb stack appears and when the target stops being vulnerable. Then rewrite the same sequence with the 4-stack ceiling.

The goal is to discover wasted actions. If the old rotation included one extra action solely to reach the fifth stack, the new version may be cleaner. If the old rotation naturally reached five stacks and stayed there during a boss phase, the new version may have less sustained value.

Do not force the rotation to reach maximum stacks if the target is about to move. A 3-stack attack with a 15% bonus can be better than a delayed 4-stack attack that misses the vulnerability window. The new numbers reward earlier action, but only when the player recognizes the encounter timing.

Reload timing deserves separate attention. If a reload resets, pauses, or delays stacking, the value of the fourth stack depends on whether the magazine cycle allows it to remain active. Record the time from the first shot to the first maximum stack, then compare that time with the target's movement pattern.

A Three-Test Method

Test One: Stationary Target

Use a stable target to measure the clean theoretical cycle. Record the time to reach 1, 2, 3, and 4 stacks, the damage at each state, and the time spent at maximum. Repeat the test so a critical hit or random effect does not decide your conclusion.

This test tells you whether the weapon has become easier to ramp. It does not tell you how the weapon performs in a real encounter.

Test Two: Mobile Elite

Use an enemy that moves, attacks, or changes position. Do not stop the test every time you miss a shot. Record how many stacks survive the movement and whether the higher early bonus makes the lost fifth stack irrelevant.

This test represents the content where uptime matters more than the final theoretical ceiling. It can reveal whether the new cap gives you useful damage before the enemy leaves range.

Test Three: Long Encounter

Use a longer fight with a predictable phase. Measure the first rotation, the sustained middle section, and the time after a forced interruption. The old weapon's fifth stack may have been valuable here, but the new version may recover faster after the interruption.

Compare total damage over the full encounter, not the highest single hit.

Attachment and Build Consequences

Do not change every attachment at once. Start with the part that influences the stacking cycle, reload, accuracy, or uptime. If you change damage, rate of fire, reload, and critical effects simultaneously, you will not know which adjustment helped.

A faster stacking build may benefit more from early Reverb value than a slow build designed to hold maximum stacks. A high-accuracy setup can make the 4-stack ceiling more reliable against moving targets. A build that relies on long stationary phases may need a different comparison.

The right attachment depends on your content. For a player farming ordinary enemies, time to first useful bonus may matter more than maximum sustained output. For a raid group, the team may create a long vulnerability window where sustained damage is more important.

Keep one familiar loadout unchanged as a control. Test the modified version beside it and compare the same target under the same conditions.

Encounter-by-Encounter Expectations

In short fights, the new 5% per stack can be valuable because the battle may end before the old fifth stack appears. Do not overinvest in a long setup if ordinary enemies die quickly.

Against mobile elites, earlier bonus value can compensate for movement, but only if shots remain accurate. A higher percentage on paper does not help when the weapon loses uptime.

In long boss phases, the missing fifth stack can matter if the old weapon reached and maintained it naturally. Watch for forced transitions, reload windows, and mechanics that reset the stack.

In group content, a teammate's crowd control can change the result. The SN700 may perform better when another player keeps targets in place, so solo tests and group tests should not be treated as identical.

When to Replace the Weapon

Replace or bench the SN700 only after it fails a practical comparison against an available alternative. The fact that one mechanic changed is not enough. Ask whether the weapon still completes the content, preserves ammunition, and fits the team's role.

A weapon that loses a few seconds of sustained damage but remains reliable may still be better than an alternative that requires expensive materials or difficult positioning. Conversely, if the new cap causes repeated phase failures, the weapon may no longer match your account's priority.

Do not dismantle it while the patch is new. Keep the old setup stored, label it clearly, and revisit the comparison after more players have tested different rotations.

A One-Week Testing Plan

Day one should be a baseline. Test the current build without changes and record the rotation.

Day two should measure the four-stack cycle on a stationary target.

Day three should test a mobile elite and record lost uptime.

Day four should compare one attachment change.

Day five should run the weapon in your most important live activity.

Day six should compare the total result with an alternative weapon.

Day seven should decide whether to keep, modify, or replace the build. This schedule prevents an emotional first-day reaction from becoming a costly rebuild.

Topuplist and Build Spending

A balance change can create pressure to buy materials, premium currency, or replacement options. If you decide to purchase supported Once Human services, review the Topuplist official website and the Once Human top-up page. Confirm the account, server or region, package, and final price before payment.

Do not spend simply because a patch note contains the word “adjustment.” Test the weapon first and separate a real account need from the excitement of a new number.

Common Testing Errors

The first error is comparing only maximum bonus. The second is testing only a stationary target. The third is changing every attachment at once. The fourth is ignoring reload time. The fifth is judging a team weapon in a solo test. The sixth is dismantling the weapon before the meta settles. The seventh is copying a community rotation without matching its gear or encounter.

The best testing notes are simple: target, team, attachment, time to maximum, total damage, interruptions, and result. You do not need a laboratory to make a better decision; you need a repeatable comparison.

Reading Community Test Results

Community testing becomes useful when the conditions are visible. A damage chart should identify the target, difficulty, weapon investment, attachments, buffs, team effects, critical rate, and measurement period. Without those details, a larger number may come from a different setup rather than from a better SN700 rotation.

Prefer repeated full-encounter results over a single perfect clip. One critical sequence can exaggerate the value of either version. Look for several runs, average performance, ammunition use, and the time lost to movement or reloads.

Check the publication date and patch version. A test recorded before 3.0.2 cannot describe the revised four-stack behavior. A hotfix after the main update can also change the result.

Use community data to choose what to test on your own account, not to skip testing. Server rules, gear quality, latency, and team composition can make an accurate public result unsuitable for your situation.

Final Takeaway

SN700 Finale is not defined by one number. The 3.0.2 adjustment removes the fifth Reverb stack and increases each remaining stack from 4% to 5%, leaving the listed maximum bonus at 20%. The real change is the path to that bonus and the value of sustained uptime.

Test the first four stacks, compare short and long encounters, keep one control build, and delay dismantling or heavy spending. If the new cycle reaches useful damage earlier, the weapon may remain excellent. If your main content depended on holding five stacks for a long phase, an alternative may now deserve more attention.

Measure what your account actually does, not what a single screenshot suggests.

FAQ

Is the SN700 Finale change a buff or a nerf?

It can be either depending on the encounter. The maximum listed bonus remains 20%, but the weapon reaches it through 4 stacks instead of 5, changing ramp time and sustained uptime.

What is the new Reverb maximum?

The new maximum is 4 stacks, with a 5% damage bonus per stack.

What was the old Reverb maximum?

The previous maximum was 5 stacks, with a 4% damage bonus per stack.

Should I dismantle SN700 Finale?

No. Test it against your actual content and keep a control loadout before making an irreversible decision.

Is the new weapon better for moving enemies?

It may provide useful damage earlier, but accuracy and uptime still matter. A higher early bonus cannot help if shots miss or the target leaves range.