Wikis / MythicSeasons / Clouds / Shader Pack

Shader Pack

The cloud fog pack is a resource pack that MythicSeasons writes to plugins/MythicSeasons/. It stops far clouds from fading into each player's fog and carries the shader looks of cloud styles. Terrain, sky and particles keep the vanilla fog. It is not the MythicMobs skill pack (Packs).

Settings

These go under clouds.shader-pack in atmosphere.yml only. A typo there is ignored without a message.

Option Default What it does
enabled true Writes the pack at startup and on /ms reload, while the master enabled is on.
name MythicSeasons-CloudFog File name without .zip. Only letters, digits, ., _ and - are kept, and an empty result uses the default.
fog-start -1 Distance in blocks where fog starts on the clouds. -1 keeps each client's own fog.
fog-end -1 Distance in blocks where that fog is full.
served auto Whether your players get the current pack, see Checking that players have the pack.
post-effects false Gives players on Minecraft 26.3 and newer the post look of styles, see Post effects.
  • Set fog-start and fog-end both or neither, with fog-start below fog-end. They also fog other text in the world, such as other plugins' text displays.
  • Do not edit the file, the plugin rewrites it.

Turning it on

  1. Leave clouds.shader-pack.enabled (on by default) and the master enabled on.
  2. Start the server or run /ms reload. When the pack's content changed, the console prints clouds.shader-pack: wrote <path> (... sha1 <hash>), or clouds.shader-pack: could not write <path>: <reason> when the write fails.
  3. Deliver plugins/MythicSeasons/MythicSeasons-CloudFog.zip to your players, see below.

/ms atmosphere info shows the state on its Fog pack line.

Delivering the pack

The plugin never sends or hosts the pack.

  • As the server resource pack: upload the zip with the SHA-1 from the wrote line. Upload it again with the new hash whenever the plugin writes a new file (new name, fog numbers or style, a plugin update).
  • Merged into your own pack: copy the mythicseasons_* overlay folders and their entries in the overlays list of pack.mcmeta (same directory, min_format, max_format and order), and copy assets/mythicseasons at the root as it is.
  • On Minecraft 26.2 and 26.3, if any overlay entry starts at pack format 64 or lower, every entry needs a formats range (ours have one), otherwise none may have one. One entry that breaks the rule makes the client reject the pack's metadata, and a 26.3 client then loads none of the server's packs. Add formats to your own entries, or leave out mythicseasons_1_21, mythicseasons_1_21_2 and mythicseasons_1_21_6 and remove formats everywhere (1.21 to 1.21.8 then get no fog fix).

Which clients it covers

Overlay folder Pack formats Minecraft Fog with -1
mythicseasons_1_21 34 1.21 to 1.21.1 None on clouds
mythicseasons_1_21_2 42 to 55 1.21.2 to 1.21.5 None on clouds
mythicseasons_1_21_6 63 to 64 1.21.6 to 1.21.8 The client's own
mythicseasons_1_21_9 69 to 84 1.21.9 to 26.1.2 The client's own
mythicseasons_26_2 88 to 100 26.2 The client's own
mythicseasons_26_3 97 to 100 26.3 The client's own

Clients outside these ranges get the normal fog.

Checking the pack your players receive

Check the zip your players download:

  1. pack.mcmeta lists every mythicseasons_* folder the pack holds, with the formats from the table. A merging tool may leave out folders outside its formats (Nexo with Pack.generation.skip_unsupported_overlays: true), which is fine.
  2. Each folder's shader files under assets/minecraft/shaders/core/ are identical to those in our zip.
  3. No other text.fsh, rendertype_text.fsh or rendertype_text_intensity.fsh covers the same formats, since only one of them can apply.
  4. assets/mythicseasons/font/cloud_0.json to cloud_15.json and their textures are there, with our provider still first if a tool rewrote the font files.
  5. In game, clouds far beyond your render distance do not fade into the fog.

Checking that players have the pack

The plugin sends shader looks only while it judges that your players get the pack version that holds them, and only to players whose client reports a loaded pack.

served Shader looks are sent when
auto with Nexo Nexo's generated pack holds our fonts, textures and identical shader files. Rechecked when that file changes.
auto without Nexo Never. The console says to set served: true once you deliver the pack yourself.
true Always. You deliver the pack.
false Never.

The status shows on the Fog pack line of /ms atmosphere info and in the console as Cloud shader looks: <status>.

The check reads the pack file on disk. With Nexo's Pack.dispatch.send_on_reload: false, players online during a Nexo pack reload keep the old pack until they rejoin, so restart after you change a shader look.

Post effects

With post-effects: true, players on Minecraft 26.3 and newer also get the post look of styles that have one. It needs a 26.3 or newer server, otherwise the console says once that post effects stay off.

A player gets it only while the pack check passes, their pack loaded, their cloud quality is not off, and their world has a solid layer with a post look that they have not hidden with /togglecloudlayer.

  • A client that fails to load it can lose the server pack and disconnect, so a player who leaves within 15 seconds of getting it, twice in a row, never gets it again on that server (the console names them). To undo it, stop the server and remove their UUID from players.cloud-post-off in data.yml.
  • Any other session, a kick or timeout included, resets the count, and so does a restart.
  • Players on 26.2 through ViaBackwards count as having it (nothing changes for them), so the 15 second rule can switch it off for them too.
  • Anything drawn over a cloud first, such as a see-through layer, water or another pack's end-of-frame effect, hides that part from the post look.

Players who decline the pack

Nothing breaks. Far clouds fade into their normal fog, and they see only the server look of styles.

Updated Nov 11, 2026