Skip to content

Instantly share code, notes, and snippets.

@felixjones
Last active July 20, 2024 01:32
Show Gist options
  • Save felixjones/d5bec1ab0c83ee134fa43a142692a09b to your computer and use it in GitHub Desktop.
Save felixjones/d5bec1ab0c83ee134fa43a142692a09b to your computer and use it in GitHub Desktop.

Two resource packs for latest 1.17 snapshot. Try them both!

@JurassikLizard
Copy link

They will hopefully provide a better way to check what block it is (when 1.17 fully releases) than getting it from the texture atlas, as if resource packs break the shader, then that is no good.

@infibrocco
Copy link

Hopefully this built-in shader feature gets improved more and more so that we don't have to rely on optifine anymore.
And also hope that sodium can cope with these changes and if both shaders and sodium work somewhere down the line, optifine will be even more redundant.

@Doomsdayrs
Copy link

aw this doesn't work anymore ;-;

@Reeses-Puffs
Copy link

Hopefully this built-in shader feature gets improved more and more so that we don't have to rely on optifine anymore.
And also hope that sodium can cope with these changes and if both shaders and sodium work somewhere down the line, optifine will be even more redundant.

I'm sure sodium will be perfectly fine, I'm more worried about canvas

@Reeses-Puffs
Copy link

canvas already has a snapshot port going strong, so I guess they'll be fine as well

@JustResolveJr
Copy link

not working for me I have fabulous graphics enabled and have edited the pack.mcmeta to make sure it is compatible for 1.17, still nothing. I am looking at it in visual studio and it all looks fine.

@Snoworange420
Copy link

i have the same issue lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment