Talk:Shaders

Discussing Imports
Right now, the discussion on imports focuses on the built-ins from the  folder. There is a note which makes more sense for local imports, but it's included in the aforementioned section. Having a general section explaining  could be better, with subsections for the build-ins in   and local files within resource packs. The main section can go a bit more in depth on the limitations of. (It took a lot of fiddling to figure out there were additional limitations for imports. Not certain if it was the uppercase characters or length of the filename, or if it was those for the function inside, but shortening the filename and making it all lowercase made it stop crashing out. Before that, I did the "add a blank line to the bottom" but it hadn't fixed it.) – Unsigned comment added by MegaScience (talk • contribs) at 05:13, 23 March 2021 (UTC). Sign comments with

Page move

 * core shaders, current title is janky.  Nixinova   T   C   05:30, 23 March 2021 (UTC)
 * core shaders, I don’t really understand code so yes support. (No please don’t ask me what this means: The standard format for doubles dedicates 52 bits to the fraction, as opposed to the 23 bits used by the 32-bit float. As a result, beyond 2^30 or 1,073,741,824 blocks, the player would only be off by (2^30)/(2^52) = 1/2^22 = 1/4194304 blocks) VillagerCraftMC the Sponge! (talk | contribs | villager) 21:56, 24 March 2021 (UTC)
 * I think Resource pack, Shader and this page should be merged, as they're all vanilla shaders that can be modified with resource pack, we have no reason to put them in three pages.--Chixvv (talk) 15:29, 25 March 2021 (UTC)
 * Core Shaders is a better title. NexaForX (𝓣𝓪𝓵𝓴 05:18, 1 April 2021 (UTC)