EngineHub / EngineHub/WorldEdit

When omitting a material while aiming crosshair at same as with //hpos1 | //hpos2, use that.

Open
#2,272 4 comments 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

### The Problem

I'm too lazy to type `//walls smooth_red_sandstone_slab[type=bottom]` a lot. When I place one at the edge of my roof and type `//hpos2` (or `//hpos1`, depending on which side I'm adjusting), and then `//walls`, my crosshair already points to the correct material. It feels frustrating to have to type it. Completion and clipboard only help some of the time.

### A Solution

The `//walls` or `//set` commands could use the aimed-at material when I omit the explicit material parameter. To avoid accidents, I'd save the aimed-at material from the previous `//hpos1` or `//hpos2` command (one memory slot for both) and only assume it if it matches the current aim.
I'm not sure how strict the match should be about block state, though.

### Alternatives

_No response_

### Anything Else?

Thanks for WE, it's a great tool!

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.