Skip to content

fix(AutoLog): disable health and predicted-damage disconnects when health is set to 0 - #6727

Merged
MineGame159 merged 2 commits into
MeteorDevelopment:masterfrom
Eccys:fix/autolog-zero-health-disable
Oct 17, 2026
Merged

MineGame159 merged 2 commits into
MeteorDevelopment:masterfrom
Eccys:fix/autolog-zero-health-disable

Conversation

@Eccys

@Eccys Eccys commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

Type of change

  • Bug fix
  • New feature

Description

The health setting in AutoLog specifies "Set to 0 to disable." However, when health was set to 0 and predict-incoming-damage (smart) was enabled, onTick still evaluated playerHealth + mc.player.getAbsorptionAmount() - PlayerUtils.possibleHealthReductions() < 0, disconnecting the player with "Health was going to be lower than 0." whenever potential incoming damage exceeded current health + absorption (even while holding a Totem of Undying and using AutoLog only for totem pops or entity counts).

Guarded the health and smart disconnect checks with if (health.get() > 0), hid smart and smartToggle when health is 0, and made smart respect smartToggle on low-health disconnects.

Related issues

Fixes #5981

How Has This Been Tested?

Verified compilation against Minecraft 26.2 (./gradlew compileJava) and tested AutoLog with health set to 0 and > 0.

Checklist:

  • My code follows the style guidelines of this project.
  • I have added comments to my code in more complex areas.
  • I have tested the code in both development and production environments.

@MineGame159
MineGame159 merged commit ab3c086 into MeteorDevelopment:master Oct 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Auto log health based logging doesn't disable properly when disabled

2 participants