Video summary

News in Data Pack Version 99.0 and Resource Pack Version 80.0 (26.1 Snapshot 6)

Main summary

Key takeaways

Gaming

Overview

This video (Minecraft 26.1 Snapshot 6) summarizes major data pack and resource pack version updates (Data Pack 99.0, Resource Pack 80.0). It focuses on on-disk storage/layout changes, world-generation feature-format updates, dirt-related tag changes, entity/data fixes, command fixes, and resource-pack / shader updates.

Storage and file-path changes

  • Dimension and world layout
    • All dimension data is now stored under dimensions/minecraft/<dimension> (for example, dimensions/minecraft/overworld).
    • Top-level data/ now only contains data that applies to all dimensions and is organized under namespace folders.
    • level.dat was updated; much specific world data was moved into separate data files.
    • Player data is moved to a players/ subfolder.
    • A world’s bundled resource pack lives in resource_packs/, but the game still only loads a single pack named resources.zip.
    • Structures saved from structure blocks are written to a folder named structure (singular) instead of structures (plural).
    • Dimension types now include a has_ender_dragon_fight boolean.

World generation and feature-format changes (mapmakers / datapack authors)

  • Rule-based providers and feature behavior
    • Rule-based block state providers (used by features like disk) can now have an optional empty fallback — an empty fallback places nothing.
    • The alter_ground tree decorator now uses a rule-based provider.
    • The tree feature uses a below_trunk provider instead of forest_dirt / dirt provider; that provider is rule-based.
  • Renamed/generalized features
    • forest_rock → block_blob (now has fields for which block state to place and what it can be placed on).
    • ice_spike → spike (now has fields for state, what to place on, and what can be replaced).
    • Huge mushroom features now include can_place_on fields.
  • Bug fixes
    • Fixed a crash for certain custom uses of the lake feature.

Dirt and tags (important for datapacks, mods, worldgen)

  • The old dirt block tag was split into multiple, more specific tags:
    • Collection tags created for mud, moss blocks, and grass blocks (each contains the blocks you’d expect).
    • The dirt tag now only contains dirt, coarse dirt, and rooted dirt.
  • New substrate and other specific tags exist for world generation conditions and feature placement, mapping to different meanings of “dirt.”
  • Mud/moss blocks/grass blocks also have corresponding item tags.

Entity and data behavior changes / bug fixes

  • Camel and saddle behavior
    • Camel husks no longer have a baby model — you cannot create a camel husk baby via commands.
    • Saddles placed on baby camels via commands no longer render (behavior changed/fixed).
  • Spawners and rendering fixes
    • Custom spawners with light limits that don’t include 15 can now spawn mobs correctly under the night sky.
    • Hanging signs now render and work properly when used in block display entities.
  • Commands and data
    • The data command was fixed so it no longer returns positive results for certain small negative numbers.

Resource pack, textures, sounds, and shaders

  • Textures and sounds
    • New textures for baby mob types were added.
    • New sound event for baby chicken steps added; a previous unwanted pixel change to baby chickens was reverted.
  • Shader changes
    • Item-entity translucent color shaders were removed.
    • entity_alpha and entity_decal have been replaced by a new dissolve flag in entity shaders.
    • Item rendering moved out of entity shaders into new item shaders (rendering split).

Practical tips / implications

  • Mapmakers / datapack authors
    • Update paths and tag references: dimension folder layout, players/, structure folder name, split dirt tags, and renamed features.
  • Resource-pack authors
    • Check new baby mob textures, the baby-chicken step sound, and adapt shaders to the new dissolve flag and item shaders.
  • Server admins
    • Be aware of behavior changes for custom spawners, structure saves, and player data location when backing up or migrating worlds.

Featured source

Slice Lime (presenter)

Rate this summary

Your feedback will help improve summaries.

Improve this summary

Reprocess with a stronger model when the summary feels incomplete or inaccurate.

Pro

Translate summary in another language

Pro

Ask questions to this video

Chat for follow-up questions, clarifications, and source-backed answers.

Coming soon

Share this summary

Original video