Skip to content

[Suggestion] Load vanilla blocks from list instead of hardcoded function #177

@LVinnyFN

Description

@LVinnyFN

Is it possible to registry vanilla blocks just as modded ones?

If so, I think it would make the mod more configurable. I saw the vanilla blocks are set via a hardcoded "list" inside a function, instead of a config file. Since the block IDs must be hardcoded somewhere, why not a config file. Maybe with even some regex syntax to allow/prevent a whole category of being added, like every ID containing the word stone, or something like that. This regex syntax part would also be usefull for adding modded blocks, something like: biomesoplenty:*_planks. And with just a single line all planks from BoP are set (I know the code part isn't simple like that, but for the final user it would be nice).

With that, we can better filter which blocks we want microblock variants and which blocks we don't.

I love using this mod on creative mode and sometimes the UI get a bit poluted with LOTS of variants that I will never use. It would also be cool for survival games, where I could configure which kinds of blocks can be crafted on microblock variants, since if the block isn't included on that list, we simply can't craft it.

Edit: Additionally with another config file, it would be nice to completelly ban some microblock variant. Let's suppose I think only the covers and hollow covers are cool/useful, then I can check false on every other microblock variant and then only covers and hollow covers microblock variants will be generated for every block on my custom registry

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions