Regen

Regen accelerates the player's natural health regeneration beyond the vanilla rate. In vanilla, health regenerates slowly when hunger is above a threshold. Regen bypasses this rate limit by sending manipulated health packets or by triggering the server's regeneration logic more frequently.

Category
Player
Type
Health regeneration
Supported clients
Wurst, LiquidBounce, Aristois
Minecraft versions
All 1.21.x
Detection risk
High on protected servers
Last checked

What it does

Regen increases the frequency at which the client requests or applies health regeneration. Configurable options:

  • Regen rate — multiplier above the vanilla rate.
  • Health threshold — health value at which regen stops.
  • Mode — packet-based or tick-accelerated.

Client support

Client Status Notes
Wurst Yes Configurable regen rate
Meteor No Not provided as a standalone module
LiquidBounce Yes Multiple regen implementations
Aristois Yes Multi-version support

Server compatibility

  • HypixelRestricted. Server-side health validation blocks most regen modes.
  • 2b2tPermitted. No anti-cheat active.
  • CubeCraftRestricted. Sentinel validates health changes.

Detection behavior

Server-side health validation checks:

  • Health delta over time. The server knows the player's actual health and validates client-reported changes.
  • Hunger state. Vanilla regeneration depends on hunger level; regen that ignores hunger is flagged.
  • Damage timing. Rapid health recovery after taking damage is unusual.

Regen at 2–3× the vanilla rate is detectable on most servers. Higher multipliers are caught immediately.

Known limitations

  • Server-side health validation rejects most Regen modes on protected servers.
  • Regen does not restore hunger; it only affects health.
  • Combined with AutoSoup, Regen can create an obvious health-recovery signature.

Related modules

Browse Supporting Clients

Every client page includes version compatibility, module support, and verification data.

Browse Clients