A server message configured for automatic termination, exactly as in the example on the official wiki (https://community.bistudio.com/wiki/DayZ:Server_Messages), has no effect: the server keeps running after the deadline has passed, and no countdown messages are observed.

Environment:

• DayZ Server 1.30.164078 (app 223350), Linux amd64, run in a Docker container (cm2network/steamcmd image) on Ubuntu

• Mission: dayzOffline.nasdara

• [Setup: stock/unmodified mpmissions folder OR mission folder mounted from a separate directory - state which one you tested]

Additional information:

• Right after mission load the RPT contains: "!!! [CE][offlineDB] :: No Shutdown message present." I do not know whether this line relates to messages.xml or to something else; mentioning it in case it is useful.

• Both messages.xml scenarios I tried (this one and a welcome-on-connect message) have no visible effect; see #DZG-1382.

• No errors about messages.xml were found in the RPT/script logs.

1) Put the following into mpmissions/dayzOffline.nasdara/db/messages.xml:

 <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <messages>
     <message>
       <delay>0</delay>
       <repeat>0</repeat>
       <deadline>5</deadline>
       <onConnect>0</onConnect>
       <shutdown>1</shutdown>
       <text>#name will shutdown in #tmin minutes.</text>
     </message>
   </messages>

2) Verified from inside the container that the file is readable and contains exactly this content.

3) Start the server and wait more than 5 minutes after the mission has finished loading.

According to the wiki, the Countdown flag is enabled (deadline > 0), the message is sent to players at the corresponding minutes before the deadline (here 5, 2 and 1), and after the countdown reaches zero the server shuts down gracefully.

Actual result:

• Server process started at 21:45:06 UTC; mission loading finished at 21:45:46 UTC (according to the RPT).

• At 21:51:39 UTC (almost 6 minutes after the mission loaded) the server was still running; no restart/shutdown happened, no new RPT was created.

• No countdown messages were received by the client.