Jump to content

[1.16.5] Disabling the weather-related darkening skies effect in a custom dimension


Recommended Posts

Posted (edited)

Hello everyone. I'm currently trying to prepare a very simple sandbox dimension, which will be used primarily for base building. But in the process of ironing out the bugs, I found one which has left me stumped

This dimension is set to be at noon always and to have no precipitation, as I wanted it to be an ever-sunny place. However, I've noticed that when it is raining in the overworld, the skies of this custom dimension will still change to an overcast sky, even though no actual rain will fall. By which I mean: the sun will vanish, the sky's colour will become much darker than usual, and the distance fog will become darker as well:

 

qx0MFV1.png

UVujlup.png

I've learned and tried a good deal of things by looking at the code over the past 2 days and have had some limited success in some areas, such as using a custom ISkyRenderHandler, which was enough to keep the sun from vanishing under these conditions. But quite frankly, I'm stumped as to what to do for the rest.

I understand where most of these changes come from, but see no good way to interfere with them as they are mostly related methods and values in the ClientWorld and World classes. I've tried the very hacky way of calling World#setRainLevels(0) on every draw, but this causes the sky to flicker heavily when weather conditions are changing to/from rain, as the skies will quickly change between its rainy colour and its clear sky colour until the transition is done.

Ultimately, the only real options which seem like they'd provide a real solution would be:

  1. I'd like for calls of World#GetRainLevel to always return 0 in this custom dimension; to my understanding, that alone would remove the need for literally any other change.
  2. Failing the above, I'd need to mess with a fair deal of methods which call World#GetRain; the ones in WorldRenderer are all easy enough to deal with, but those in ClientWorld and FogRenderer once again seem out of my reach.

----

With that in mind, is there any way to accomplish this? Did I make some mistake and failed to notice a good way to accomplish this ? Or is this a fool's errand and I should save my time and just give up?

Sorry for the long post, and thank you in advance for your time

Edited by Kirika

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
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.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I see. I'm sure I tried again with a lower case word, a few times. I ended up doing the same thing as pixxy in the end. Is this beyond the scope of the admins to fix? Are they already aware of it, or should I use 'contact us' to post a ticket?
    • I’m working on a Manta Ray entity in MCreator using GeckoLib animations, and my goal is to have a looping (flip) animation that ends at −360°, then transitions seamlessly into a swim animation starting at 0°. However, every method I’ve tried—like quickly interpolating the angle, inserting a brief keyframe at 0°, or using a micro “bridge” animation—still causes a visible “flash” https://imgur.com/a/5ucjUb9 or "jump" when the rotation resets. I want a perfectly smooth motion from the flip’s final rotation to the swim’s initial rotation. If anyone has solved this in MCreator/GeckoLib, or found a better trick for handling the −360° →0° gap without a snap, I’d appreciate some advice ! P.S.- I cannot set swim to start at -360 because I would have the same issue but in reverse. Here's the custom LoopingAnimationGoal :   class LoopingAnimationGoal extends Goal { private final MantaRayEntity entity; private final int cooldownTime; private int animationTimer; private int cooldownTimer; // New boolean to prevent double calls private boolean isLoopingActive = false; public LoopingAnimationGoal(MantaRayEntity entity, int cooldownTime) { this.entity = entity; this.cooldownTime = cooldownTime; this.animationTimer = 0; this.cooldownTimer = 0; this.setFlags(EnumSet.of(Flag.MOVE, Flag.LOOK)); } @Override public boolean canUse() { System.out.println("[DEBUG] LoopingGoal canUse => cooldownTimer=" + cooldownTimer); if (cooldownTimer > 0) { cooldownTimer--; return false; } BlockPos entityPos = entity.blockPosition(); boolean canUse = entity.isWaterAbove(entityPos, 4); System.out.println("[DEBUG] LoopingGoal canUse => WATER " + (canUse ? "DETECTED" : "NOT DETECTED") + " at " + entityPos + ", returning " + canUse); return canUse; } @Override public void start() { entity.setAnimation("looping"); animationTimer = 63; isLoopingActive = true; System.out.println("[DEBUG] Looping animation STARTED. Timer=" + animationTimer + ", gameTime=" + entity.level().getGameTime()); } @Override public boolean canContinueToUse() { System.out.println("[DEBUG] LoopingGoal canContinueToUse => animationTimer=" + animationTimer); return animationTimer > 0; } @Override public void tick() { animationTimer--; System.out.println("[DEBUG] LoopingGoal TICK => animationTimer=" + animationTimer); // We stop ONLY if we are still looping if (animationTimer <= 0 && isLoopingActive) { System.out.println("[DEBUG] condition => animationTimer <= 0 && isLoopingActive"); stop(); } } @Override public void stop() { // Check if already stopped if (!isLoopingActive) { System.out.println("[DEBUG] stop() called again, but isLoopingActive = false. Doing nothing."); return; } System.out.println("[DEBUG] Looping STOP at tick=" + entity.level().getGameTime() + ", last known rotation=" + entity.getXRot() + "/" + entity.getYRot() + ", animationTimer=" + animationTimer); // Immediately switch to "swim" entity.setAnimation("swim"); // Reset cooldown cooldownTimer = cooldownTime; // Disable looping to prevent a second stop isLoopingActive = false; System.out.println("[DEBUG] Looping STOP => setAnimation('swim'), cooldownTimer=" + cooldownTimer); } }  
    • So is the intention of the crusher for ores meant to be used with a silk touch pickaxe or something? Cause that seems like too much effort just to profit off of the machine, when everything drops as raw materials now. Am I just missing something? 
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.