Ferenc Kálmán
- feca1997
- feca1997
- Europe/Stockholm
- Yes
- No
MC-57312
Ubuntu
Ubuntu 14.04 LTS,
OpenJDK 1.7.0_55
Reproduce:
/execute @p ~ ~ ~ tp ~ ~1 ~Maybe it's on purpose, but I think it should tp the person who the execute is used on.
Another similar, but bit different issue:
/spawnpoint <player> doesn't work at all.examples:
/spawnpoint @a --> no, it tells me usage
/spawnpoint @p --> same
/spawnpoint feca1997 --> same (I thought at least this would work)/spawnpoint and /spawnpoint @a ~ ~ ~ work as intended.
Many explosions in short time looks glitchy.
May affect older versions too.
Many explosions in short time looks glitchy.
May affect older versions too.
Many explosions in short time looks glitchy.
May affect older versions too.Many explosions in short time looks glitchy.
Older versions may be affected too.
withMany explosions in short time looks glitchy.
Older versions may be affected too.Reproduce by using the following command in a repeating command block:
/summon minecraft:fireworks_rocket ~ ~ ~ {LifeTime:5,FireworksItem:{id:fireworks,Count:1,tag:{Fireworks:{Explosions:[{Type:4,Flicker:1,Trail:1,Colors:[11913727],FadeColors:[16771420]}]}}}}
withMany explosionsinshort time looksglitchy.
Older versions may be affected too.Reproduce by using the following command in a repeating command block:
/summon minecraft:fireworks_rocket ~ ~ ~ {LifeTime:5,FireworksItem:{id:fireworks,Count:1,tag:{Fireworks:{Explosions:[{Type:4,Flicker:1,Trail:1,Colors:[11913727],FadeColors:[16771420]}]}}}}Many explosions within a short time look glitchy.
It's possibly due to the overlapping background light panes.
Older versions may be affected too.Reproduce by using the following command in a repeating command block:
/summon minecraft:fireworks_rocket ~ ~ ~ {LifeTime:5,FireworksItem:{id:fireworks,Count:1,tag:{Fireworks:{Explosions:[{Type:4,Colors:[11743532],FadeColors:[11743532]}]}}}}
Many explosions within a short time look glitchy.
It's possibly due to the overlapping background light panes.
Older versions may be affected too.Reproduce by using the following command in a repeating command block:
/summon minecraft:fireworks_rocket ~ ~ ~ {LifeTime:5,FireworksItem:{id:fireworks,Count:1,tag:{Fireworks:{Explosions:[{Type:4,Colors:[11743532],FadeColors:[11743532]}]}}}}Test in newer versions:
/summon firework_rocket ~ ~1 ~ {LifeTime:10,FireworksItem:{id:firework_rocket,Count:1,tag:{Fireworks:{Explosions:[{Type:4,Colors:[I;11743532],FadeColors:[I;11743532]}]}}}}
If you push to the east/west side of a full block and try to place another full block on top of the first it will show up for a second then disappear.
In 15w35b every direction is affected.
If you push to the east/west side of a full block and try to place another full block on top of the first it will show up for a second then disappear.
In 15w35b every direction is affected.
If you push to the east/west side of a full block and try to place another full block on top of the first it will show up for a second then disappear.
EDIT: So I've found the problem: this thing only happens when you have less than 60 fps (I had ~30).
Basically if you lagg you may push into blocks a little more and you may collide with the placed one.
Cannot place block on other from east/west when game laggs.
If you push to the east/west side of a full block and try to place another full block on top of the first it will show up for a second then disappear.
EDIT: So I've found the problem: this thing only happens when you have less than 60 fps (I had ~30).
Basically if you lagg you may push into blocks a little more and you may collide with the placed one.If you push to the east/west side of a full block and try to place another full block on top of the first it will show up for a second then disappear.
EDIT: Did more testing and could reproduce with 60 fps completely randomly (sometimes happens, sometimes not)
First I was surprised that I couldn't reproduce it neither, but then I realized it's all the fault of lagg.
Reproduce:/summon AreaEffectCloud ~ ~ ~ {Particle:dragonbreath,Radius:7,Duration:1000}and try the block placing thing.
(If it doesn't lagg enough, try Radius:8-10)
If you push to the east/west side of a full block and try to place another full block on top of the first it will show up for a second then disappear.
EDIT: Did more testing and could reproduce with 60 fps completely randomly (sometimes happens, sometimes not)
If you push to the east/west side of a full block and try to place another full block on top of the first it will show up for a second then disappear.
EDIT: Did more testing and could reproduce with 60 fps completely randomly (sometimes happens, sometimes not)
EDIT: I give up it's not that annoying, and seems to be hard to reproduce.
If you push to the
east/westside of a full block and try to place another full block on top of the first it will show up for a second then disappear.EDIT: Did more testing and could reproduce with 60 fps completely randomly (sometimes happens, sometimes not)
EDIT: I give up it's not that annoying, and seems to be hard to reproduce.
Cannot place block on otherfrom east/west when game laggs.Cannot place block on other in some cases.
2016-12-14_18.45.43.pngSometimes llamas keep following an other as they'd still make up the caravan even after leashing / unleashing / killing the leader.
If you leash them they will still try to follow that llama as long as the rope let's them.This creates the cool effect of a resting caravan (see image #1), but also makes it almost impossible to leave a llama behind or assemble a new caravan (see image #2).
Llamas should only stay in formation when there's a player directly leading a lama within a certain radius, and they aren't leashed.
Sometimes llamas keep following an other as they'd still make up the caravan even after leashing / unleashing / killing the leader.
If you leash them they will still try to follow that llama as long as the rope let's them.This creates the cool effect of a resting caravan (see image #1), but also makes it almost impossible to leave a llama behind or assemble a new caravan (see image #2).
What I suggest:
The members of the caravan should keep their position, until:
- they get leashed
- a player leading a non-full caravan gets within a certain proximity of them
- their leader gets unleashed (even by dying)
In 16w50a the issue seems to be mostly resolved, though some wandering llamas from a previous caravan refused to join my recently created caravan.
Also while the leader is leashed, they still refuse to leave the caravan even when leashed.
Sometimes llamas keep following an other as they'd still make up the caravan even after leashing / unleashing / killing the leader.
If you leash them they will still try to follow that llama as long as the rope let's them.This creates the cool effect of a resting caravan (see image #1), but also makes it almost impossible to leave a llama behind or assemble a new caravan (see image #2).
What I suggest:
The members of the caravan should keep their position, until:
- they get leashed
- a player leading a non-full caravan gets within a certain proximity of them
- their leader gets unleashed (even by dying)
Sometimes llamas keep following an other as they'd still make up the caravan even after leashing / unleashing / killing the leader.
If you leash them they will still try to follow that llama as long as the rope let's them.This creates the cool effect of a resting caravan (see image #1), but also makes it almost impossible to leave a llama behind or assemble a new caravan (see image #2).
What I suggest:
The members of the caravan should keep their position, until:
- they get leashed
- a player leading a non-full caravan gets within a certain proximity of them
- their leader gets unleashed (even by dying) -> this is already done in 16w50a
Llamas keep caravan formation even when they get leashed
Sometimes llamas keep following an other as they'd still make up the caravan evenafter leashing / unleashing / killing the leader.If you leash them they will still try to follow that llama as long as the rope let's them.This creates the cool effect of a resting caravan (see image #1), but also makes it almost impossible to leave a llama behind or assemble a new caravan (see image #2).
What I suggest:
The members of the caravan should keep their position, until:
- they get leashed
- a player leading a non-full caravan gets within a certain proximity of them
- their leader gets unleashed (even by dying) -> this is already done in 16w50a
Llamas keep following an other as they'd still make up the caravan even when they get leashed.
If you have a resting caravan (see image #1) and leash their members, they still try to keep the formation (see image #2).
Yeah, I know, but still "/execute @p ~ ~ ~ tp ~ ~ ~" should be ran as the player ran it. Not a big deal, but it's still a bug I think.
But it's not a random command ran at the player, it is executed BY the player, though as he'd be OP.
If you do "/execute @p ~ ~ ~ say Hi" it will say "Hi" AS the player. (see pic)
"/spawnpoint @a" without coords doesn't work either. I guess it's different, but I don't want to create a whole new issue.
sZPeddy: /execute runs command as player would be OP
If you leave it like this then you could allow signs and books to have their texts either in String OR Compound.
It would eliminate the need of so many escape characters.
I mean just look at this:
It looks like every NBT tag has a static type, so it may not be possible to add, but would be useful.
Yeah it's because you have to escape the backslashes themself, too. That's intended and totally okay in a string but with this style it's aweful.
An other way to solve it is to just make every line a Compound and convert simple "text" to
{"text":"text"}.
Side note:
I went far enough to unload the chunks, went back and the llamas reset to having no leaders but their leashes became invisible
That's a separate issue, maybe already reported, I wasn't sure though..
It looks fixed in 19w08b.