A short system/server chat message containing two newline characters does not display as three readable lines. Only the first line is fully visible. Thin fragments of text are visible immediately below it, consistent with subsequent lines being vertically clipped.

The message is sent in one call to PlayerBase.MessageImportant(). The test payload is only 115 ASCII characters, including the two line breaks, so it is below the logged ChatMaxSystemLength value of 1000. No space padding is used in this test.

The screenshot is consistent with vertical clipping. It does not by itself prove whether the complete payload reaches the text widget unchanged.

The public ChatLine implementation passes the message text to TextWidget.SetText(). The extracted gui/layouts/day_z_chat_item.layout used during this investigation has a 25-unit root height and "size to text v" 0 on the text widget. These are possible implementation leads, not a confirmed root cause.

1. Start a local server and connect a player with Game Messages enabled.

2. After the client has loaded, send the following string to that player:

player.MessageImportant("[SERVER RESTART] 1 minute remaining.\nPark safely and finish your current action.\nPlease log out before the restart.");

3. Observe the message in the bottom-left chat area.

For the same local test mission, the attached init.c sends this payload once, five seconds after connection.

Only [SERVER RESTART] 1 minute remaining. is fully readable. The second and third lines are not displayed as complete readable lines; a thin red fragment is visible below the first line.

All three lines should be readable, with enough vertical space allocated for the complete message. Any subsequent chat rows should be positioned so that they do not overlap the multiline text.