Medium Impact Shaders

Medium impact is the largest group on the site: thirteen packs, which is more than the low, high and ultra tiers put together. That is not an accident. It is the level at which a shader can do proper directional shadows, volumetric light and reflections without needing hardware that most players do not own.

Twelve of the thirteen ask for 2 GB of video memory. Complementary Reimagined asks for 3 GB, because it reads PBR resource packs and holds more texture data while it works. Every pack at this level wants 4 GB of system memory behind it, which is double what the low tier asks and the clearest sign that this tier expects a dedicated card rather than an integrated chip.

The thirteen come from three categories. Seven are realistic packs, five are fantasy packs, and one, Soft Voxels Lite, is a performance pack that climbed a tier to afford voxel lighting. In practice that means the hardware question is already settled when you arrive here and the remaining decision is entirely about how you want the world to look.

If you want the world to look like a plausible place, the realistic seven are BSL Shaders, Complementary Reimagined, Nostalgia Shader, Sildur's Vibrant Shaders, Chocapic13's Shaders, ProjectLUMA and Noble Shaders. BSL is the usual starting point and covers every version from 1.7.10 to 26.2.

If you want it to look illustrated, the fantasy five are Miniature Shader, Oceano Shaders, AstraLex Shaders, Pastel Shaders and Enchanted Shaders. They range from the tilt-shift miniature effect to a chalky pastel palette, and none of them costs more than the realistic seven.

Soft Voxels Lite is the odd one out and worth singling out. It is the only pack at this level that builds a voxel model of the light around you, so coloured shadows fall correctly rather than being approximated, and it does that inside the same 2 GB budget. It covers 1.19 to 1.20.1, which is where its updates stopped, and it needs Iris.

Thirteen packs sit here, which means that for the first time the question is not whether your machine can hold the pack but which parts of it you want. All of these ship a settings menu, and three sliders in it account for most of the difference between comfortable and not.

Shadow resolution is the first. It sets how much detail the shadow map holds, and doubling it quadruples the memory the shadows take. If the pack stutters when you turn quickly, this is what to lower, and the visible result is slightly softer shadow edges at a distance.

Volumetric lighting is the second, and it is the effect that is expensive in a way that does not show up in a still screenshot. It costs per frame regardless of whether there is anything in the air to light, so in a flat, cloudless world you are paying for something you cannot see. Turning it off in the desert and back on in a jungle is a legitimate way to play.

Reflections are the third and the most negotiable. Screen-space reflections cost roughly in proportion to how much water is on screen, which means an ocean base pays for them constantly and an underground base never notices. If your world is mostly inland, this is free performance.

The thing not to lower first is texture quality or render distance, which is the instinct people bring from playing without shaders. At this level the shader is the expensive part and the world is not, so a change inside the shader menu buys back far more than the same effort spent outside it.

Thirteen packs sit at this level, and they all spend their budget on roughly the same four jobs. Knowing what those jobs are makes the settings menu readable, because every slider in it belongs to one of them.

The first job is the shadow map. The scene is drawn once from the point of view of the sun, and that image is used to decide what is in shadow. Shadow resolution sets how detailed that image is, and shadow distance sets how far from you it is drawn. Both cost memory rather than raw work, which is why lowering them helps a card that is short of memory more than one that is short of speed.

The second job is what the game already drew. Screen-space reflections take the image on your screen and reuse it as the reflection in water and on polished blocks. It is cheap, it is convincing until something needs to reflect that is behind you, and it costs in proportion to how much reflective surface is on screen. An ocean base pays for it constantly.

The third job is the air. Volumetric lighting samples along the line between your eye and every surface to decide how much light is hanging in the air on the way. That is where the fog, the godrays and the shafts through a canopy come from, and it costs the same whether or not there is anything interesting in the air, which is why it can be turned off in a flat, clear world without losing much.

The fourth job is everything applied to the finished image: bloom around bright pixels, colour grading, and any sharpening. These are the cheapest passes on the list and the most visible per frame spent, which is why even the low tier keeps bloom.

That order is also the order to lower things in when a scene stutters. Shadow resolution first, reflections second, volumetric lighting third, and the final image passes last, because those are what make the picture look finished in the first place.

There is a standard list of advice for making Minecraft run better, and about half of it is either irrelevant once a shader is loaded or actively counterproductive. Knowing which half saves an evening.

Lowering the texture quality rarely helps at this level unless you are running a high resolution resource pack, because the shader work has little to do with how detailed the block textures are. Turning off fancy graphics does less than it used to, since the pack has replaced most of what that setting controlled. And capping the frame rate does not make anything faster; it only makes what you have steadier, which is worth doing for a different reason.

The advice that does hold up is duller. Give the game more memory than the default profile does. Keep the render distance sensible rather than heroic. Close the browser. And prefer the loader that runs alongside a rendering optimiser, because it raises the floor before the shader has done anything at all.

The one exception worth respecting is the smooth lighting setting in the game itself. Some packs replace it entirely and some read it, so it is worth toggling once and looking rather than assuming.

Both feel like the game running badly and they have opposite causes, so telling them apart saves you from tuning the wrong thing.

A slowdown is even. The frame rate is lower than you would like, but it is consistent, and it responds gradually as you lower settings. That is the machine being asked to do more work than it can, and any of the sliders will help in proportion.

A stutter is not even. Everything is fine and then it is not, usually when you turn a corner, cross into new terrain or a storm starts. That is almost always memory rather than speed: something new had to be loaded and there was no room for it. Lowering shadow resolution or render distance frees room; lowering the effects that were already running does very little.

The quick test is to stand still in a familiar place and turn slowly on the spot. If it is smooth there and rough while exploring, you are dealing with the second problem, and the settings that fix it are the ones that decide how much of the world is held at once.

The most common cause of disappointment at this level is a high resolution texture pack quietly competing for the same memory. Try your candidate with the default textures once, purely as a control.

This is the level most people should start at if their machine allows it. It is where the effects that made you want a shader in the first place become affordable, and where the choice stops being about hardware and starts being about what you want the world to look like.

Write down the settings you changed. The menus at this level are long, the names differ between packs, and an update can quietly reset them. A short note beats rediscovering the same three adjustments every few months.