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

Pattern Saving #2609

Open
xdemoted opened this issue Mar 9, 2024 · 1 comment
Open

Pattern Saving #2609

xdemoted opened this issue Mar 9, 2024 · 1 comment
Labels
Enhancement New feature or request

Comments

@xdemoted
Copy link

xdemoted commented Mar 9, 2024

What feature do you want to see added?

Essentially the request is for a pattern creation system that allows for patterns to be saved and referenced later on.

Some example use cases would be:

Creating a list of all blocks that contain wood for replacement later
//pattern save wood oak_planks,acacia_wood,spruce_logs ...
//replace #pattern[wood] blue_concrete
This command would look for a saved pattern and apply that pattern to replace all blocks that match with blue_concrete

Another would be for saving patterns that are repeated often
//pattern save leaves 35%oak_leaves[persistent=true],35%jungle_leaves[persistent=true],30%air
//replace blue_concrete #pattern[leaves]

The overall goal of this is to take patterns that are repeated often and allow for easy access later on, this is especially useful when masks should be the same between builds, it would be far easier to reference an already created pattern.

Are there any alternatives?

No

Anything else?

No response

@xdemoted xdemoted added the Enhancement New feature or request label Mar 9, 2024
@OneLiteFeather
Copy link
Member

I was told by @TheMeinerLP we've had this feature before but this was a very complex and unfortunately not well implemented solution so the implementation for this is commented out as far as I know. Might give it a second try or a different way of saving (like Clipboard Connect with Redis for example)

It would benefit the building scene a lot as most of the patterns are often written down on internal documentation, also you could share the patterns directly with others with a save/load and share option.

If it is not possible to do this issue, I would suggest collecting patterns in our documentation repository as an issue for advanced patterns.

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

No branches or pull requests

2 participants