mojira.dev
MCPE-157298

Health and hunger bars showing in Creative Mode

Whenever I go into Creative Mode the health and hunger bars still show and it makes it difficult to tell if I'm in Creative Mode.

Linked issues

MCPE-157439 I can see HP in creative mode Resolved MCPE-157822 Non-functioning hunger and health bar occasionally appear on the screen when joining a Creative world Resolved MCPE-158384 The health and hunger bars stay even if switched in to creative mode Resolved MCPE-158667 Error With Gamemode UI Resolved MCPE-159986 Hearts and hunger bar in creative. Resolved

Attachments

Comments 11

Do you have any resource packs enabled? If so, does disabling them fix the issue?

I do have resource packs enabled, but I don't think it's because of that.

Can confirm. to explain, this started on 1.19.0 betas, and when changing something in the ui/hud_screen.json file, the healt and hunger bar appear when on creative mode for an unknown reason.

Does this occur when using the Spectator experimental mode? Any additional information that you might have would be useful.

Also, please make sure that you have removed/disabled any resource packs, to make sure they are not the issue. Otherwise, we may not be able to track the bug here.

Alright, I don't know if this is the only cause of this bug, but at least this is what happened to me.

For further explanation, pre-1.19.0 hud_screen.json files have a "binding name" for heart, hunger, and XP bars renderers which makes them invisible when changing to creative mode. However, in 1.19.0+, the code for the binding name has been changed, and when a resource pack that contains a pre-1.19.0 hud_screen.json file is enabled, the heart, hunger and XP bars are shown when on creative or spectator modes because the binding name seems to not accept the old version on the renderers of the hud_screen.json file.

pre-1.19.0 hud_screen.json file code for heart renderer:

"heart_renderer": {
    "type": "custom",
    "size": [ 1, 1 ],
    "renderer": "heart_renderer",
    "layer": 1,
    "bindings": [
      {
        "binding_name": "#is_not_creative_mode",

1.19.0+ hud_screen.json file code for heart renderer:

"heart_renderer": {
    "type": "custom",
    "size": [ 1, 1 ],
    "renderer": "heart_renderer",
    "layer": 1,
    "bindings": [
      {
        "binding_name": "#show_survival_ui",

The binding name has been changed from "#is_not_creative_mode" to "#show_survival_ui" in 1.19, and this is, at least for me, the reason this bug started to happen.

Some duplicates from this issue, like MCPE-160095, has a resource pack that seems to change the HUD screen when enabled; And that case goes into the case i mentioned above, where the hud_screen file is outdated.

To workaround this, simply change the outdated binding name with the new one from 1.19+, for the XP, hunger, and heart renderers.

1 more comments

I accidentally made a duplicate report and was sent here. The exact same thing is happening to me on iOS 15.6.1!

I personally might make myself a pack to change the hud_screen.JSON file to the old binding until this is patched, but I will NOT be uploading this pack anywhere. I am a beginner to pack making, however after a small bit of work with .JSON, I believe you just have to make a .JSON file with the correct formatting and the old binding key. I’m glad I’m not alone in having this bug.

Now in 1.19.40 there is another issue with outdated UI files: If your resource pack has an pre-1.19.40 ui_common.json file, it will probably trigger MCPE-162063 as per MCPE-163774 and MCPE-163820.

This issue has been happening since before the experimental Spectator mode and it was because of the resource packs, but I don't know which one was causing it.

I created a new world with the resource packs disabled and the hunger and health bars vanish properly in Creative mode.

Resolving as Invalid as this issue is caused by outdated resource packs.

Jake Thorson

(Unassigned)

818375

Community Consensus

Multiple

1.19.0, 1.19.2 Hotfix, 1.19.30.20 Preview, 1.19.11 Hotfix, 1.19.20, 1.19.21 Hotfix, 1.19.31 Hotfix, 1.19.50, 1.20.41 Hotfix

Retrieved