Main / Health detections
Anti health regeneration
health.regenserverDefault: logThe player's health went up fast without a heal.
How ByteAC finds it
The server compares health between samples. A gain above the regeneration amount within the window, while alive and not right after a revive or heal, is checked again 1.1 s later.
Measured by the server. The player cannot fake or block it.
What the numbers mean
These are the values shown under the detection in the Threat feed and on the player page.
- from
- Health before.
- to
- Health after (200 = full on most servers).
Can also be caused by
Heal items, medics, revive scripts that do not tell ByteAC. Set the revive event name or call exports.ByteAC:Allow(src, "heal", 5).
What to do
Log.
The action (Off, Log, Kick, Ban) is set per detection on the Protection page. It only applies when Enforcement is on Custom. See Actions, modes & numbers.
Related settings
- Max healthdefault 200
- -
- Max armordefault 100
- -
- Revive event name (client)default
- Health jumps right after this event are not flagged.
- Regeneration amountdefault 40 HP
- Health gained within the window below before anti health regeneration flags. Raise it if players get healed on kill or respawn.
- Regeneration windowdefault 3 s
- -
- Godmode minimum hit damagedefault 10
- Only hits at least this strong are checked by anti invincibility.
- Godmode check delaydefault 2 s
- How long after a hit health must still be unchanged. Lower it if scripts refill health shortly after hits.
- Damage immunity gracedefault 1 s
- Immunity must stay on this long in a row before anti damage immunity flags. Raise it if scripts give spawn protection or safe-zone immunity.