EngineHub / EngineHub/WorldEdit

New Block Category Pattern for Targeted Block

Open
#1,674 1 comment 0 reactions 0 assignees View on GitHub
status:pending type:feature-request
Dominant language
Java
Stars
3.5k
Forks
960
Avg merge
6h 57m
Merged PRs (30d)
1

Description

**Is your feature request related to a problem? Please describe.**
This request does not necessarily solve a problem, but instead allows for rapid editing of selected blocks based on blocks already in your environment, without typing out the entire block name and associated data. It could potentially assist players in doing block edits even if they do not know the block name or format of the blockstate data, simply by looking at the block they want to use.

**Describe the solution you'd like**
An example usage of this feature could be as simple as `//set #targeted` where the current WE selection would be replaced with whatever block is currently displayed in the Minecraft F3 window under Targeted Block or, put more simply, whatever block you are currently looking at. Other examples could be things like `//replace #targeted stone` or `//gmask #targeted`

**Describe alternatives you've considered**
The default raycast length used in the F3 window to query the Targeted Block would be sufficient, but if that raycast length could be extended, it would be even more helpful when using this feature.

In a best case scenario, one would be able to store two different #targeted selections as variables (most likely as part of a CraftScript), then run a command or script like `//replace #targeted1 #targeted2` This would allow a builder to do rapid replacements of block selections just by looking at two different blocks and running one command.

**Additional context**
![1](https://user-images.githubusercontent.com/10479671/107724691-122b4d80-6caa-11eb-9207-bfbd1a1d9add.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.