[MC-30955] Chat message too long when using /tellraw command

Long commands run from a click event are truncated, causing the command to fail.

Steps to Reproduce:
1.type following command in a command block:

/tellraw @a {"text":"Press to give ","color":"blue","extra":[{"text":"Click","clickEvent":{"action":"run_command","value":"/effect @a 1 30 4"}},{"text":"sec","color":"red","clickEvent":{"action":"run_command","value":"/give @a iron_sword 1 0 {ench:[{id:32,lvl:3}],display:{Name:Blade of Glory,Lore:[Hello this is Lore,This is a good weapon,I'm trying to find if there is a limit on the length of a command]}}"}}]}

2. power command block
3. click the red word "sec" in the chat.

This produces the error:

Data tag parsing failed: Unbalanced brackets:
{ench:[{id:32,lvl:3}],display:{Name:Blade of Glory,Lore:[Hello this is Lore,

Linked issues

is duplicated by 4

MC-32282 Long command block text crash Resolved

MC-33917 tellraw CommandBlock Error Resolved

MC-42486 Command Block Problems Resolved

MC-73768 "/tellraw" command will not work properly inside a command block after a certain length Resolved

relates to 1

MC-97531 Confusing error message when using run_command Resolved

Comments 32

ItsMartin 2013-09-13T12:09:12Z

Confirmed, was able to reproduce this in 13w37b.

Anon Ymus 2013-09-14T02:38:34Z

Confirmed. Even happens with the correct command:

/tellraw @a {"text":"Press to give ","color":"blue","extra":[{"text":"Click","clickEvent":{"action":"run_command","value":"/effect @a 1 30 4"}},{"text":"sec","color":"red","clickEvent":{"action":"run_command","value":"/give @a 267 1 0 {ench:[{id:32,lvl:3}],display:{Name:\"Blade of Glory\",Lore:[\"Hello this is Lore\",\"This is a good weapon\",\"I'm trying to find if there is a limit on the length of a command\"]}}"}}]}

DoobySkoo 2013-09-15T21:53:38Z

It also does the same thing for this command

tellraw @a {text:"<Dragon Slayer> Click ",extra:[{text:"here",color:gold,bold:true,clickEvent:{action:run_command,value:'/give @p 261 1 0 {ench:[{id:48,lvl:127},{id:51,lvl:1}],display:{Name:"Dragon Begon",Lore:[The bow forged from the blood of a dragon.]}}'}},{text:" to get the bow forged from dragon blood."}]}

Then gives the error and puts me on the multiplayer menu

Skylinerw 2013-09-16T19:01:22Z

Confirmed as well. It's likely because what's being issued through the 'run_command' action is being run through the player themselves. Having a shorter /tellraw command within the run_command value allows it to work. The command blocks don't have a character limit, but players do.

Matthew House 2013-09-17T22:03:48Z

I think it would be easy to detect if is was sent by a command, but I'm not a Java programmer, so I'm not sure. I hope they fix this soon, because I would really like nested /tellraw commands that don't kick me from the game.

22 more comments

Soboy 007 2013-10-04T21:00:26Z

Confirmed once again. Easy fix would be to have the server run the command as the client somehow. Would also fix the issue of needing to be an OP to run a majority of the commands used with Tellraw.

Yolandi Briel 2013-10-05T18:44:06Z

Confirmed on Windows 7 as well.

Patrick Shannon 2013-10-06T21:34:38Z

Why is there a command length limit again? I can understand the issue with chat, but command length limits make it harder for mapmakers to work.

Why not just keep the limit for chat, but not for commands?

Anon Ymus 2013-10-06T22:13:55Z

The limit is for chat; when a command is run by clicking on /tellraw text, it is effectively run through the client's chat.

Ben Lewis 2013-10-06T22:29:48Z

@Patrick There is no longer any limit on command block length but, the /tellraw "run_command" command executes the command as if the player typed the command into chat. So as there is a limit on the length a chat message can be, so this bug occurs.

How the /tellraw command (I assume) is implemented is the JSON bit of the command is sent to the applicable clients where they do all the logic from there. A possible solution is to split the logic between the server and client so the client sends the server a click event where the server executes the command(maybe on behalf of player). This would also mean non-Op issue will also be fixed. But it might be hard to split up the logic and Dinnerbone intended it to be all client side.

Skylinerw 2013-10-10T21:34:11Z

Confirmed for 13w41a

Luke Nguyen 2013-10-14T13:43:54Z

Confirmed

Skylinerw 2013-11-21T18:28:01Z

Confirmed for 1.7 and snapshots 13w47a/b/c, although it behaves differently now. Instead of being kicked off the server, your text output will either be trimmed, resulting in the loss of text, or you will receive the error "Invalid json: End on input".

Jason 2013-12-01T20:57:15Z

I know a way mojang could fix this. they just need to detect if there is a '/' at the very beginning of the chat message, and if so, the player can use more characters.

Skylinerw 2013-12-20T05:43:01Z

Confirmed for 1.7.4.

Roadsguy 2013-12-20T17:28:22Z

I suggest making it so that commands run from inside tellraw simply are treated like command block/console commands. This would simultaneously fix the annoying problems of players not being able to click to run commands in tellraw if cheats are disabled, or if they're not an op on a server (it's not like they can get a tellraw message unless another op wants them to anyway...).

Ezekiel 2013-12-24T16:45:11Z

Clients can only send a maximum of 90 characters in chat.

Skylinerw 2014-01-08T09:17:05Z

Since 1.7.4's small crashing via long messages fix, the character limit within the "value" tag has been 100 characters, which I've confirmed on numerous occasions when both creating my own commands and helping others with theirs. This can also be observed by copying a 101-character long string of text and pasting it into the chat box; the last character will be trimmed off.

Skylinerw 2014-01-12T04:51:42Z

Confirmed for 14w02c

Matthew House 2014-01-30T14:22:59Z

Confirmed for 14w04b.

Skylinerw 2014-02-08T18:37:54Z

Still present in 14w06b.

TrainerRedstone7 2014-02-22T03:04:46Z

It's still in 14w08a.

Matthew House 2014-06-25T19:30:10Z

Confirmed for 14w26b.

marcono1234 2014-06-28T12:02:54Z

Confirmed for

14w26c
14w30c
14w31a
1.8-pre 1

Like Skylinerw said earlier

This can also be observed by copying a 101-character long string of text and pasting it into the chat box; the last character will be trimmed off.

The command now gets cut off

1.8.3 And please fix the command

/tellraw @a {"text":"Press to give ","color":"blue","extra":[{"text":"Click","clickEvent":{"action":"run_command","value":"/effect @a 1 30 4"}},{"text":"sec","color":"red","clickEvent":{"action":"run_command","value":"/give @a diamond_pickaxe 1 0 {ench:[{id:32,lvl:3}],display:{Name:Blade of Glory,Lore:[Hello this is Lore,This is a good weapon,I'm trying to find if there is a limit on the length of a command]}}"}}]}

Zi-Wen Lin 2014-08-27T15:56:13Z

You can add Minecraft 1.8-pre 2 because it still appears...

Torabi 2015-03-16T13:33:53Z

The command no longer disconnects the player, but it still truncates the command and produces an error message. I've updated the issue accordingly.

Tronics 2015-11-13T05:20:31Z

Still present in 15w46a, the bug is not resolved

Paint 2015-12-29T16:17:53Z

Confirmed for 15w51b.

Tronics 2016-02-12T04:27:24Z

Confirmed for 16w06a

michael 2016-02-15T08:39:44Z

The run_command tag in tellraw is used to define commands that are sent through the games chat system when a player clicks that component in the chat window. This command has the same limitations as any command typed into the chat directly.

One solution to make the example work is using the /trigger command.

Tronics 2016-02-15T14:29:04Z

We speak about the run_command, not the suggest_command. suggest_command display the command in chat, so it's normal to limit the size. But I don't understand why the lenght should be limited with run_command. The biggest problem is with book: there are the same problem: many users report to me the problem with my book generator: command run from a book are also limited, so it's very difficult to make commands book with this limitation.

user-f2760 2016-02-15T15:06:54Z

the run_command causes you to run it, so you send the command, that's why it's still limited, making an eception will make the server say "this message is too long, kick person"