DDRKhat
- ddrkhat
- ddrkhat
- Europe/London
- Yes
- No
MC-9424
When you perform the /clear command a player whilst they are attempting to craft, it can cause momentary visual glitches depending on the speed of repetition - the slower the more jarring.
What I expected to happen was:
A player to not notice that the /clear command is being performed - unless an item was removed from their inventoryWhat actually happened was:
Graphical crafting glitches that are very jarring for a player to work with - depending on the clock speed of the clear command.Steps to Reproduce:
1. Craft a clock (Hopper-Clock makes it most noticeable)
2. Aim some redstone at a commandblock performing the following command: /clear @a 0 0
3. Attempt to craft itemsFind attached a video clip that demonstrates the effect (first proving it's inventory only by placing blocks and using items)
When you perform the /clear command on a player whilst they are attempting to craft, it can cause momentary visual glitches depending on the speed of repetition - the slower the more jarring.
What I expected to happen was:
A player to not notice that the /clear command is being performed - unless an item was removed from their inventoryWhat actually happened was:
Graphical crafting glitches that are very jarring for a player to work with - depending on the clock speed of the clear command.Steps to Reproduce:
1. Craft a clock (Hopper-Clock makes it most noticeable)
2. Aim some redstone at a commandblock performing the following command: /clear @a 0 0
3. Attempt to craft itemsFind attached a video clip that demonstrates the effect (first proving it's inventory only by placing blocks and using items)
When you perform the /clear command on a player whilst they are attempting to craft, it can cause momentary visual glitches depending on the speed of repetition - the slower the more jarring.
What I expected to happen was:
A player to not notice that the /clear command is being performed - unless an item was removed from their inventoryWhat actually happened was:
Graphical crafting glitches that are very jarring for a player to work with - depending on the clock speed of the clear command.Steps to Reproduce:
1.Craft aclock (Hopper-Clock makes it most noticeable)
2. Aim some redstone at a commandblock performing the following command: /clear @a 0 0
3. Attempt to craft itemsFind attached a video clip that demonstrates the effect (first proving it's inventory only by placing blocks and using items)
When you perform the /clear command on a player whilst they are attempting to craft, it can cause momentary visual glitches depending on the speed of repetition - the slower the more jarring.
What I expected to happen was:
A player to not notice that the /clear command is being performed - unless an item was removed from their inventoryWhat actually happened was:
Graphical crafting glitches that are very jarring for a player to work with - depending on the clock speed of the clear command.Steps to Reproduce:
1. Build a redstone clock (Hopper-Clock makes it most noticeable)
2. Aim some redstone at a commandblock performing the following command: /clear @a 0 0
3. Attempt to craft itemsFind attached a video clip that demonstrates the effect (first proving it's inventory only by placing blocks and using items)
Decimals completely breaks it. Upon giving any of the co-ordinates in question a decimal it did nothing to the player within the radius (even if stood upon the very centre)
I swear I had made the post but apparently not.
This is still an issue even in the current latest version.
This can be resolved by properly formatting your Summoned Item
/summon Item ~ ~2 ~
{id:1,Age:5900}(Stone with 10s of life - spews tons of Item Entity has no item?!
/summon Item ~ ~2 ~ {Item:
{id:1},Age:5900} (Stone with 10s of life - does NOT)
The difference between these two items is that the item spawned has a tag Item: Not FULLY sure why this resolves the issue, but it works for me.
It would seem like spawners are suffering the same issue as an improperly formatted command if that is the case. So the issue could be in that it is not summoning an item properly.
I can say that this issue STILL exists all the way up to the (currently latest) snapshot (14w02c)
Personal environment: Windows 7 (64x) - Java 7 (64-bit).
Server environment: ubuntu 12.04 (32x) - Java 7 (32-bit).
Are you sure you properly formatted the command?
try the following command;
/spawnpoint @a ~ ~ ~
It will set EVERYBODY'S spawnpoint to YOUR current co-ordinates.