No Clouds

Use this checklist when the volumetric clouds do not show, show for some players only, or show next to the vanilla clouds. Stop at the first check that fails. The clouds need neither MythicMobs nor MS_Atmosphere.

Checklist

1. The server version

The cloud layer needs Minecraft 1.21.11 or newer and a server build that can draw it. Otherwise the console prints one of these at start:

• Atmosphere clouds need Minecraft 1.21.11 or newer; cloud layer disabled.
• Atmosphere cloud rendering is unavailable on this server build; cloud layer disabled.

2. Both switches, and a restart

enabled at the top of atmosphere.yml and clouds.enabled must be true, and clouds.enabled needs a restart. Read the Clouds: line of /ms atmosphere info:

After clouds.enabled: false and a reload, info reads Clouds: off, but the layer keeps drawing until the restart.

3. The world is switched on

/ms atmosphere info must show a line with regions for your world (Worlds: none means no world is on). If not, run /ms atmosphere toggle <world>, which prints Atmosphere in <world>: on. Only overworld-type worlds can be switched on. See No Rain.

4. The player's cloud quality is not off

Ask the player to run /cloudquality.

• Good: Cloud quality: <preset>, change with /cloudquality <off/low/medium/high>, with a preset other than off.
• Bad: off. Run /cloudquality high, which prints Cloud quality: high.
• Bad: the player is in a WorldGuard region with season-clouds set to deny, which works like off there. See Land Claims.

Players who never chose get clouds.quality.default (high as shipped), see Cloud Quality.

5. A layer is loaded

Run /ms atmosphere profile <world>. Layers come from clouds.layers ([cumulus] as shipped), one file in cloud-layers/ per name.

• Good: Layer cumulus (solid) for each layer, or Layer <id> (see-through <opacity>) for an opacity below 1.
• Bad: Cloud layers: none. The list is empty or none of its layers loaded. A clouds.layers: [] in a world block, a season file or a profile removes every layer, and the last place that sets the list wins.

The console says why a layer did not load:

Players can hide a layer that has a toggle name with /togglecloudlayer, see Player toggles.

6. There is cloud to draw

Run /ms atmosphere stats under the sky you expect and read the Clouds: line.

• Clouds: none (simulated none): no simulated cloud here, and the shipped cumulus layer draws only simulated cloud. Walk to other weather, or wait.
• Clouds: none (simulated y<a> to y<b>): the layer's forms-at, full-at, coverage and ground-clearance keep it from drawing that cloud, see Layer Options.
• Rain with no cloud drawn above you: rain follows the first solid layer (opacity 1), or the simulated cloud when the list has no solid layer.

7. The view, and the build time

Read the Renderer: line of /ms atmosphere stats (it arrives a moment after the rest). Quads are cloud faces, built in tiles of 256 by 256 blocks.

• spawned <a>/<b> quads: <b> faces lie in the tiles in your view and <a> exist for you. spawned 0/0 quads means none are in view.
• (tiles still meshing) or (gen swap pending, lag <n>): the clouds are still being built and fill in over the next seconds.
• no cloud view yet: the cloud layer has not processed you yet. It starts about three seconds after the simulation.
• Clouds are drawn only inside a cone around the view direction, the fov-cull-angle of the player's preset (110 degrees as shipped). In third-person front view (F5 twice), clouds ahead of the camera may drop out.

See The Renderer line.

8. Terrain hides the faces

With clouds.occlusion-culling on, faces that blocks hide from the player's eye are skipped. The Renderer: line counts them as (<n> occlusion-hidden, <m> by terrain).

• That is expected in a cave, a closed building or a deep valley.
• Blocks removed by a command, WorldEdit or a plugin that changes blocks without an event are noticed within 10 seconds, and only in the chunks around each player.
• While a player moves 10 blocks per second or faster, for example when flying, terrain hides nothing and by terrain is left out.
• To test, set clouds.occlusion-culling to false and run /ms reload. Faces behind other clouds are then drawn too.

9. The resource pack

Clouds beyond a client's render distance fade into its fog. To remove the fade, set clouds.shader-pack.enabled to true, deliver plugins/MythicSeasons/MythicSeasons-CloudFog.zip to your players and check what they receive. The plugin writes the file only while the master enabled switch is on, and never sends it. See Shader Pack.

10. The vanilla clouds still show

They still show next to the new clouds:

• In a world without a season.
• Where a land plugin turns season effects off.
• For a player who ran /toggleseasoncolors, in chunks sent after that.
• In every world while modify-biome-on-client is false.
• In a biome that no biome file covers.
• After you turned clouds.enabled on without a restart.

See Biome Colors.

11. Errors in the console

• cloud tick failed for <player>: <error> and cloud tick failed for world <world>: <error> are cloud layer errors.
• /ms atmosphere dumpclouds writes your cloud view to plugins/MythicSeasons/debug and prints Cloud view written to <path>, or No cloud view to dump (are clouds running and visible?). Attach the file to a report.