WORLDEDIT-3122 - Reported by rsod

When I do /gmask 18, or /mask 18, or /mask leaves /gmask leaves, it works... really weird... look:
http://www.youtube.com/watch?v=TgYho-kJM1s&feature=youtu.be
It doesn't replaces all leaves, just some of them..

Comment by rsod

version 3165-75b9f3e

Comment by PseudoKnight

It works in build 3080 for 1.7.5. Might be something in the recent WorldEdit overhaul.

Comment by sk89q

I think I encountered this bug the other day. I couldn't figure out why it wasn't replacing blocks and I was sure that I had the mask correct.

Comment by rtcabooservb

Issue with replace not replacing all blocks still occurs with the latest dev build. Ticket should be reopened. :(

Comment by sk89q

I was able to reproduce this with #3165 but I can't reproduce it with #3237.

How reliably reproducible is this?

Comment by rtcabooservb

Using worldedit 3242, I am able to replicate the issue every time. It seems using the block wildcards in the command, the issue doesn't occur. But when specifying exact ID data, it occurs.

Example.

//replace 18 1 (Or alternatively //replace leaf stone)
http://i.imgur.com/DPdNqVR.png

//replace 18:0 1
http://i.imgur.com/VK6qBsS.png

Occurs with other IDs being specified specifically and doesn't need to be replaced to stone. Just used stone to easily tell the difference between leaves.

Comment by sk89q

Err shouldn't it not replace all the leaves if you specify :0?

Not all leaves have :0. Use /info, right click the leaves that aren't replaced, and check the data values in the brackets?

Comment by rtcabooservb

What I did was got oak tree saplings and used bonemeal to grow the tree. All those leaves should be oak leaves. I thought 18:0 is oak leaves, 18:1 is spruce leaves, 18:2 is birch leaves, and 18:3 is jungle leaves.

And I thought if I don't specify :# or type leaves instead of an ID, it uses the block wildcard, which replaces all leaves. However, specifying :0 (which only works on those leaves by the way, I tested all other variations of :# to make sure I got the ID right), does not replace every single leaf in the tree. When typing the command again, more leaves turn to stone, so they all have the same ID, just not all being replaced at once.

Comment by PseudoKnight

There is more than one type of oak leaves.

Comment by rtcabooservb

Very odd behavior with this. :(
Testing on dev build 3259.

1A) //replace 18 1
1B) //undo
2A) //replace 18:0 1
2B) //undo
3A) //replace 18:0 18:3
3B) //undo
4A) //replace 18:0 1
4B) //undo

http://imgur.com/WbqvHzn
http://imgur.com/3CzccYV
http://imgur.com/gbPpk8b
http://imgur.com/Awk9iS5

./info on the leaves not being replaced outputs the data

@(x, y, z coords): #18 (Leaves) [8] (14/15)

After some time has passed, a so called cooldown period, more blocks are replaced when typing the command again. Spamming the command only replaces 0/1/2 blocks at a time, but after a longer wait in-between command inputs, typing again replaces 10+. Sometimes it replaces all leaves as intended if it isn't 'cooling down'.

@(x, y, z coords): #18 (Leaves) [8] (10/11)
@(x, y, z coords): #18 (Leaves) [8] (3/4)

Comment by PseudoKnight

Just so you're aware: http://minecraft.gamepedia.com/Leaves#Data_values