Sorry, bot, I was thinking that was the same as 18w06a. Why am I talking with a bot anyway?
1.8.2-pre4 confirmed... My villagers of my villager breeder despawn... All of them... I hate had change to creative to fix it on my server survival 😞
tks kumasasa for close the issue
Wow, seth... u.u but why go ahead?
man, you will not believe, I have found, the command must be
tellraw @p {text:"Line1\nLine2 <-- click",color:green,clickEvent:{action:run_command,value:"/tellraw @p {text:'Line1
nLine2',color:red}"}}
I think as it is a "second command" that have to take another "\".
As I close the issue?
Now with the functions "show_", I think this was more serious and important: MC-75721 This needs to be corrected.
Confirmed in 1.7.2.
Confirmed in 1.7.1.
(I removed what I said here about the symbol §). I made a post in the forum about it: http://bit.ly/1ccs9N8. Check it there.
Seriously? Not solved this for 1.7?
I found nothing. I searched for "accent" and "accentuation".
Sorry Kumasasa, my mistake.
Confirmed in 13w41b.
Confirmed in 13w41a.
So why do not you add the following idea which was also proposed for MC-31826?
tellraw @r {text:{playername:@p} test}
This would be sent to a random player with the name of the player closest followed by the message "test".
It would be very useful for us developers map.
Yes, just put the question because I thought relevant since it is a similar bug. And as for not being able to use "@p", "@r" or "@a", in command "tellraw", what you tell me?
So Kumasasa, the problem is that - as far as I know, if I'm wrong correct me - you can not write a message like: "/tellraw @p @r" being that my goal is to send a random name for player more close. If it were possible this command would be perfect, but not works.
Nobody to help me?
????
Yes, I'm just saying that no chat output is given even though the save have failed... I understand they don'r want to allow uppercase anymore, but at least give us an output saying the save failed.