跳到主内容
Ciallo
← 服务器文集

Server Constitution · Draft for Review · 58 / 60

Chapter 58: Downtime and Recovery: Putting Maintenance Explanations Into Practice

待审阅草案。本文不代表服务器已正式采用这些entries款,执行范围和权限以现行公告为准。

Text size18
Read at your own pace

Article 536: State the Known Status in Announcements

A downtime notice may state the affected scope, confirmed status, actions to pause, and where to check the next update. If recovery time is unconfirmed, say investigation continues instead of inventing precise minutes. Players may describe specific effects, and administrators may explain real-life availability. Neither bans on criticism nor notification bombardment substitute for communication.

Article 537: Check Before and After Recovery Separately

Before recovery, maintainers check what is actually usable. Afterward, players first inspect key buildings, items, and unconfirmed trades. Not every disconnection causes rollback, and not every system saves to the same moment. Results should refer to actual data. One normal login screen does not guarantee every system is unchanged, nor does one discrepancy mean all data is lost.

Article 538: Repeated Actions With Uncertain Results

If payment, sale, or authorization shows no result during disconnection, check first rather than retry repeatedly. Administrators may assist using actual records while players provide times, people involved, and interface feedback. Separate new effects of repeated actions from the original fault. Do not simply blame players for all consequences or promise unconditional restoration before facts are confirmed.

Article 539: Explain Recovery Capabilities Honestly

Logs, screenshots, and world backups serve different purposes. Confirm their actual available scope. Without relevant data, discuss manual repairs, returns, or other feasible options without falsely claiming every detail is restored. If remedies affect third-party buildings, balances, or permissions, check actual rights rather than arbitrarily transfer losses to reassure one player.

Article 540: Concluding Maintenance Matters

After handling the issue, state which features are confirmed usable, which remain paused, and what those involved still need to do. Leave unconfirmed causes open and update when new facts appear. For changed long-term equipment conditions or an inability to continue operating, organize actual handovers and preservation capabilities. Do not promise permanent availability or treat honest limits as abandonment of every responsibility.

在两部文集中查找

Search涵盖介绍与宪法草案的All正文。

Contact Ender

Say hello, discuss a commission, or send a little kindness. Here's where to find me.

© 2026 Ender · Cat Garden