Explanation
No game assets
Why the repository holds no Minecraft files, and how the tools keep it that way.
TextureScript's repository contains no Minecraft textures, models or other game files, and never will. Those files belong to Mojang. Redistributing them, or anything traced from them, is not something an open-source tool should do or invite.
Yet the tools need vanilla constantly: to plant wheat beside your corn, to give an agent reference grids, to measure the conventions the lint enforces. The answer is to read the game from the copy the user already has.
How each part follows the rule
- Scenes read vanilla blocks from your client jar at run time and keep them in memory.
- The authoring skill ships only the authored corn example and a manifest of vanilla
textures to look at.
fetchextracts those from your own jar, and refuses to write them anywhere git would track them. - The lint rules ship as numbers, measurements of vanilla, not as textures.
- The pre-commit hook compares staged PNG and JSON files with your jar and refuses copies, re-encodes, nearest-neighbour upscales and model or blockstate JSON taken from the game.
What this asks of you
Do not commit or publish fetched references, or anything traced from them. Draw your own textures; use vanilla to compare, not to copy.