Minecraft guides — page 4
Practical write-ups on commands, datapacks, building and server performance — each one paired with the tool that does the work.
Post effects and loot pools: the two halves of one chest
A loot pool's weights decide what drops; the /posteffect command decides how it feels. Both are numbers you can check before writing the datapack.
Sponge and structure blocks are not the same file
A .schem, a .litematic and a Bedrock .mcstructure look interchangeable until you convert one and every chest, entity and block state is gone.
The armor texture you replace is not the one you think
Armor is layered and split by material, so painting the wrong file leaves your pack looking untouched in game.
The End achievement toast is the one that never fires
Advancement toasts are drawn at the game's own pixel size, and the End achievement is the one players screenshot most and reproduce worst.
The GUI recolour that survives every bevel: brightness, not flat fill
Painting a flat colour over Minecraft's inventory kills every shadow and highlight. The GUI Colorizer keeps them by driving the gradient from brightness instead.
The same red text breaks on Java and Bedrock
A colour code that renders perfectly in one plugin shows up as literal ampersands in the next. The format is the reason, not the plugin.
A cape texture is 2,048 pixels and the cape itself draws only 372 of them
The file is 64×32, the cape lives in a 22×17 corner, the elytra in the block beside it, and the side people actually see is 160 pixels — under 8% of the image. Plus the one-pixel offset that catches everyone.
A trimmed armour set has 1.57 billion possible appearances, which is why the lock button exists
199 states per slot to the fourth power. Rerolling all four at once will never converge on a look — locking the pieces you like turns an unsearchable space into a workable one.
A custom head stores a URL wrapped in base64 JSON, not an image
The profile component holds base64 of {textures:{SKIN:{url:…}}}. That is why a head's look is fixed at the moment it was made, and why the database can be tens of thousands of entries.
A Minecraft username is 1–16 characters of exactly three things, and a UUID has two spellings
Letters, digits, underscore. No hyphens, no dots, no spaces. And a UUID is accepted with or without its dashes — which is why one lookup fails and the identical one works.