Chat and commands run via chat trim excess whitespace

Confirmed for

• 1.8.4 For *CustomName* tag too

is this still the case in 16w04a?

It's fixed, example using required JSON structure:

/setblock ~ ~1 ~1 wall_sign 3 replace {Text1:"[\"         1\"]",Text2:"[\"\"]",Text3:"[\"\"]",Text4:"[\"\"]"}

Confirmed for

• 16w04a

Only fixed for signs

Still affects normal chat and /tellraw command

/tellraw @p {"text":"       1"}

Confirmed for 1.9

Please link to this comment in the description

The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.

The reason why this is happening is because the method net.minecraft.network.NetHandlerPlayServer.processChatMessage(CPacketChatMessage) removes multiple whitespaces before testing if the entered message is a command or not. The test whether or not the message contains the section character § is probably not needed for commands neither.

/**
 * Process chat messages (broadcast back to clients) and commands (executes)
 */
public void processChatMessage(CPacketChatMessage packetIn)
{
    PacketThreadUtil.checkThreadAndEnqueue(packetIn, this, this.playerEntity.getServerForPlayer());

    if (this.playerEntity.getChatVisibility() == EntityPlayer.EnumChatVisibility.HIDDEN)
    {
        TextComponentTranslation textcomponenttranslation = new TextComponentTranslation("chat.cannotSend", new Object[0]);
        textcomponenttranslation.getChatStyle().setColor(TextFormatting.RED);
        this.sendPacket(new SPacketChat(textcomponenttranslation));
    }
    else
    {
        this.playerEntity.markPlayerActive();
        String s = packetIn.getMessage();
        // Removed this from here
        //s = StringUtils.normalizeSpace(s);
        //
        //for (int i = 0; i < s.length(); ++i)
        //{
        //    if (!ChatAllowedCharacters.isAllowedCharacter(s.charAt(i)))
        //    {
        //        this.kickPlayerFromServer("Illegal characters in chat");
        //        return;
        //    }
        //}

        if (s.startsWith("/"))
        {
            this.handleSlashCommand(s);
        }
        else
        {
            // Added this here
            s = StringUtils.normalizeSpace(s);

            for (int i = 0; i < s.length(); ++i)
            {
                if (!ChatAllowedCharacters.isAllowedCharacter(s.charAt(i)))
                {
                    this.kickPlayerFromServer("Illegal characters in chat");
                    return;
                }
            }
            
            ITextComponent itextcomponent = new TextComponentTranslation("chat.type.text", new Object[] {this.playerEntity.getDisplayName(), s});
            this.serverController.getPlayerList().sendChatMsgImpl(itextcomponent, false);
        }

        this.chatSpamThresholdCount += 20;

        if (this.chatSpamThresholdCount > 200 && !this.serverController.getPlayerList().canSendCommands(this.playerEntity.getGameProfile()))
        {
            this.kickPlayerFromServer("disconnect.spam");
        }
    }
}

Still in 1.9.1-pre3

Still in 16w15b

Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.

This is an automated comment on any open or reopened issue with out-of-date affected versions.

This also seems to apply to giving written books using commands. Attempting to use spaces to indent/centre text:

give @s written_book 1 0 {title:"Welcome",author:"Stick God",pages:["[{\"text\":\"\\n
n Welcome
n to
n ZombieCraft\",\"color\":\"black\"}]"]}

The extra spaces are stripped out and the text in the book is left justified.

That's because you use the command in the chat, and not in a command block/function.

Confirmed for 1.13.1.

This issue also makes it impossible to disable or enable file data packs with more than 2 consecutive spaces in its name.

Confirmed for 1.14 Pre-Release 2.

Confirmed for 19w46a.

/say "a   hello"

Produces

a hello

instead.

Affects 1.15 Pre release 1.

Still a problem in 1.15.2

Is this still an issue in 1.16.3 or later?

Can confirm that this is still an issue in 21w03a.

Can confirm in 21w05b.

Can confirm in 21w06a.

Can confirm in 21w07a. Video attached.

Can confirm in 1.16.5 and 21w08b.

Can confirm in 21w11a.

Can confirm in 1.17.1.

Can confirm in 1.18.1.