Plutonium updates & restarts

Plutainer applies updates on startup when auto-update is enabled. Restarts wait for a fresh player count of zero and share the fleet’s rolling restart limit.

{#if error}{/if} {#if notice}

{notice}

{/if} {#if data}

Latest published revision: {data.release.revision ? `r${data.release.revision}` : 'Unknown'} · Production manifest · Changelog {#if data.release.checkedAt} · Checked {$timeFormat.dateTime(data.release.checkedAt)}{/if}

{#if data.release.error}

Update check failed: {data.release.error} Any displayed release is cached.

{/if}
{ event.preventDefault(); void refresh({ action: 'schedule', enabled, time, timeZone: $timeZone }); }}>

Saving uses your selected timezone and follows its daylight saving changes. If the time is skipped, the queue starts at the next valid minute; repeated times run once.

{#if data.schedule.enabled && data.schedule.timeZone !== $timeZone}

The saved schedule is {data.schedule.time} in {data.schedule.timeZone}. Save to use {$timeZone} instead.

{/if}

This restarts all fleet servers daily, even without a new release. Busy servers may restart later. Disabling the schedule stops future runs; cancel existing queued restarts below.

{#if data.schedule.nextAt}

Next run: {$timeFormat.dateTime(data.schedule.nextAt)}

{/if}
{#each data.servers as server (server.server)} {:else}{/each}
ServerRunning revisionUpdate statusAction
{server.server} {server.revision ? `r${server.revision}` : 'Unknown'} {#if server.checked_at}Checked {$timeFormat.dateTime(server.checked_at)}{/if} {#if server.error}{server.error}{/if} {server.revision === null || data.release.revision === null || data.release.error ? 'Unverified' : server.revision < data.release.revision ? 'Update available' : server.revision > data.release.revision ? 'Ahead of published release' : 'Up to date'}
No fleet servers yet.
{#if data.servers.length}{/if} {#if data.jobs.length}

Restart activity

{/if} {:else}

{busy ? 'Loading maintenance status…' : 'Maintenance status unavailable.'}

{/if}