Do not call a bonus a multiplier until the numbers prove it
No public description currently confirms INFs ADMINS in SAE income multipliers, their names, percentages, prices, stacking rules, or persistence. The official cover confirms a Most $/s rate display, which gives you a clean value to test. Use that display to measure one change at a time instead of treating every increase as a multiplier.
A cash reward, a producer upgrade, and a true rate multiplier can all make progress feel faster. They are not the same system. Your goal is to identify what changed: the stored balance, the base rate, a displayed bonus, or the final $ / s result.
Status checked September 14, 2026. This page is a live test method. It does not claim that any multiplier purchase or bonus is available in the current build.
Start with a clean baseline
Before activating anything that looks like a bonus, record:
- current cash;
- displayed
$ / s; - every visible bonus label or icon;
- server type and player count;
- whether the account has just joined, respawned, or completed an action;
- the exact time of the capture.
Wait through at least two visible cash updates without interacting. If the rate changes on its own, the baseline is not stable. Find the cause or begin again later.
Do not use the large values shown in the promotional cover as your baseline. $1T/s, $249B/s, and $99B/s are examples in the artwork, not documented account states.
Apply one-change multiplier testing
Use the loop baseline, activate, measure, remove, recheck.
- Baseline: record cash and
$ / sbefore the action. - Activate: use one clearly labeled bonus, if the live game presents one.
- Measure: record the immediate rate and the rate after a fixed interval.
- Remove: let a temporary effect expire or disable it only through a normal interface option.
- Recheck: confirm whether the value returns to baseline.
If there is no clearly labeled bonus in the live interface, stop. Do not test random buttons and assign them multiplier names.
| Result | Safe interpretation | Next check |
|---|---|---|
| Cash jumps, rate stays fixed | One-time cash change | Repeat without spending |
| Rate rises by a fixed amount | Additive rate change is one possibility | Test at a second baseline |
| Rate scales with the baseline | Multiplication is one possibility | Repeat with a different base rate |
| Icon appears, numbers do not move | Effect is not reflected in the tested display | Check label details and duration |
| Rate remains after the icon ends | Another upgrade or delayed refresh is involved | Rejoin and compare |
Two measurements can fit more than one formula. Use a second baseline before deciding how the bonus combines.
Tell additive and multiplicative changes apart
Assume a visible bonus can be safely activated twice at two different starting rates. Record the increase each time.
- If the increase stays the same while the base rate changes, the effect behaves like a fixed addition in those tests.
- If the increase grows in proportion to the base rate, the effect behaves like a multiplier in those tests.
- If neither pattern repeats, another variable, cap, rounding rule, or timing effect is involved.
Do not publish a percentage from a compact suffix alone. A label such as 1T/s can hide lower digits. Use an expanded stat view if one exists, or test at a smaller value where the display exposes enough precision.
Test stacking without wasting progress
Stacking needs three controlled states:
| State | Active effects | Value to record |
|---|---|---|
| A | No tested bonus | Baseline $ / s |
| B | Bonus one only | Rate, icon, timer |
| C | Bonus one plus bonus two | Rate, icons, timers |
Compare State C with both A and B. If two effects share a timer or one replaces the other, record that interface behavior before calculating anything. If the second action costs premium currency or valuable progress, do not purchase it solely for a test. Wait for a normal play opportunity or a clearly reversible option.
Do not assume “2x plus 2x equals 4x.” A game can add percentages, multiply them, keep the strongest effect, or cap the final rate. The before-and-after display is what separates those rules here.
Check caps, duration, and persistence separately
One session can answer duration; it cannot settle persistence. Use separate checks:
- Record the activation time and any visible timer.
- Watch whether the rate returns to baseline when the timer ends.
- If death is safe, record the value before and after a normal respawn.
- Record the value, leave normally, and rejoin once.
- Compare a public server with another server only after saving the first result.
Do not perform destructive resets or spend rare items for these checks. If the game warns that an action clears progress, cancel it.
Common multiplier testing errors
Changing the base rate during a test hides the result. A purchase can cover up the effect you are trying to measure.
A cash increase is not automatically “2x income.” A one-time payout does not establish a rate bonus.
Rounded suffixes are not exact numbers. Hidden digits can distort the calculated percentage.
Several effects at once make the result unreadable. Test one effect before testing a stack.
An admin-labeled action is not automatically permanent. Record death and rejoin behavior separately.
FAQ
Are income multipliers confirmed in INFs ADMINS in SAE?
No exact multiplier system is documented in the accepted public information. Check the live interface for a named bonus before testing it.
How do I calculate a multiplier?
Divide the tested final rate by the stable baseline rate, using expanded values rather than rounded suffixes whenever possible.
How can I tell whether bonuses stack?
Compare a baseline, each bonus alone, and both bonuses together without changing anything else.
Do income bonuses survive death or rejoining?
That behavior is not documented. Capture the rate before and after a normal respawn and a separate rejoin.
Can admin controls change the multiplier?
No exact admin effect is confirmed. Only connect an admin action to income after one controlled before-and-after test shows the change.