Integration between Watchdog and Autopause?

[Knufle]

Enhancement Type

Improve an existing feature

Describe the enhancement

I'm running a cobblemon server https://modrinth.com/modpack/cobblemon-fabric with the following yaml

services:
  minecraft_cobblemon_fabric_modpack:
    image: itzg/minecraft-server:java21-alpine
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"
    environment:
      EULA: "TRUE"
      TYPE: "MODRINTH"
      MODRINTH_MODPACK: "cobblemon-fabric"
      ENABLE_AUTOPAUSE: "TRUE"
      MAX_MEMORY: "4G"
    volumes:
      - mc_cobblemon_fabric_data:/data
    restart: unless-stopped
volumes:
  mc_cobblemon_fabric_data:

And I've noticed that everytime the server autopauses it crashes because of watchdog from what I was able to understand.

[Autopause loop] MC Server listening for connections - pausing in 600 seconds

[Autopause loop] No client connected since startup / knocked - pausing

[15:38:08] [RCON Listener #1/INFO]: Thread RCON Client /0:0:0:0:0:0:0:1 started

[15:38:08] [Server thread/INFO]: [Rcon: Saved the game]

[15:38:08] [RCON Client /0:0:0:0:0:0:0:1 #2/INFO]: Thread RCON Client /0:0:0:0:0:0:0:1 shutting down

[2025-01-19T15:38:08+00:00] [Autopause] Pausing Java process

[15:40:32] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 143850ms or 2877 ticks behind

[15:40:32] [Server Watchdog/ERROR]: A single server tick took 143.85 seconds (should be max 0.05)

[15:40:32] [Server Watchdog/ERROR]: Considering it to be crashed, server will forcibly shutdown.

Crash report: https://logs.notifiarr.com/?208efb44bfba53ce#AVBL15eX7QKKgM7bKNfkNRvBWVDCK2hxM4tepbkdTsk8

Is there any way to circumvent this?

[itzg]

Read the box that says "important"

https://docker-minecraft-server.readthedocs.io/en/latest/misc/autopause-autostop/autopause/

[Knufle]

Read the box that says "important"

https://docker-minecraft-server.readthedocs.io/en/latest/misc/autopause-autostop/autopause/

How are you always so fast? I was adding a comment with exactly that link when you replied lol, yeah, I tested here and just adding MAX_TICK_TIME=-1 fixed it, thanks