From 6a846e2c403de4d84da09f6537b53b339dfde96e Mon Sep 17 00:00:00 2001
From: Jason Penilla <11360596+jpenilla@users.noreply.github.com>
Date: Thu, 28 Apr 2022 19:51:06 -0700
Subject: [PATCH] Use setMessage instead of arraycopy

setMessage affects messages, filteredMessage, and renderMessages, we were only doing an arraycopy for messages

fixes #7774
---
 patches/server/Adventure.patch | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/patches/server/Adventure.patch b/patches/server/Adventure.patch
index 12786e021f..679ce10adf 100644
--- a/patches/server/Adventure.patch
+++ b/patches/server/Adventure.patch
@@ -2424,7 +2424,9 @@ index 0000000000000000000000000000000000000000..00000000000000000000000000000000
 +        SignBlockEntity sign = new SignBlockEntity(new BlockPos(loc.getBlockX(), loc.getBlockY(), loc.getBlockZ()), Blocks.OAK_SIGN.defaultBlockState());
 +        sign.setColor(net.minecraft.world.item.DyeColor.byId(dyeColor.getWoolData()));
 +        sign.setHasGlowingText(hasGlowingText);
-+        System.arraycopy(components, 0, sign.messages, 0, sign.messages.length);
++        for (int i = 0; i < components.length; i++) {
++            sign.setMessage(i, components[i]);
++        }
 +
 +        getHandle().connection.send(sign.getUpdatePacket());
 +    }