Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move stone blocks and textures into nested wood folder #1122

Conversation

Argmaster
Copy link
Contributor

@Argmaster Argmaster commented Feb 27, 2025

This pull request moves stone like blocks .zig.zon and texture files into nested stone folders for blocks and textures.


List of blocks considered stone like:

[
    "stone",
    "basalt",
    "basalt_bricks",
    "basalt_tile",
    "basalt_wall",
    "coal_block",
    "coal_ore",
    "cobblestone",
    "cut_diamond_block",
    "diamond_block",
    "diamond_ore",
    "ferrock",
    "ferrock_bricks",
    "ferrock_tiles",
    "ferrock_wall",
    "frost",
    "glacite",
    "glacite_bricks",
    "glacite_tile",
    "glacite_wall",
    "gold_block",
    "gold_ore",
    "ice",
    "iron_block",
    "iron_ore",
    "limestone",
    "limestone_bricks",
    "limestone_tiles",
    "limestone_wall",
    "magma",
    "marble",
    "marble_bricks",
    "marble_tile",
    "marble_wall",
    "mossy_cobblestone",
    "obsidian",
    "pebbles",
    "sandstone",
    "sandstone_bricks",
    "sandstone_tile",
    "sandstone_wall",
    "stone_bricks",
    "stone_tile",
    "stone_wall",
    "terracotta",
    "terracotta_bricks",
    "terracotta_tiles",
    "terracotta_wall",
    "void_stone",
    "void_stone_bricks",
    "void_stone_tile",
    "void_stone_wall",
]

List is based on ".tag" property including ".stone".

@IntegratedQuantum
Copy link
Member

In my opinion putting all the stone types into one folder doesn't really fix the issue. In my opinion it even makes it worse since you grouped some things in there that really aren't stones in my opinion.

I would prefer having one folder for each stone variant instead.
But before you go out and do that, please wait for #897 to avoid causing extra conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants