Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

[Solved] [1.17.1] Rendering: GUI Elements and Fog


Recommended Posts

I have two semi-related problems, both involving rendering.

For the first situation I want to hide the air bubbles/breath bar when a particular piece of armor is worn. Previously I used 

RenderGameOverlayEvent.Pre event

and canceled the event if the element type was 


which no longer exists in 1.17 it seems, and now I'm not sure how to recreate this functionality with the new system.

For the second, I want to disable the under-lava-view fog when a particular piece of armor is worn. Previously I used 

EntityViewRenderEvent.FogDensity event



to achieve the desired result.

To be honest with you I don't remember how I came up with that solution anymore, only that fogStart and fogEnd became deprecated at some point before 1.16.5 (as I found out when finally updating my mod yesterday), and are completely removed now. For 1.17 I tried replacing those with 


which has no effect, unless I'm missing something else for that to work. Not sure how to get the same effect here.

Edited by Rohzek

Developing the Spiral Power Mod .


Link to comment
Share on other sites

7 hours ago, Rohzek said:

and now I'm not sure how to recreate this functionality with the new system.

RenderGameOverlayEvent.PreLayer will fire for all overlay elements. You can check if it is the air level by comparing the overlay element to ForgeIngameGui.AIR_LEVEL_ELEMENT.

7 hours ago, Rohzek said:

For the second, I want to disable the under-lava-view fog when a particular piece of armor is worn.

You can either use EntityViewRenderEvent.FogDensity, which will set setShaderFogStart and setShaderFogEnd for you based on the density you set on the event (provided you cancelled the event) or you can use EntityViewRenderEvent.RenderFogEvent (only called if FogDensity is not cancelled) and do your own fog settings there (by manually setting setShaderFogStart and setShaderFogEnd for example). You can see where this happens in FogRenderer#setupFog.

  • Like 1
Link to comment
Share on other sites

  • Rohzek changed the title to [Solved] [1.17.1] Rendering: GUI Elements and Fog
  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing

    No registered users viewing this page.

  • Posts

    • show the code your use for this is the Event called?, use debugger to check the values in the condition
    • if you add your Biome to the Overworld via BiomeManager#addAdditionalOverworldBiomes, you need to register your Biome via DeferredRegister or RegistryEvent unfortunately a json only Biome does not work in this case
    • use debugger to check the conditions you are using before you render your Entity
    • yes, and then post the correct logs
    • Good Morning, I tried overriding one of the vanilla rock blocks according to instructions in this old thread, but failed for the same reason the org TM did, even though I got a tiny bit farther than he did. I can remove the original block entirely from world spawn, and replace it with custom version, which I want to prevent due to following up workload(adapting recipes etc. to custom block). What I tried solving the issue/actually making replacing(partially) work: 1. I had to use the original Forge variant of registering the block in main class, like that: which actually did use the custom granite block as replacer(not exactly illustrated in the old thread), but didn't consider it on world feature generation... 2. I then believed it was due to not using correct path variables for assets texture/models/blockstates etc., so I created missing asset packets for both, vanilla asset path, and my mod path. This also did not fix the issue with creating holes filled up with Items.AIR on world feature generation. 3. I then tried to remove the vanilla granite block during feature generation, and reimported it after with my replacement set up, during feature generation as well(according to @Luis_ST advice). But the holes were still there, only this time I got my replaced granite block spawned as well. What do I want to achieve(asking myself and you in hope maybe there's a better solution)? Mojang found it a good idea, to give one of the hardest rock materials on this planet, the .harvestLevel(soft as a pillow), so I can harvest it with a wooden pickaxes(which technically is even worth, but doesn't matter since wooden "pickaxe" tools do not exist in my mod). I really just want to compare harvestLevel of any of my tools, against the harvestLevel of the targetBlock, so I can automatically disallow harvesting it, if the tool doesn't match the harvestLevel(which for whatever reason does not work as intended in 1.16.5 Minecraft). Edit: and before you shout "doPlayerHarvestCheck". Yes, I do that! Edit2: Also, why are there Manga Comic Girls, on the right upper corner of my Monitor, stating how can it be that big?(whatever "it" is?)
  • Topics

  • Who's Online (See full list)

  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.