Minecraft’s texture updates often break old builds and split the community. Resource packs like Programmer Art help, but they are global and limited. I propose an official, built-in way to access legacy textures and models through commands—no resource pack required.
How it could work:
· Bundle a small legacy asset library into the client.
· For items: use /give with a model component, e.g.
/give @s minecraft:diamond_sword[minecraft:item_model="minecraft:legacy_diamond_sword"]
· For blocks without item forms (fire, water, portal, etc.): use /setblock with a block model component, e.g.
/setblock ~ ~ ~ minecraft:fire[minecraft:block_model="minecraft:legacy_fire"]
· This works like custom player heads: the model ID is stored in the block/item data, and rendering pulls from the client’s built-in library.
Why it matters:
· Preserves old creations without forcing a global visual switch.
· Lets players mix old and new textures exactly where they want.
· Lightweight: data stays with the block/item, almost no extra space when unused.
· Technically ready: 1.21.4+ already supports data-driven models via components.
Purpose: Protect creative work from being visually erased by updates, and reduce community division.
Significance: Respects both art styles, gives builders long-term stability, and proves change does not have to mean loss.
Please consider adding this feature.
0 Comments
Please sign in to leave a comment.
Post a new comment: